THE METHODS · THE STUDIO ROOM · Nº 437 · EDITION 2 · LAUNCHING SOON

LUND CARDS · THE METHODSNº 437

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE ROAD CARD · The road seat: milestones with owners, dates and dependencies; the path; the slips named.

WAKES WHEN A project has a date and nobody can say which milestones must fall in which order. · Something slipped and no one knows what it drags with it. · A board wants the critical path on one sheet. · A milestone is marked done and nobody wrote the day.

THE LOOP

Lay the milestones with owners and dates
Check: CYCLE, OUT OF ORDER, NO OWNER
Find the critical path and the slack
Board the slips; shift what depends

NEVER

Never marks a milestone done without a day
Never hides a slip from the board
Never shifts the file in place
Never claims a certainty it does not have

IT MAKES check — CYCLE with the loop, OUT OF ORDER with both days, NO OWNER, DONE WITHOUT A DAY (never counted done); exit 1 on CYCLE or DONE WITHOUT A DAY, the others named for a person; path — the critical path: the longest chain in days from the earliest due day through the dependencies to the latest, each hop with its days, and the slack of every other milestone; refused on CYCLE or OUT OF ORDER (exit 1); board — every milestone LATE (days late, what it drags), AT RISK (due inside warning_days), ON TRACK or DONE, in that order; the slips listed; a done row with no day is DONE WITHOUT A DAY, not DONE; shift — a new sheet with X and everything downstream of it moved N days (a done milestone is not moved); NEVER IN PLACE when --out is the input, ALREADY DONE when X is done (each exit 1); UNKNOWN ID exit 2.

THE LAW A road is a sheet of milestones, each with an owner, a day and what it waits on; the machine finds the order and the longest chain, and says what a slip drags with it. A milestone is done only with the day it was done; a slip is on the board the day it happens. The sheet is never rewritten in place: a shift writes a new sheet.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/road.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (9 tests) · references/ (schema + fictional demo) · START-HERE.md · system/ doors · MY-LEDGER.md · LICENSE-NOTE.md · card.svg · card.json · card.html · AUDIT.md · MANIFEST.md · WITNESS.md · SELFTEST.md.

PROOF SELFTEST 14/14 · witnessed in Claude 2026-10-14 on fictional fixtures · the test prompts in fresh chat, 9/9 · Edition 2.

THE SEAL 98 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 5

IT CAN BE WRONG an AI reading a text file: it can be wrong and can invent a number, a rule, a name or a date; check what matters against your own records and the source; the risk is yours. LICENSE-NOTE.md rides in the packet and is the licence.

THE PUNCH · SHA-256 OF SKILL.MD · 56EC7FB790E411EE8957CB9A

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

THE ROAD CARD

The road seat: milestones with owners, dates and dependencies; the path; the slips named.

CHECK · PATH · BOARD · SHIFT

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 →

THE SPEC SHEET · READ BEFORE YOU BUY · THE STANDARD EVERY CARD MEETS →

SEAL: 98 of 100 · LEGENDARY · WITNESSED
EDITION: E1 · witnessed 2026-10-14
MACHINE: scripts/road.py · 4 commands · selftest 14/14
RUNS: On your own computer. Standard library only, offline; no account, no key, no telemetry.
HOSTS: Claude · Claude Code · ChatGPT · Gemini · any AI that reads a file (START-HERE.md and system/ name each door)
LICENCE: One person, any number of their own AIs and computers · editions replace files · nothing renews · freeze, not loss
PUNCH: 56EC7FB790E411EE8957CB9A · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE ROAD CARD, Edition 2. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=road-card. Punch 56EC7FB790E411EE8957CB9A. Retrieved 2026-10-14.

What it is.

Use when a project needs its milestones laid on a road with owners, dates and dependencies, the critical path found and slips reported. Not for daily task lists or for a look-back.

It carries a machine that shows its working: check — CYCLE with the loop, OUT OF ORDER with both days, NO OWNER, DONE WITHOUT A DAY (never counted done); exit 1 on CYCLE or DONE WITHOUT A DAY, the others named for a person; path — the critical path: the longest chain in days from the earliest due day through the dependencies to the latest, each hop with its days, and the slack of every other milestone; refused on CYCLE or OUT OF ORDER (exit 1); board — every milestone LATE (days late, what it drags), AT RISK (due inside warning_days), ON TRACK or DONE, in that order; the slips listed; a done row with no day is DONE WITHOUT A DAY, not DONE; shift — a new sheet with X and everything downstream of it moved N days (a done milestone is not moved); NEVER IN PLACE when --out is the input, ALREADY DONE when X is done (each exit 1); UNKNOWN ID exit 2 — 14 checks in its selftest. It never marks a milestone done without a day; never hides a slip from the board; never shifts the file in place; never claims a certainty it does not have.

