THE METHODS · THE CARD BENCH · Nº 433 · EDITION 2 · LAUNCHING SOON

LUND CARDS · THE METHODSNº 433

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE EDITION CARD · The version seat: editions numbered, punched and compared; a new one only when something moved.

WAKES WHEN A card was re-cut and needs its edition number and note. · Two zips of the same card exist and nobody knows what differs. · A buyer asks which edition they hold. · Someone wants to cut 'edition 3' with nothing changed.

THE LOOP

Punch each packet from its door
Compare: added, changed, removed, same
Write the note: number, date, what moved
Verify a packet against the punch it claims

NEVER

Never cuts an edition of nothing
Never writes an edition note with nothing said
Never deletes an older edition
Never claims a certainty it does not have

IT MAKES punch — print the packet's punch: the first 96 bits of SHA-256 of its door file, as 24 hex characters; compare — file-by-file: ADDED, CHANGED, REMOVED, SAME; NO CHANGE when the two are identical (exit 1); note — write the edition note; refused when nothing changed or --what is empty; verify — is this packet the edition the punch names? MATCH or NOT THIS EDITION; list — print every packet (folder or .skill.zip) in DIR with its punch and its edition line if the door has one.

THE LAW An edition is a number, a date, a note of what moved and a punch that proves which one a person holds. Editions replace files; they do not erase them. An edition with nothing changed is not an edition, and one with nothing said about it is not finished.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/edition.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (9 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 13/13 · witnessed in Claude 2026-10-14 on fictional fixtures · the test prompts in fresh chat, 9/9 · Edition 2.

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. LICENSE-NOTE.md rides in the packet and is the licence.

THE PUNCH · SHA-256 OF SKILL.MD · A9ECBD5C755FD9B4DC463D3A

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

THE EDITION CARD

The version seat: editions numbered, punched and compared; a new one only when something moved.

PUNCH · COMPARE · NOTE · VERIFY · LIST

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: 98 of 100 · LEGENDARY · WITNESSED
EDITION: E1 · witnessed 2026-10-14
MACHINE: scripts/edition.py · 5 commands · selftest 13/13
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: A9ECBD5C755FD9B4DC463D3A · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE EDITION CARD, Edition 2. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=edition-card. Punch A9ECBD5C755FD9B4DC463D3A. Retrieved 2026-10-14.

What it is.

Use when a packet replaces an earlier one: the punch of each, the file-by-file difference, the edition note, and proof of which edition a person holds. Not for packing the zip or witnessing the runs.

It carries a machine that shows its working: punch — print the packet's punch: the first 96 bits of SHA-256 of its door file, as 24 hex characters; compare — file-by-file: ADDED, CHANGED, REMOVED, SAME; NO CHANGE when the two are identical (exit 1); note — write the edition note; refused when nothing changed or --what is empty; verify — is this packet the edition the punch names? MATCH or NOT THIS EDITION; list — print every packet (folder or .skill.zip) in DIR with its punch and its edition line if the door has one — 13 checks in its selftest. It never cuts an edition of nothing; never writes an edition note with nothing said; never deletes an older edition; never claims a certainty it does not have.

The law, written into the card.

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

THE LAWAn edition is a number, a date, a note of what moved and a punch that proves which one a person holds. Editions replace files; they do not erase them. An edition with nothing changed is not an edition, and one with nothing said about it is not finished.

The method.

Punch the packet: the first 96 bits of the hash of its door file, as 24 hex characters, is its name in the register.
Compare the old and the new file by file: ADDED, CHANGED, REMOVED, SAME; two identical packets are NO CHANGE and no edition is cut.
Write the edition note: the number, the date, what moved in plain words, both punches, the file lists. An empty 'what moved' is refused.
Verify any packet against the punch it claims: MATCH or NOT THIS EDITION.
Keep the older edition; the note is how a holder of either one knows where they stand.

What you bring.

The old packet and the new one, as folders or zips.
What moved, in your own words.
The number the new edition takes.

Planned as a separate seat, not in this box and not yet on sale: the edition notes the studio writes at every re-cut.

What it does once your AI has it.

punch Print the packet's punch: the first 96 bits of SHA-256 of its door file, as 24 hex characters
compare File-by-file: ADDED, CHANGED, REMOVED, SAME; NO CHANGE when the two are identical (exit 1)
note Write the edition note; refused when nothing changed or --what is empty
verify Is this packet the edition the punch names? MATCH or NOT THIS EDITION
list Print every packet (folder or .skill.zip) in DIR with its punch and its edition line if the door has one

What it will never do.

It never cuts an edition of nothing; never writes an edition note with nothing said; never deletes an older edition; never claims a certainty it does not have.

Where it hands off: Packing the new edition for the shelf → THE PACKAGE CARD; Witnessing the runs on the new edition → THE WITNESS CARD; Checking the new tin against the new box → THE TIN CARD.

It is not a licence record. 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/edition.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
tests/EVALS.json and scripts/evals.py — 9 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 edition notes the studio writes at every re-cut). Also not in the box: any data you must bring, and advice of any kind (not a licence record).

