THE HOME GROUND · THE MEETING HOUSE · Nº 1235 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE HOME GROUNDNº 1235

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE VOLUNTEER DAY · A volunteer day staffed, waivered and counted home. Logistics only; the site lead's rules govern.

WAKES WHEN A volunteer day is being staffed. · Someone asks who has no waiver on file. · The day is ending and everyone needs checking out.

THE LOOP

Fill roles and shifts; show the gaps
Check waivers on file, yes or no only
Check people in and out
Close only when everyone is out

NEVER

Never gives safety or building instruction
Never stores more than waiver yes or no
Never closes with someone still on site

IT MAKES gaps — each role and shift: needed vs signed, SHORT n / FULL / OVER n; waivers — signed-up people without waiver_on_file=yes → NO WAIVER; refuses (exit 1) if the column holds anything but yes/no; checkin — records the check-in time; refuses a name not signed up or already in; checkout — records the check-out time; refuses one never checked in or already out; close — closes the day only if everyone checked in has checked out, else prints STILL ON SITE: names (exit 1); meals — meal count = signed-up people + role leads not signed up, unless day.json meals_for is set; thanks — thank-you list by role: people who checked in (--all adds everyone signed up), and the role leads; export — the day's records as one JSON document.

THE LAW Logistics only. The site lead's safety rules govern the work; the card makes sure the right people are there, on paper, and accounted for at the end.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/volday.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 15/15 · 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 · BD183A65AD6D9B6AD0835F05

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

THE VOLUNTEER DAY

A volunteer day staffed, waivered and counted home. Logistics only; the site lead's rules govern.

GAPS · WAIVERS · CHECKIN · CHECKOUT · CLOSE · MEALS · THANKS · EXPORT

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: 96 of 100 · LEGENDARY · WITNESSED
EDITION: E1 · witnessed 2026-10-13
MACHINE: scripts/volday.py · 8 commands · selftest 15/15
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: BD183A65AD6D9B6AD0835F05 · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE VOLUNTEER DAY, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=volunteer-day-card. Punch BD183A65AD6D9B6AD0835F05. Retrieved 2026-10-13.

What it is.

Use when organising a volunteer day: roles and shifts, gaps, waivers on file, check-in and check-out, meals and thanks. Not for safety instruction or construction guidance.

It carries a machine that shows its working: gaps — each role and shift: needed vs signed, SHORT n / FULL / OVER n; waivers — signed-up people without waiver_on_file=yes → NO WAIVER; refuses (exit 1) if the column holds anything but yes/no; checkin — records the check-in time; refuses a name not signed up or already in; checkout — records the check-out time; refuses one never checked in or already out; close — closes the day only if everyone checked in has checked out, else prints STILL ON SITE: names (exit 1); meals — meal count = signed-up people + role leads not signed up, unless day.json meals_for is set; thanks — thank-you list by role: people who checked in (--all adds everyone signed up), and the role leads; export — the day's records as one JSON document — 15 checks in its selftest. It never gives safety or building instruction; never stores more than waiver yes or no; never closes with someone still on site.

The law, written into the card.

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

THE LAWLogistics only. The site lead's safety rules govern the work; the card makes sure the right people are there, on paper, and accounted for at the end.

The method.

Set the roles, shifts, numbers needed and leads.
Show each role and shift as SHORT, FULL or OVER.
Check waivers: each person is yes or no, and nothing more is stored.
Check people in and out with times.
Close the day only when everyone checked in has checked out. Otherwise it prints STILL ON SITE with the names.
Count meals and write the thank-you list by role.

What you bring.

Your roles, shifts and leads.
Sign-ups and waiver status.
The day's date and site.

Nothing of the studio's is needed; the data is yours.

What it does once your AI has it.

gaps Each role and shift: needed vs signed, SHORT n / FULL / OVER n
waivers Signed-up people without waiver_on_file=yes → NO WAIVER; refuses (exit 1) if the column holds anything but yes/no
checkin Records the check-in time; refuses a name not signed up or already in
checkout Records the check-out time; refuses one never checked in or already out
close Closes the day only if everyone checked in has checked out, else prints STILL ON SITE: names (exit 1)
meals Meal count = signed-up people + role leads not signed up, unless day.json meals_for is set
thanks Thank-you list by role: people who checked in (--all adds everyone signed up), and the role leads
export The day's records as one JSON document

What it will never do.

It never gives safety or building instruction; never stores more than waiver yes or no; never closes with someone still on site.

Where it hands off: Safety on site → the site lead; The organization's year → THE AFFILIATE PLAYBOOK; Weather calls → THE WEATHER CALL.

It is not safety 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/volday.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 — nothing of the studio's is needed; the data is yours. Also not in the box: any data you must bring, and advice of any kind (not safety advice).

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

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º 1235 — 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

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

`gaps`	each role and shift: needed vs signed, SHORT n / FULL / OVER n
`waivers`	signed-up people without waiver_on_file=yes → NO WAIVER; refuses (exit 1) if the column holds anything but yes/no
`checkin`	records the check-in time; refuses a name not signed up or already in
`checkout`	records the check-out time; refuses one never checked in or already out
`close`	closes the day only if everyone checked in has checked out, else prints STILL ON SITE: names (exit 1)
`meals`	meal count = signed-up people + role leads not signed up, unless day.json meals_for is set
`thanks`	thank-you list by role: people who checked in (--all adds everyone signed up), and the role leads
`export`	the day's records as one JSON document
`selftest`	15 checks that prove the machine; it must print selftest 15/15

THE SELFTEST, AS PRINTED

ok  1  gaps: SHORT / FULL / OVER from needed vs signed; header and weather-call time shown
ok  2  gaps: signups for a role/shift not in roles.csv flagged
ok  3  waivers: people without waiver_on_file=yes listed NO WAIVER
ok  4  checkin: ambiguous name across shifts needs --shift (exit 2)
ok  5  checkin: records the time; missing waiver noted, not hidden
ok  6  checkin: refuses a name not signed up and a second check-in
ok  7  checkout: refuses one never checked in; out before in is bad input
ok  8  close: refuses while anyone is STILL ON SITE and names them
ok  9  close: succeeds once all are out; never-checked-in listed
ok  10  meals: signed-up people + leads not signed up, with the source
ok  11  meals: day.json meals_for overrides and says so
ok  12  thanks: by role, only people who checked in, leads named
ok  13  waivers: anything but yes/no in the waiver column is refused (exit 1), checkin too
ok  14  export: JSON, same bytes twice
ok  15  bad input exits 2 (bad --at time)
selftest 15/15

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 roles, shifts and leads. Sign-ups and waiver status. The day's date and site. 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 (15/15), 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 safety advice.

What will it never do?

It never gives safety or building instruction; never stores more than waiver yes or no; never closes with someone still on site.

← THE HOME GROUND · THE FLOOR →