THE INTRO CARD is free — what an AI skill card is and how to use one Download →Lost Lauren, contact us

THE HOME GROUND · THE TRAILHEAD · Nº 1213 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE HOME GROUNDNº 1213
THE RACE DIRECTOR — the LSC-1 face
THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE RACE DIRECTOR · An event's permits, insurance, timing and aid on a board of lead times, with late said out loud.

WAKES WHEN A director is planning an event and needs every item against its lead time. · Someone asks what is late or due this week. · Aid stations need their spacing checked along the course.

THE LOOP

  1. Start the item list; set the lead times
  2. Board the latest start date for each item
  3. Mark LATE plainly; never confirm for the agency
  4. Space the aid stations and flag the gaps

NEVER

  • Never marks a permit confirmed on its own
  • Never guesses a lead time
  • Never gives legal advice

IT MAKES init — write a starter items.csv (names and categories only, lead_days blank) and a blank event.json if missing; board — every item: days to the event, latest start, LATE, NO LEAD TIME SET (exit 1 if anything is late); aid — aid stations in km order from start to finish, gaps over the limit flagged; countdown — what must move this week: late items, items whose latest start or due date falls in the next 7 days; export — the event and every item with its computed latest start, as JSON.

THE LAW The agency's word is the only confirmation. The card holds the plan, works out what is late from lead times the director sets, and never moves an item's status by itself.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/racedirector.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (8 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-13 on fictional fixtures · the test prompts in fresh chats owed · Edition 1.

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

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 · 1620FF68F3DD543FE4B46CB7

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

THE RACE DIRECTOR

An event's permits, insurance, timing and aid on a board of lead times, with late said out loud.

INIT · BOARD · AID · COUNTDOWN · EXPORT

96LEGENDARYWITNESSEDIN CLAUDEIN LUNDRIN 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
96 of 100 · LEGENDARY · WITNESSED
EDITION
E1 · witnessed 2026-10-13
MACHINE
scripts/racedirector.py · 5 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
1620FF68F3DD543FE4B46CB7 · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE RACE DIRECTOR, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=race-director-card. Punch 1620FF68F3DD543FE4B46CB7. Retrieved 2026-10-13.

What it is.

Use when a race director tracks an event's to-dos against lead times: permits, insurance, timing, aid stations, volunteers. Not for legal advice or for confirming a permit.

It carries a machine that shows its working: init — write a starter items.csv (names and categories only, lead_days blank) and a blank event.json if missing; board — every item: days to the event, latest start, LATE, NO LEAD TIME SET (exit 1 if anything is late); aid — aid stations in km order from start to finish, gaps over the limit flagged; countdown — what must move this week: late items, items whose latest start or due date falls in the next 7 days; export — the event and every item with its computed latest start, as JSON — 14 checks in its selftest. It never marks a permit confirmed on its own; never guesses a lead time; never gives legal advice.

The law, written into the card.

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

THE LAWThe agency's word is the only confirmation. The card holds the plan, works out what is late from lead times the director sets, and never moves an item's status by itself.

The method.

  1. Start a blank item list — permits, insurance, timing, aid, medical, course, volunteers — and fill each owner and lead time from the agencies and vendors you deal with.
  2. Board every item: its latest start date is the event date minus its lead time. Past that date and not confirmed or done, it prints LATE. No lead time set prints NO LEAD TIME SET.
  3. Change an item's status yourself, in the file, when the agency or vendor gives its word. No command does it for you.
  4. Place aid stations by distance and flag any gap wider than the limit you set.
  5. Each week, print what must move this week.

What you bring.

  • Your event's date, start time and distance.
  • Each item's owner, lead time and status, from the agencies and vendors you deal with.

Planned as a separate seat, not in this box and not yet on sale: the studio's notes on local permit lead times.

What it does once your AI has it.

  • init Write a starter items.csv (names and categories only, lead_days blank) and a blank event.json if missing
  • board Every item: days to the event, latest start, LATE, NO LEAD TIME SET (exit 1 if anything is late)
  • aid Aid stations in km order from start to finish, gaps over the limit flagged
  • countdown What must move this week: late items, items whose latest start or due date falls in the next 7 days
  • export The event and every item with its computed latest start, as JSON

What it will never do.

It never marks a permit confirmed on its own; never guesses a lead time; never gives legal advice.

Where it hands off: Race-day weather calls → THE WEATHER CALL; Volunteer logistics → THE VOLUNTEER DAY; Permit terms → the agency and your counsel.

It is not legal advice. 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/racedirector.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
  • tests/EVALS.json and scripts/evals.py — 8 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 notes on local permit lead times). Also not in the box: any data you must bring, and advice of any kind (not legal advice).

PROOF · SELFTEST 14/14 · WITNESSED IN CLAUDE 2026-10-13 ON FICTIONAL FIXTURES · THE TEST PROMPTS IN FRESH CHATS OWED · EDITION 1 · PUNCH 1620FF68F3DD543FE4B46CB7

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º 1213 — 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.

One email when it is on sale, from the studio; nothing else, ever.

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

racedirector.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.

initwrite a starter items.csv (names and categories only, lead_days blank) and a blank event.json if missing
boardevery item: days to the event, latest start, LATE, NO LEAD TIME SET (exit 1 if anything is late)
aidaid stations in km order from start to finish, gaps over the limit flagged
countdownwhat must move this week: late items, items whose latest start or due date falls in the next 7 days
exportthe event and every item with its computed latest start, as JSON
selftest14 checks that prove the machine; it must print selftest 14/14
THE SELFTEST, AS PRINTED
ok  1  init writes starter items with every lead_days blank
ok  2  init refuses to overwrite an existing plan (exit 1)
ok  3  board computes latest start = event − lead_days
ok  4  board marks a past-start unconfirmed item LATE (exit 1)
ok  5  board does not mark a confirmed item late
ok  6  board prints NO LEAD TIME SET for a blank lead_days
ok  7  board says the agency's word is the only confirmation on unconfirmed permits
ok  8  no command changes a status: items.csv unchanged after board and countdown
ok  9  aid sorts stations and flags gaps over 5 km (start→4, 4→12.5, 12.5→21)
ok  10  aid lists a station with no at= as NO POSITION, never guessed
ok  11  --max-gap override clears the gap flags
ok  12  countdown lists items due or starting within 7 days and the late ones
ok  13  export is byte-identical JSON with latest_start, null when no lead time
ok  14  board rejects an event with no name or date (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?

Your event's date, start time and distance. Each item's owner, lead time and status, from the agencies and vendors you deal with. 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-13 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: The 8 test prompts asked in fresh chats with the card installed. Until they are run and scored, the tests are owed. 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 legal advice.

What will it never do?

It never marks a permit confirmed on its own; never guesses a lead time; never gives legal advice.

← THE HOME GROUND · THE FLOOR →

AT YOUR ELBOW, NEVER THE BOSS · NOT LEGAL ADVICE · NOT A PAYMENT CARD · NO REFUNDS · © 2026 LUND STUDIO LLC

PAY BYAmerican Express Apple Pay Diners ClubDiscoverGoogle Pay Mastercard PayPalShop Pay Visa
CART · 0