LUND CARDS · THE INSTRUMENTS

LUND CARDS · THE INSTRUMENTSNº 066 · PROPOSED

THE CRITICAL PATH CARD — the LSC-1 face, front

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE CRITICAL PATH CARD · the path, and the float around it

WAKES WHEN tasks with durations and dependencies must become a schedule

THE LOOP

Name the card; ask for the task sheet: id, name, duration, deps
Run `critical_path.py run tasks.csv -o PATH.md`
Read the finish and the path; every task on it is the schedule
Read the floats; a task with float can move without moving the finish
Hand PATH.md to whoever owns the calendar

NEVER

Refuse to estimate a duration; the numbers are the planner's — THE INTENT CARD checks the plan's who and when
Refuse a sheet with a cycle in it; name the cycle and stop
Refuse to call a task critical because it feels important; only zero float is critical
Refuse to invent proof, prices, quotes or numbers

IN THE BOX

PROOF

THE PUNCH · SHA-256 OF SKILL.MD · 35210A07B2D960EAB57108A9

THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →

THE CRITICAL PATH CARD

the path, and the float around it

EXCHANGE · CRITICAL PATH ABOARD · SELFTEST

LEGENDARYWITNESSEDIN CLAUDE IN LUNDR IN CHATGPT

WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →

What it is.

Tasks with durations and dependencies go in; earliest and latest start and finish, the float of every task and the critical path come out. A plan is a schedule only once this has been run, and a slip on the path is a slip on the finish. The card carries critical_path.py, the machine, with a selftest that builds its own fixture, and audit.py, the packet’s own gate.

Durations are in whatever unit the sheet uses and are not questioned. Resource limits, calendars and lag are not modeled; the path is the dependency path. A plan with no dependencies has no path, only a longest task.

What’s in the buy.

scripts/critical_path.py — the machine (run)
scripts/audit.py — the packet’s own gate
CARD.md · SKILL.md · TIN · LICENCE + LEDGER · MANIFEST, every file hashed · the two faces, card.json, card.html

PROOF · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 5 — 25 of 25 → 98 of 100 · WITNESSED. · CUT 2026-09-08 · PUNCH 35210A07B2D960EAB57108A9

ON EVERY DOOR · A CARD FOR YOUR AI, A FILE FOR YOUR COMPUTER

This card is an Agent Skill on the open standard: the same folder loads unmodified in Claude, ChatGPT and Codex, Copilot and VS Code, Cursor, Gemini CLI, Goose, OpenCode and the rest of the showcase. Its words are Markdown, so any chat with an instructions box holds them, any local model runs them offline, and any MCP client can load them — THE UNIVERSAL CUT: a pasteable system card, the rules-file family, an Ollama Modelfile, an MCP server, all cut from this card’s own SKILL.md by THE CARD FORGE. The universal cut is in this card’s box. And card.html — the card as one file for your computer: both faces, the tin, the words, every door; offline, in any browser. The machines aboard run wherever the host can run Python; the words run everywhere. The host marks →

Take it.

Nº 066 · PROPOSED —LAUNCHING SOON

Sold as is under the term printed. A card instructs an AI you operate; results depend on your model, your files and your judgement. Not legal, tax, medical or financial advice. The terms →

LAUNCHING SOON

THE TERM LADDER · PICK YOUR WINDOW

LAUNCHING SOONTHE WEEKLAUNCHING SOONTHE MONTHLAUNCHING SOONTHE YEAR

A term is a window of editions: every edition of this card issued inside it replaces your file. When the window closes, the file you hold keeps working — freeze, not loss. Nothing auto-renews; come back and take another term when you want the next editions.

LAUNCHING SOON.

← ALL THE CARDS · THE DECK