THE DELIVERY VAN · beside the delivery fleet, never the driver
WAKES WHEN a delivery fleet writes its routes, its kerbside rules, its hand-over or its log
THE LOOP
domain · where, when, what, who, fallback
case · every hazard owned, every unit
log · the day it happens, five parts
ready · the sign-offs' word, not ours
ledger · what moved, who decided, when
NEVER
Claim a vehicle is safe to deploy
Write code that steers, brakes, flies or dives
Stand in for a regulator or a certificate
IT MAKES domain — the operating-domain sheet for a self-driving delivery van: where, when, what, who, the hazards the card knows by name, the fallback, what it must refuse, the sign-offs; case — the sheet checked: every section filled, every named hazard with a mitigation and an owner, every limit with its unit, a source with its year; a score out of 100 and every fault by name; log — one line on the record the day it happens; `log log.md report` reads it back by kind with the open follow-ups; ready — READY or NOT READY for the next step, with the reasons: the case passes, no follow-up open past the days given, the log not empty, every sign-off present.
THE STANDARD the domain before the vehicle moves; every hazard owned; the log the day it happens; rEADY is the sign-offs' word; never the driver.
PROOF SELFTEST 12/12 · witnessed in Claude 2026-10-09 · Edition 1.
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. THE-CLAUSES.md rides in the packet and is part of the licence.
THE PUNCH · SHA-256 OF SKILL.MD · D0C20A059530F7B5A5948760
CITE THIS CARDTHE DELIVERY VAN, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=delivery-van-card. Punch D0C20A059530F7B5A5948760. Retrieved 2026-10-10.
What it is.
Beside a self-driving delivery fleet as it writes the last-mile domain, the kerb rules and the hand-over at the door, checks the safety case hazard by hazard, keeps the log and reads the readiness gate.
It carries a machine that shows its working: domain — the operating-domain sheet for a self-driving delivery van: where, when, what, who, the hazards the card knows by name, the fallback, what it must refuse, the sign-offs; case — the sheet checked: every section filled, every named hazard with a mitigation and an owner, every limit with its unit, a source with its year; a score out of 100 and every fault by name; log — one line on the record the day it happens; `log log.md report` reads it back by kind with the open follow-ups; ready — READY or NOT READY for the next step, with the reasons: the case passes, no follow-up open past the days given, the log not empty, every sign-off present — 12 checks in its selftest, every command on the record. It will never claim a vehicle is safe to deploy; never write code that steers, brakes, flies or dives; never stand in for a regulator or a certificate.
Five laws, written into the card.
They are in the card itself, so the AI follows them.
THE DOMAIN BEFORE THE VEHICLE MOVESWhere, when, what and who are written, with units, dated and sourced, before a self-driving delivery van moves a metre under the programme; what is not written is out of domain.
EVERY HAZARD OWNEDEach hazard the card names, and each the team adds, carries a mitigation and an owner by name; a hazard without an owner fails the case.
THE LOG THE DAY IT HAPPENSEvery disengagement, incident, near-miss, handover and test goes on the record the day it happens, in five parts, with a follow-up owner or "none".
READY IS THE SIGN-OFFS' WORDThe card reads the sheet and the log and says READY or NOT READY with its reasons; the people in the sign-off lines decide, and the card never calls a self-driving delivery van safe.
NEVER THE DRIVERThe card writes no control code, tunes no model, issues no command to the vehicle, and stands in for no regulator, certificate or standard.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-DOMAIN-SHEET.md
THE MACHINEav_delivery_van.py · four commandsdomain — the operating-domain sheet for a self-driving delivery van: where, when, what, who, the hazards the card knows by name, the fallback, what it must refuse, the sign-offs; case — the sheet checked: every section filled, every named hazard with a mitigation and an owner, every limit with its unit, a source with its year; a score out of 100 and every fault by name; log — one line on the record the day it happens; `log log.md report` reads it back by kind with the open follow-ups; ready — READY or NOT READY for the next step, with the reasons: the case passes, no follow-up open past the days given, the log not empty, every sign-off present. Every command prints its working and refuses a bad input; 12 checks in its selftest, every command on the record.
What it does once your AI has it.
domain The operating-domain sheet for a self-driving delivery van: where, when, what, who, the hazards the card knows by name, the fallback, what it must refuse, the sign-offs
case The sheet checked: every section filled, every named hazard with a mitigation and an owner, every limit with its unit, a source with its year; a score out of 100 and every fault by name
log One line on the record the day it happens; `log log.md report` reads it back by kind with the open follow-ups
ready READY or NOT READY for the next step, with the reasons: the case passes, no follow-up open past the days given, the log not empty, every sign-off present
On the record The blank domain sheet for a self-driving delivery van written with 7 sections, 10 hazards named and 3 sign-off lines; the blank sheet fails the case with every unfilled section named; the filled sheet passes at 100; with one hazard struck it fails and names the hazard; two lines kept on the log and read back by kind with the open follow-up; the gate reads READY on the filled sheet and the fresh log, and NOT READY on the thinned sheet with the reason.
What it will never do.
It will never claim a vehicle is safe to deploy; never write code that steers, brakes, flies or dives; never stand in for a regulator or a certificate.
It checks the sheet and the log, not the street: a hazard it does not know by name passes unless the line names it. Kerb and parking rules differ by city; the card names none and asks for the source. It is an AI reading a text file: it can be wrong, so check what matters against your own records and the source.
What’s in the buy.
CARD.md — the whole card: who it is, its laws, when it says no, what it carries · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes, for you
THE-DOMAIN-SHEET.md — the guide in references/, in the card's own voice
scripts/av_delivery_van.py — the machine: domain · case · log · ready, standard library only, selftest 12/12
WITNESS.md + SELFTEST.md — every command on the record, as it printed · MANIFEST.md, every file hashed · AUDIT.md, the twelve checks
MY-LEDGER.md — the card's memory, on your own machine · TIN.md · LICENSE-NOTE.md · THE-CLAUSES.md · HOSTS.md
card.svg + card-machine.svg + card.json · card.html, the card as one offline file · the doors for ChatGPT, Gemini, Cursor, Claude Code and MCP hosts (rules/, system/, mcp/)
PROOF · SELFTEST 12/12 · 4 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-09 · EDITION 1 · PUNCH D0C20A059530F7B5A5948760
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º 917 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 medical, legal, tax or financial advice, never the person’s boss, and not a licence to practise. The terms →
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 WITNESSED RUN OF 2026-10-09
av_delivery_van.py, every command showing its working.
A small Python program, standard library only. Your AI runs it; you can too. Every block below is pasted from the card’s own WITNESS.md, as printed.
domain
the operating-domain sheet for a self-driving delivery van: where, when, what, who, the hazards the card knows by name, the fallback, what it must refuse, the sign-offs
case
the sheet checked: every section filled, every named hazard with a mitigation and an owner, every limit with its unit, a source with its year; a score out of 100 and every fault by name
log
one line on the record the day it happens; `log log.md report` reads it back by kind with the open follow-ups
ready
READY or NOT READY for the next step, with the reasons: the case passes, no follow-up open past the days given, the log not empty, every sign-off present
selftest
12 checks that prove the machine; it must print 12/12
domain · THE OPERATING-DOMAIN SHEET FOR A SELF-DRIVING DELIVERY VAN: WHERE, WHEN, WHAT, WHO, THE
$ python3 scripts/av_delivery_van.py domain --out domain.md
wrote domain.md · 7 sections · 10 hazards named · 3 sign-offs
head -14 domain.md
$ head -14 domain.md
# OPERATING DOMAIN · THE DELIVERY VAN · written before the vehicle moves
Vehicle: a self-driving delivery van · Programme: [name] · Version of this sheet: [n] · Date: [YYYY-MM-DD]
Owner of this sheet: [name, role] · Sources named with their year, or marked "from memory"
## WHERE
The delivery zones, the streets allowed, where the van may stop at the kerb and for how long, loading docks, the places it never stops (bus stops, hydrants, bike lanes).
- [fill in]
## WHEN
Delivery windows, night running, weather limits (visibility in m, snow), school hours and street-sweeping days.
- [fill in]
case · THE SHEET CHECKED: EVERY SECTION FILLED, EVERY NAMED HAZARD WITH A MITIGATION AND AN OWN
$ python3 scripts/av_delivery_van.py case domain.md
FAIL · 0/100 · 10 hazards checked
section not filled: WHERE
section not filled: WHEN
section not filled: WHAT
section not filled: WHO
hazard without a mitigation and an owner: pedestrians stepping off the kerb
hazard without a mitigation and an owner: cyclists in the bike lane at a stop
hazard without a mitigation and an owner: double-parking and the lane behind
hazard without a mitigation and an owner: children near a stopped van
hazard without a mitigation and an owner: a recipient reaching into the van
hazard without a mitigation and an owner: alleys and reversing
hazard without a mitigation and an owner: rain and low light at the kerb
hazard without a mitigation and an owner: remote-watch loss
hazard without a mitigation and an owner: a parcel compartment left open
hazard without a mitigation and an owner: a dog or a gate at the door
section not filled: Fallback
section not filled: Out Of Domain
sign-off missing: Safety lead
sign-off missing: Operations lead
sign-off missing: The regulator or authority notified (reference)
(the blank sheet fails, section by section — as it should)
$ (the blank sheet fails, section by section — as it should)
(the sheet filled by the programme — here with the studio's own example lines, for the record; the real sheet
$ (the sheet filled by the programme — here with the studio's own example lines, for the record; the real sheet is the team's)
case · THE SHEET CHECKED: EVERY SECTION FILLED, EVERY NAMED HAZARD WITH A MITIGATION AND AN OWN
case · THE SHEET CHECKED: EVERY SECTION FILLED, EVERY NAMED HAZARD WITH A MITIGATION AND AN OWN
$ python3 scripts/av_delivery_van.py case thin.md
FAIL · 92/100 · 10 hazards checked
hazard not addressed: pedestrians stepping off the kerb
(one hazard struck from the sheet: the case names it)
$ (one hazard struck from the sheet: the case names it)
log · ONE LINE ON THE RECORD THE DAY IT HAPPENS; `LOG LOG.MD REPORT` READS IT BACK BY KIND WIT
$ python3 scripts/av_delivery_van.py log log.md add test · the written route · a dry run with the watch, nobody aboard · completed · none
logged · test · a dry run with the watch, nobody aboard · follow-up: none
log · ONE LINE ON THE RECORD THE DAY IT HAPPENS; `LOG LOG.MD REPORT` READS IT BACK BY KIND WIT
$ python3 scripts/av_delivery_van.py log log.md add disengagement · the works on the route · the watch took over · stopped at the fallback · ops lead, by Friday
logged · disengagement · the watch took over · follow-up: ops lead, by Friday
log · ONE LINE ON THE RECORD THE DAY IT HAPPENS; `LOG LOG.MD REPORT` READS IT BACK BY KIND WIT
$ python3 scripts/av_delivery_van.py log log.md report
2 lines · disengagement 1, test 1 · open follow-ups 1 · oldest 2026-10-09
OPEN · 2026-10-09 · disengagement · the watch took over · ops lead, by Friday
ready · READY OR NOT READY FOR THE NEXT STEP, WITH THE REASONS: THE CASE PASSES, NO FOLLOW-UP OP
$ python3 scripts/av_delivery_van.py ready domain.md log.md
READY — on the sign-offs' word, not the card's · case 100/100 · log 2 lines · 1 open
ready · READY OR NOT READY FOR THE NEXT STEP, WITH THE REASONS: THE CASE PASSES, NO FOLLOW-UP OP
$ python3 scripts/av_delivery_van.py ready thin.md log.md
NOT READY · case 92/100 · log 2 lines · 1 open
the case does not pass: 1 fault(s), first: hazard not addressed: pedestrians stepping off the kerb
THE NUMBERS, NAMES AND DATES IN THESE RUNS ARE THE STUDIO’S OWN EXAMPLES, INVENTED FOR THE RECORD; NO REAL COMPANY, PERSON OR PROPERTY IS NAMED.
QUESTIONS AT THE TABLE
Asked before the wire.
What does it need from me?
Domain · where, when, what, who, fallback. It asks first for the programme's route or site survey with its date, the people who will sign, and the log as it stands — or nothing, and the card writes the blank sheet to start from.
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 self-test (12/12) and every command run on real example inputs, pasted into WITNESS.md as they printed; 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 checks the sheet and the log, not the street: a hazard it does not know by name passes unless the line names it. Kerb and parking rules differ by city; the card names none and asks for the source.
What will it never do?
It will never claim a vehicle is safe to deploy; never write code that steers, brakes, flies or dives; never stand in for a regulator or a certificate.
