THE HANDOFF CARD · from sold to delivered, nothing dropped
WAKES WHEN a deal closes and moves to onboarding, or a customer says "but we were told"
THE LOOP
check <handoff.md> · the eight fields
promises <notes> · numbered, to sign off
diff <promises> <plan> · what is unplanned
plan it, or tell the customer now
sign the promises off with sales
NEVER
Start onboarding on a hand-off with gaps
Let a promise go unplanned in silence
Promise for the delivery team
IT MAKES check — the eight fields: FOUND, EMPTY or MISSING; promises — every promising sentence, numbered, with its line; the sign-off list; diff — each promise PLANNED (with the plan line) or PROMISED, NOT PLANNED.
THE STANDARD eight fields before the first call; every promise is numbered; promised and not planned is named early; the plan is the delivery team's; words, not intent; roles, not contact details.
PROOF SELFTEST 7/7 · witnessed in Claude 2026-10-10 · 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 · 7DD2917215632DE44ED57313
CITE THIS CARDTHE HANDOFF CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=handoff-card. Punch 7DD2917215632DE44ED57313. Retrieved 2026-10-10.
What it is.
Carries a customer across the line between the people who sold and the people who deliver: check reads a hand-off note for the eight fields the onboarding team needs on the first day — customer, signed, bought, success, stakeholders, promises, risks, go-live — written as a line or a heading, and names each FOUND, EMPTY (blank or TBD) or MISSING; promises pulls every sentence in the sales notes that promises something (we will, included, within ten days, by Friday) with its line, and writes them as a list to sign off; diff sets those promises against the onboarding plan and names every one PROMISED, NOT PLANNED before the customer finds it.
It carries a machine that shows its working: check — the eight fields: FOUND, EMPTY or MISSING; promises — every promising sentence, numbered, with its line; the sign-off list; diff — each promise PLANNED (with the plan line) or PROMISED, NOT PLANNED — 7 checks in its selftest, every command on the record. It will never start onboarding on a hand-off with gaps; never let a promise go unplanned in silence; never promise for the delivery team.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
EIGHT FIELDS BEFORE THE FIRST CALLCustomer, signed, bought, success, stakeholders, promises, risks, go-live; a field left blank or TBD is EMPTY, not found.
EVERY PROMISE IS NUMBEREDEach sentence that promises something is pulled out with its line and signed off with the person who made it.
PROMISED AND NOT PLANNED IS NAMED EARLYBefore the kickoff, not after the customer notices; the team plans it or says plainly that it will not be done.
THE PLAN IS THE DELIVERY TEAM'SThe card sets promises beside the plan; it never promises on the team's behalf.
WORDS, NOT INTENTThe card reads what was written; what someone meant is asked, not assumed.
ROLES, NOT CONTACT DETAILSStakeholders are written by role; the card keeps no address or number.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-ONBOARDING-TEAM.md
THE MACHINEhandoff.py · three commandscheck — the eight fields: FOUND, EMPTY or MISSING; promises — every promising sentence, numbered, with its line; the sign-off list; diff — each promise PLANNED (with the plan line) or PROMISED, NOT PLANNED. Every command prints its working and refuses a bad input; 7 checks in its selftest, every command on the record.
What it does once your AI has it.
check The eight fields: FOUND, EMPTY or MISSING
promises Every promising sentence, numbered, with its line; the sign-off list
diff Each promise PLANNED (with the plan line) or PROMISED, NOT PLANNED
On the record The hand-off read: five fields found, promises and risks EMPTY, go-live MISSING; three promises pulled from the call notes and written to sign off; set against the plan, two found on their lines and the migration named PROMISED, NOT PLANNED.
What it will never do.
It will never start onboarding on a hand-off with gaps; never let a promise go unplanned in silence; never promise for the delivery team.
Promises are found by the words promises are usually made in; a promise made in other words can be missed, and a sentence can be caught that promised nothing. A promise is matched to the plan by the words they share, cut to their stems; a plan line in other words can be missed, so read every PROMISED, NOT PLANNED before acting on it. 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-ONBOARDING-TEAM.md — the guide in references/, in the card's own voice
scripts/handoff.py — the machine: check · promises · diff, standard library only, selftest 7/7
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 7/7 · 3 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH 7DD2917215632DE44ED57313
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º 1095 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-10
handoff.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.
check
the eight fields: FOUND, EMPTY or MISSING
promises
every promising sentence, numbered, with its line; the sign-off list
diff
each promise PLANNED (with the plan line) or PROMISED, NOT PLANNED
selftest
7 checks that prove the machine; it must print 7/7
(a hand-off note written by sales)
$ (a hand-off note written by sales)
check · THE EIGHT FIELDS: FOUND, EMPTY OR MISSING
$ python3 scripts/handoff.py check handoff.md
FOUND customer Northfield Bakery Group
FOUND signed 2026-10-01
FOUND bought The ordering page, three locations.
FOUND success Pre-orders on by the first Friday.
FOUND stakeholders the operations lead (sponsor); the head baker
EMPTY promises TBD
EMPTY risks
MISSING go-live
5 of 8 fields found; ask sales for: promises, risks, go-live
(the sales call notes)
$ (the sales call notes)
promises · EVERY PROMISING SENTENCE, NUMBERED, WITH ITS LINE; THE SIGN-OFF LIST
$ python3 scripts/handoff.py promises sales-notes.md --out PROMISES.md
1 · line 2 · We will migrate their old order list for them.
2 · line 3 · Training is included for all three sites.
3 · line 4 · We can have the first location live within 10 days.
3 promises to sign off
written: PROMISES.md
(the onboarding plan)
$ (the onboarding plan)
diff · EACH PROMISE PLANNED (WITH THE PLAN LINE) OR PROMISED, NOT PLANNED
$ python3 scripts/handoff.py diff PROMISES.md plan.md
PROMISED, NOT PLANNED · line 5 · We will migrate their old order list for them.
PLANNED (plan line 2) · Training is included for all three sites. ⇢ Week 2: training sessions at each site
PLANNED (plan line 1) · We can have the first location live within 10 days. ⇢ Week 1: first location live, menus loaded
3 promises · 2 in the plan · 1 not
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?
Check <handoff.md> · the eight fields. It asks first for the hand-off note, the sales notes or call notes, and the onboarding plan.
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 (7/7) 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. Promises are found by the words promises are usually made in; a promise made in other words can be missed, and a sentence can be caught that promised nothing. A promise is matched to the plan by the words they share, cut to their stems; a plan line in other words can be missed, so read every PROMISED, NOT PLANNED before acting on it.
What will it never do?
It will never start onboarding on a hand-off with gaps; never let a promise go unplanned in silence; never promise for the delivery team.