The law, written into the card.

It is in the card itself, so the AI follows it.

THE LAWA road is a sheet of milestones, each with an owner, a day and what it waits on; the machine finds the order and the longest chain, and says what a slip drags with it. A milestone is done only with the day it was done; a slip is on the board the day it happens. The sheet is never rewritten in place: a shift writes a new sheet.

The method.

Lay the milestones: id, name, owner, due day, what it depends on (by id), status; one row each.
Check the sheet: a dependency loop is CYCLE; a milestone due before what it waits on is OUT OF ORDER; a blank owner is NO OWNER; nothing proceeds on a sheet with a CYCLE.
Find the critical path: the longest chain of due days through the dependencies, and the slack on everything off it.
Board it by today's date: LATE, AT RISK (due inside the house's warning window), ON TRACK, DONE; the slips listed with the days.
Shift a milestone by n days into a new sheet, dragging everything that depends on it; the old sheet stays as the record of what was promised.

What you bring.

The milestones, with owners and dates.
What each depends on.
The house's warning window, in days.

Planned as a separate seat, not in this box and not yet on sale: the studio's own roads for its builds.

What it does once your AI has it.

check CYCLE with the loop, OUT OF ORDER with both days, NO OWNER, DONE WITHOUT A DAY (never counted done); exit 1 on CYCLE or DONE WITHOUT A DAY, the others named for a person
path The critical path: the longest chain in days from the earliest due day through the dependencies to the latest, each hop with its days, and the slack of every other milestone; refused on CYCLE or OUT OF ORDER (exit 1)
board Every milestone LATE (days late, what it drags), AT RISK (due inside warning_days), ON TRACK or DONE, in that order; the slips listed; a done row with no day is DONE WITHOUT A DAY, not DONE
shift A new sheet with X and everything downstream of it moved N days (a done milestone is not moved); NEVER IN PLACE when --out is the input, ALREADY DONE when X is done (each exit 1); UNKNOWN ID exit 2

What it will never do.

It never marks a milestone done without a day; never hides a slip from the board; never shifts the file in place; never claims a certainty it does not have.

Where it hands off: Looking back after the road is walked → THE AFTER-ACTION CARD; Ranking which project to run first → THE BOARD CARD; The tasks inside one milestone → the team's own task list.

It is not a promise of delivery. It is an AI reading a text file: it can be wrong, so check what matters against your own records and the source. The holder brings their own AI; no endorsement by Anthropic or any other AI company is claimed.

What’s in the buy.