PROOF · SELFTEST 13/13 · WITNESSED IN CLAUDE 2026-10-14 ON FICTIONAL FIXTURES · THE 9 TEST PROMPTS ASKED IN A FRESH CHAT HOLDING ONLY THE CARD · 9/9 · EDITION 2 · PUNCH A9ECBD5C755FD9B4DC463D3A

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

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

`punch`	print the packet's punch: the first 96 bits of SHA-256 of its door file, as 24 hex characters
`compare`	file-by-file: ADDED, CHANGED, REMOVED, SAME; NO CHANGE when the two are identical (exit 1)
`note`	write the edition note; refused when nothing changed or --what is empty
`verify`	is this packet the edition the punch names? MATCH or NOT THIS EDITION
`list`	print every packet (folder or .skill.zip) in DIR with its punch and its edition line if the door has one
`selftest`	13 checks that prove the machine; it must print selftest 13/13

THE SELFTEST, AS PRINTED

ADDED    NEW.md
CHANGED  SKILL.md
CHANGED  scripts/m.py
REMOVED  OLD.md
compare <tmp> · 1 added · 2 changed · 1 removed · 1 same
NO CHANGE: the two packets are identical file for file; a new edition of nothing is refused
note <tmp> · edition 2 · 1 added · 2 changed · 1 removed
NO NOTE: an edition with nothing said about what moved is refused
NO CHANGE: nothing moved between the two packets; an edition is refused
verify <tmp> · MATCH · this is the edition punched 289642EEF710BE6172CE9050
verify <tmp> · NOT THIS EDITION · the packet punches 289642EEF710BE6172CE9050, not 6511DD1C4C564ABD717195A6
card-e1                              6511DD1C4C564ABD717195A6  E1
card-e2                              289642EEF710BE6172CE9050  E2
card-e2.skill.zip                    289642EEF710BE6172CE9050  E2
nodoor                               NO DOOR: the packet has no SKILL.md to punch
list <tmp> · 4 packets
ok   1  punch is 24 hex characters of the door's hash and moves when the door moves
ok   2  the edition line is read from the door
ok   3  compare names ADDED, CHANGED, REMOVED and SAME file by file
ok   4  a zipped packet punches the same as its folder
ok   5  compare writes the difference and exits 0 when something moved
ok   6  two identical packets are NO CHANGE: exit 1
ok   7  note writes the edition note with both punches and what moved
ok   8  an edition note with nothing said is NO NOTE: refused
ok   9  an edition of an unchanged packet is NO CHANGE: refused
ok   10  verify says MATCH for the right punch
ok   11  verify says NOT THIS EDITION for another edition's punch
ok   12  a packet with no door is NO DOOR
ok   13  list prints every packet with its punch
selftest 13/13

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?

The old packet and the new one, as folders or zips. What moved, in your own words. The number the new edition takes. 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 (13/13), run from inside the packet in Claude on 2026-10-14 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: 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 a licence record.

What will it never do?

It never cuts an edition of nothing; never writes an edition note with nothing said; never deletes an older edition; never claims a certainty it does not have.

← THE METHODS · THE FLOOR →