THE SCOPE CARD · the statement of work, kept honest
WAKES WHEN an engagement is scoped, a statement of work is signed, or the client asks for more
THE LOOP
sow · the skeleton, a slot for every part
fill it with the client
check · acceptance, dates, open words
sign; then change for every new ask
out of scope: a change order first
NEVER
Sign a deliverable with no acceptance
Leave an open-ended word in the scope
Start out-of-scope work unagreed
IT MAKES sow — the skeleton, every slot marked; check — sections, acceptance, dates, open-ended words, empty slots; change — a request logged IN or OUT OF SCOPE; the log and its days.
THE STANDARD every deliverable has acceptance and a date; out of scope is written down; no open-ended words; every change is logged; both sides are protected; the signed paper governs.
PROOF SELFTEST 8/8 · 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 · 4B2F4631E856251D55F37816
CITE THIS CARDTHE SCOPE CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=scope-card. Punch 4B2F4631E856251D55F37816. Retrieved 2026-10-10.
What it is.
Keeps an engagement's scope honest on both sides: sow writes the statement of work with a slot for every part — the objective, each deliverable with its acceptance and its date, what is out of scope, the assumptions, the client's responsibilities, the timeline and the change process; check reads a statement for missing sections, deliverables with no acceptance or no date, open-ended words that let scope run (as needed, ongoing, including but not limited to, etc.) and slots left empty; change logs each request against the deliverables as IN SCOPE (with the deliverable) or OUT OF SCOPE, needing a change order, and counts the days asked for each way.
It carries a machine that shows its working: sow — the skeleton, every slot marked; check — sections, acceptance, dates, open-ended words, empty slots; change — a request logged IN or OUT OF SCOPE; the log and its days — 8 checks in its selftest, every command on the record. It will never sign a deliverable with no acceptance; never leave an open-ended word in the scope; never start out-of-scope work unagreed.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
EVERY DELIVERABLE HAS ACCEPTANCE AND A DATEHow both sides will know it is done, and when; a deliverable with neither is named.
OUT OF SCOPE IS WRITTEN DOWNWhat the engagement will not do is named in its own section, so no one assumes it.
NO OPEN-ENDED WORDSAs needed, ongoing, any and all, including but not limited to — each is named with its line.
EVERY CHANGE IS LOGGEDA request matched to a deliverable is in scope; one that matches none needs a change order before work begins.
BOTH SIDES ARE PROTECTEDA clear scope keeps the client from paying for what they did not get, and the team from giving what was not agreed.
THE SIGNED PAPER GOVERNSThe card drafts and reads; the signed statement of work is the contract. Not legal advice.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-CONSULTANCY.md
THE MACHINEscope.py · three commandssow — the skeleton, every slot marked; check — sections, acceptance, dates, open-ended words, empty slots; change — a request logged IN or OUT OF SCOPE; the log and its days. Every command prints its working and refuses a bad input; 8 checks in its selftest, every command on the record.
change A request logged IN or OUT OF SCOPE; the log and its days
On the record The statement of work written with every slot marked; checked, it named three deliverables with no acceptance and no date and every empty slot; filled, it named the one open-ended phrase left in; two requests logged — one in scope under the training deliverable, one out of scope needing a change order — and the log counted the days.
What it will never do.
It will never sign a deliverable with no acceptance; never leave an open-ended word in the scope; never start out-of-scope work unagreed.
A request is matched to a deliverable by the words they share; a request in other words can read OUT OF SCOPE when it is in, or the reverse — the people who signed decide. The open-ended list is the common phrases; others slip past. Not legal advice; a statement of work is a contract document, and the signed one governs. 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-CONSULTANCY.md — the guide in references/, in the card's own voice
scripts/scope.py — the machine: sow · check · change, standard library only, selftest 8/8
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 8/8 · 3 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH 4B2F4631E856251D55F37816
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º 1101 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
scope.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.
a request logged IN or OUT OF SCOPE; the log and its days
selftest
8 checks that prove the machine; it must print 8/8
sow · THE SKELETON, EVERY SLOT MARKED
$ python3 scripts/scope.py sow --client Northfield Bakery Group --objective Cut waste at three bakeries by planning the bake from pre-orders. --deliverables Waste baseline report;Pre-order bake plan;Staff training on the plan --weeks 6 --out SOW.md
written: SOW.md · 3 deliverables · 10 slots to fill
$ python3 scripts/scope.py check SOW.md
DELIVERABLE D1 · Waste baseline report · no acceptance
DELIVERABLE D1 · Waste baseline report · no date
DELIVERABLE D2 · Pre-order bake plan · no acceptance
DELIVERABLE D2 · Pre-order bake plan · no date
DELIVERABLE D3 · Staff training on the plan · no acceptance
DELIVERABLE D3 · Staff training on the plan · no date
SLOT line 8 · ⟨how both sides will know it is done⟩
SLOT line 9 · ⟨week or date⟩
SLOT line 12 · ⟨how both sides will know it is done⟩
SLOT line 13 · ⟨week or date⟩
SLOT line 16 · ⟨how both sides will know it is done⟩
SLOT line 17 · ⟨week or date⟩
SLOT line 20 · ⟨what this engagement will not do, named⟩
SLOT line 23 · ⟨what is taken as true, and what happens if it is not⟩
SLOT line 26 · ⟨access, people, data and decisions the client provides, and by when⟩
SLOT line 29 · ⟨date⟩
16 findings · mend before it is signed
(the statement filled in with the client — and one loose line left in)
$ (the statement filled in with the client — and one loose line left in)
$ python3 scripts/scope.py check SOW.md
OPEN-ENDED line 34 · "as needed" — Support as needed for the bakeries.
1 finding · mend before it is signed
change · A REQUEST LOGGED IN OR OUT OF SCOPE; THE LOG AND ITS DAYS
$ python3 scripts/scope.py change changes.jsonl --sow SOW.md --request one more training session for the night staff on the plan --days 1 --by head baker --date 2026-10-21
IN SCOPE · one more training session for the night staff on the plan · under D3 · Staff training on the plan · 1 day · logged
change · A REQUEST LOGGED IN OR OUT OF SCOPE; THE LOG AND ITS DAYS
$ python3 scripts/scope.py change changes.jsonl --sow SOW.md --request build a loyalty app --days 8 --by operations lead --date 2026-10-22
OUT OF SCOPE · build a loyalty app · a change order is needed before work begins · 8 days · logged
change · A REQUEST LOGGED IN OR OUT OF SCOPE; THE LOG AND ITS DAYS
$ python3 scripts/scope.py change changes.jsonl --sow SOW.md
2026-10-21 IN SCOPE 1 d · one more training session for the night staff on the plan · asked by head baker
2026-10-22 OUT OF SCOPE 8 d · build a loyalty app · asked by operations lead
2 requests · 1 day in scope · 8 days out of scope — a change order is needed before that work begins
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?
Sow · the skeleton, a slot for every part. It asks first for the client, the objective and the deliverables; later, each new request as it is made.
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 (8/8) 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. A request is matched to a deliverable by the words they share; a request in other words can read OUT OF SCOPE when it is in, or the reverse — the people who signed decide. The open-ended list is the common phrases; others slip past. Not legal advice; a statement of work is a contract document, and the signed one governs.
What will it never do?
It will never sign a deliverable with no acceptance; never leave an open-ended word in the scope; never start out-of-scope work unagreed.