SKILL.md — the card your AI reads: when it wakes, the loop, the never-lines, the hand-offs.
CARD.md — the whole card in ten sections: face, law, method, machine, what you bring, never, tests, seal, term.
scripts/road.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
tests/EVALS.json and scripts/evals.py — 9 test prompts and the offline runner that scores your AI's answers.
references/ — the data schema and FICTIONAL demo files, invented to show the machine, not real.
MY-LEDGER.md — your own record of what you asked and what you decided.
START-HERE.md, system/short-prompt.md, system/rules.md — the doors, for any AI with or without skills.
card.svg, card.json, card.html, AUDIT.md, MANIFEST.md, WITNESS.md, SELFTEST.md — the faces and the proof.
NOT IN THE BOX — any studio edition (planned, not yet on sale: the studio's own roads for its builds). Also not in the box: any data you must bring, and advice of any kind (not a promise of delivery).

PROOF · SELFTEST 14/14 · WITNESSED IN CLAUDE 2026-10-14 ON FICTIONAL FIXTURES · THE 9 TEST PROMPTS ASKED IN A FRESH CHAT HOLDING ONLY THE CARD · 9/9 · EDITION 2 · PUNCH 56EC7FB790E411EE8957CB9A

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

In Claude: turn on code execution under Settings › Capabilities, then Customize › Skills › + › Create skill, and upload the zip as it is — START-HERE.md in the box walks you through it, and tells you how to keep the ledger. In ChatGPT, Gemini and the rest: a Project, a GPT or a Gem with the card’s files attached and the short door in the box pasted as its instructions. The words run anywhere an AI reads Markdown; the machines run wherever the host runs Python. Witnessed in Claude only. The host marks →

Take it.

Nº 437 — 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 medical, legal, tax or financial advice, never the person’s boss, and not a licence to practise. The terms →

ONE PAYMENT · NOTHING RENEWS ITSELF

OFFLINE · ONE LICENCE · PUNCH-CHECKABLE · THE STANDARD

One payment. The file is yours to keep and keeps working at its edition; new editions issued in the year after you buy reach you by email as replacement files. Tax is added at checkout where it applies. Nothing auto-renews.

A TERM, NOT A SUBSCRIPTION: NOTHING RENEWS ITSELF AND NOBODY IS CHARGED AGAIN. WHEN A TERM ENDS THE FILES STAY ON YOUR COMPUTER AND STAY READABLE — FREEZE, NOT LOSS.

THE MACHINE · IN THE OPEN · FROM THE CARD’S OWN SELFTEST.MD

road.py, every command showing its working.

A small Python program, standard library only. Your AI runs it; you can too. The block below is pasted from the card’s own SELFTEST.md, as printed when it was run from inside the packet.

`check`	CYCLE with the loop, OUT OF ORDER with both days, NO OWNER, DONE WITHOUT A DAY (never counted done); exit 1 on CYCLE or DONE WITHOUT A DAY, the others named for a person
`path`	the critical path: the longest chain in days from the earliest due day through the dependencies to the latest, each hop with its days, and the slack of every other milestone; refused on CYCLE or OUT OF ORDER (exit 1)
`board`	every milestone LATE (days late, what it drags), AT RISK (due inside warning_days), ON TRACK or DONE, in that order; the slips listed; a done row with no day is DONE WITHOUT A DAY, not DONE
`shift`	a new sheet with X and everything downstream of it moved N days (a done milestone is not moved); NEVER IN PLACE when --out is the input, ALREADY DONE when X is done (each exit 1); UNKNOWN ID exit 2
`selftest`	14 checks that prove the machine; it must print selftest 14/14

THE SELFTEST, AS PRINTED

ok   1  check on a clean sheet: every row listed with its owner and due day, no flags, 2 done (2 proven with a day), exit 0
ok   2  check names NO OWNER and OUT OF ORDER (both days printed) for a person, and they alone do not stop the road
ok   3  check never counts done without a day: m9 is DONE WITHOUT A DAY, 3 done (2 proven with a day), exit 1
ok   4  check lists a CYCLE as the loop in order and exits 1
ok   5  an unknown dependency, a status outside todo|doing|done, a malformed due day and a duplicate id are bad input (exit 2)
ok   6  path: the critical path is the longest chain in days from the earliest due day, each hop with its days, 73 days in all
ok   7  path prints the slack of every other milestone with the day it may slip to and its dependents
ok   8  path refuses on CYCLE and on OUT OF ORDER (exit 1) and prints no chain
ok   9  board: LATE with days late and what it drags, AT RISK inside the warning window, ON TRACK, DONE with the day (and days after its day), from --today
ok   10  board never omits a late milestone and never counts done without a day: m3, m4, m5 all LATE and on the SLIPS line, most late first; m9 is DONE WITHOUT A DAY apart from DONE; NO OWNER printed in the owner column
ok   11  the warning window is the rule's: at 40 days m7 is AT RISK; a rule without warning_days is bad input (exit 2)
ok   12  shift moves the milestone and everything downstream by N days into a new sheet, leaves upstream and done rows alone, keeps the # line and the columns, and leaves the input byte for byte as it was
ok   13  shift refuses NEVER IN PLACE when --out is the input sheet, however spelled (exit 1), and the sheet is untouched
ok   14  shift refuses a done milestone as ALREADY DONE and a looped sheet as CYCLE (exit 1); an id not on the sheet is UNKNOWN ID (exit 2)
selftest 14/14

THE RUN IS PASTED FROM THE CARD’S OWN SELFTEST.MD AS PRINTED. ITS FIXTURES ARE FICTIONAL, INVENTED FOR THE TEST; NO PRIVATE PERSON IS NAMED.

QUESTIONS AT THE TABLE

Asked before the wire.

What does it need from me?

The milestones, with owners and dates. What each depends on. The house's warning window, in days. If something it needs is missing, it says what is missing and stops there.

Does it send anything anywhere?

No. The machine is a standard-library Python program that runs on your own computer and sends nothing anywhere; the words run wherever an AI reads Markdown. No server, no account, no key.

What is on the record?

The machine's selftest (14/14), run from inside the packet in Claude on 2026-10-14 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: Any run on real data. Every demo file is fictional. The punch on the face is the SHA-256 of SKILL.md, so a downloaded copy can be checked against this room.

Can it be wrong?

Yes — it is an AI reading a text file: it can be wrong and can invent a number, a rule, a name or a date; check what matters against your own records and the source; the risk is yours. LICENSE-NOTE.md rides in the packet and is the licence. It is not a promise of delivery.

What will it never do?

It never marks a milestone done without a day; never hides a slip from the board; never shifts the file in place; never claims a certainty it does not have.

← THE METHODS · THE FLOOR →