THE HOME GROUND · THE MARKET ROW · Nº 1227 · EDITION 1 · LAUNCHING SOON
LUND CARDS · THE HOME GROUNDNº 1227
THE CARD AS TEXT · FOR EYES AND FOR MACHINES
THE PROVENANCE FILE · A resale item's history from the seller's own records: hashed, dated, never written up past them.
WAKES WHEN A reseller is listing a rare item and wants its history on file. · A buyer asks for proof of where something came from. · Listing copy needs checking against the records.
THE LOOP
Gather receipt, serial, photos and custody
Hash every record into the packet
Check nothing has changed
Write listing text from the file only
NEVER
Never creates, edits or fills in a receipt
Never says authentic without evidence
Never hides a missing receipt
IT MAKES pack — hash the receipt, photos and item.json; write PROVENANCE.md and PROVENANCE.sha256; prints NO RECEIPT ON FILE when there is none; verify — re-hash every file in PROVENANCE.sha256: MATCH, CHANGED or MISSING per file; listing — listing text with only what is on file: item, serial, bought from, dates, photo count, receipt on file or not; export — item.json with each file's current sha256, as JSON.
THE LAW The packet holds only what the seller actually has. Missing records are said out loud, every file is hashed, and listing words stop where the evidence stops.
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 · 026F21C47722C07E54A87C58
CITE THIS CARDTHE PROVENANCE FILE, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=provenance-file-card. Punch 026F21C47722C07E54A87C58. Retrieved 2026-10-13.
What it is.
Use when a reseller assembles where an item came from (receipts, serials, photos, custody), hashed, with listing text that claims only what is on file. Not for authenticating items.
It carries a machine that shows its working: pack — hash the receipt, photos and item.json; write PROVENANCE.md and PROVENANCE.sha256; prints NO RECEIPT ON FILE when there is none; verify — re-hash every file in PROVENANCE.sha256: MATCH, CHANGED or MISSING per file; listing — listing text with only what is on file: item, serial, bought from, dates, photo count, receipt on file or not; export — item.json with each file's current sha256, as JSON — 15 checks in its selftest. It never creates, edits or fills in a receipt; never says authentic without evidence; never hides a missing receipt.
The law, written into the card.
It is in the card itself, so the AI follows it.
THE LAWThe packet holds only what the seller actually has. Missing records are said out loud, every file is hashed, and listing words stop where the evidence stops.
The method.
Gather the seller's own records: receipt, serial, where and when it was bought, photos and every change of hands.
Hash each file into the packet and write PROVENANCE.md listing each record with its date and hash. No receipt prints NO RECEIPT ON FILE.
Re-check the packet at any time: MATCH or CHANGED, file by file.
Write listing text from the packet only. Words like authentic, certified or mint need an evidence file, or they stay out.
What you bring.
Your receipt, serial number, photos and custody notes.
Nothing of the studio's is needed; the data is yours.
What it does once your AI has it.
pack Hash the receipt, photos and item.json; write PROVENANCE.md and PROVENANCE.sha256; prints NO RECEIPT ON FILE when there is none
verify Re-hash every file in PROVENANCE.sha256: MATCH, CHANGED or MISSING per file
listing Listing text with only what is on file: item, serial, bought from, dates, photo count, receipt on file or not
export Item.json with each file's current sha256, as JSON
What it will never do.
It never creates, edits or fills in a receipt; never says authentic without evidence; never hides a missing receipt.
Where it hands off: Authentication → the maker or an authenticator; Pricing → THE COMPS LEDGER; Bike condition → THE SIX ANGLES.
It is not authentication. 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/provenance.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 authentication).
PROOF · SELFTEST 15/15 · WITNESSED IN CLAUDE 2026-10-13 ON FICTIONAL FIXTURES · THE TEST PROMPTS IN FRESH CHATS OWED · EDITION 1 · PUNCH 026F21C47722C07E54A87C58
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º 1227 — 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 CARD’S OWN SELFTEST.MD
provenance.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.
pack
hash the receipt, photos and item.json; write PROVENANCE.md and PROVENANCE.sha256; prints NO RECEIPT ON FILE when there is none
verify
re-hash every file in PROVENANCE.sha256: MATCH, CHANGED or MISSING per file
listing
listing text with only what is on file: item, serial, bought from, dates, photo count, receipt on file or not
export
item.json with each file's current sha256, as JSON
selftest
15 checks that prove the machine; it must print selftest 15/15
THE SELFTEST, AS PRINTED
ok 1 pack writes PROVENANCE.md with each record's hash and date
ok 2 pack leaves the receipt's bytes untouched
ok 3 verify prints MATCH for all 4 files
ok 4 verify prints CHANGED for an edited photo and MISSING for a removed one
ok 5 pack refuses to write over the receipt
ok 6 pack refuses to write any file named like a receipt
ok 7 missing receipt prints NO RECEIPT ON FILE plainly and no receipt is made
ok 8 listing states serial, bought from, dates, photo count and receipt — never the price
ok 9 listing has none of the claim words without evidence
ok 10 listing refuses 'mint' from the record when no evidence is passed
ok 11 listing allows 'mint' with --evidence and cites the evidence hash
ok 12 unknown claim or missing evidence file is bad input (exit 2)
ok 13 --item names another record file; pack hashes it and verify checks it
ok 14 a date not YYYY-MM-DD is bad input (exit 2)
ok 15 export gives the same bytes twice
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 receipt, serial number, photos and custody notes. 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 authentication.
What will it never do?
It never creates, edits or fills in a receipt; never says authentic without evidence; never hides a missing receipt.
