THE PROVENANCE CARD · a record and a plain line on every AI output
WAKES WHEN AI-made work goes out under a name, or someone asks what was made with an AI, and from what
THE LOOP
stamp <file> --model --by · the record
disclose · the reader's line, the meta
publish with the line on it
verify · MATCH, or CHANGED since
ledger · every output recorded?
NEVER
Publish AI-made work as if no AI touched it
Call a plain record a signed credential
Stamp a file it has not hashed
IT MAKES stamp — the record, beside the file; disclose — the reader's line and the meta tags; verify — MATCH or CHANGED; ledger — every output: RECORDED, CHANGED or NO RECORD.
THE STANDARD said plainly; the record is the file's; changed is named; the ledger misses nothing; sources are named; a record, not a credential.
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 · F937EA266CA66E620BA2BBEF
CITE THIS CARDTHE PROVENANCE CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=provenance-card. Punch F937EA266CA66E620BA2BBEF. Retrieved 2026-10-10.
What it is.
Gives every AI-made output a record and a plain line for its reader: stamp writes a content record beside a file — its SHA-256 and size, the day it was made, the model, who directed it, whether a person edited it after, and the sources it drew on; disclose turns the record into the line a reader sees (made with an AI, directed by…, edited by a person, drawn from…) and the meta tags a page carries; verify says whether the file is still the one its record describes; ledger reads a folder and names every output with no record or a record that no longer matches.
It carries a machine that shows its working: stamp — the record, beside the file; disclose — the reader's line and the meta tags; verify — MATCH or CHANGED; ledger — every output: RECORDED, CHANGED or NO RECORD — 8 checks in its selftest, every command on the record. It will never publish AI-made work as if no AI touched it; never call a plain record a signed credential; never stamp a file it has not hashed.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
SAID PLAINLYEvery AI-made output carries a line a reader understands: made with an AI, by whose direction, edited or not, drawn from what.
THE RECORD IS THE FILE'SIts SHA-256 and size are in the record, so the record describes one file and no other.
CHANGED IS NAMEDA file edited after its record reads CHANGED; it is stamped again, not passed.
THE LEDGER MISSES NOTHINGEvery output in a folder is RECORDED, CHANGED or NO RECORD.
SOURCES ARE NAMEDWhat the output drew on is listed where it can be; a source that cannot be named is said to be unnamed.
A RECORD, NOT A CREDENTIALThe card says what was said about a file and whether it changed; it does not prove who wrote the record.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-HORIZON.md
THE MACHINEprovenance.py · four commandsstamp — the record, beside the file; disclose — the reader's line and the meta tags; verify — MATCH or CHANGED; ledger — every output: RECORDED, CHANGED or NO RECORD. Every command prints its working and refuses a bad input; 8 checks in its selftest, every command on the record.
What it does once your AI has it.
stamp The record, beside the file
disclose The reader's line and the meta tags
verify MATCH or CHANGED
ledger Every output: RECORDED, CHANGED or NO RECORD
On the record A post stamped with its hash, model, director, sources and the fact a person edited it; the reader's line and the meta tags written from the record; verified MATCH, then CHANGED once a line was added; the ledger named the changed post and the menu with no record.
What it will never do.
It will never publish AI-made work as if no AI touched it; never call a plain record a signed credential; never stamp a file it has not hashed.
The record is plain JSON beside the file, not a cryptographic signature or a content-credential standard; anyone can write one, so it is honesty made easy, not proof. Where a platform or a law asks for a particular disclosure, its wording governs. Not legal advice. 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-HORIZON.md — the guide in references/, in the card's own voice
scripts/provenance.py — the machine: stamp · disclose · verify · ledger, 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 · 4 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH F937EA266CA66E620BA2BBEF
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º 1110 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
provenance.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.
stamp
the record, beside the file
disclose
the reader's line and the meta tags
verify
MATCH or CHANGED
ledger
every output: RECORDED, CHANGED or NO RECORD
selftest
8 checks that prove the machine; it must print 8/8
(two AI-drafted pages)
$ (two AI-drafted pages)
stamp · THE RECORD, BESIDE THE FILE
$ python3 scripts/provenance.py stamp out/post.md --model model-x --by the head baker --sources our bake log;the night team --edited yes --date 2026-10-10
recorded: post.md.prov.json · sha-256 8c6fb52bc0ae3e4e… · 80 bytes
Made with an AI (model-x), directed by the head baker and edited by a person, 2026-10-10. Drawn from: our bake log; the night team.
disclose · THE READER'S LINE AND THE META TAGS
$ python3 scripts/provenance.py disclose out/post.md.prov.json
Made with an AI (model-x), directed by the head baker and edited by a person, 2026-10-10. Drawn from: our bake log; the night team.
<meta name="ai-generated" content="true">
<meta name="ai-model" content="model-x">
<meta name="content-sha256" content="8c6fb52bc0ae3e4e4eaa3a7793a520e043b8827fc108652d1e0fd861abd46715">
<meta name="content-made" content="2026-10-10">
<meta name="ai-disclosure" content="Made with an AI (model-x), directed by the head baker and edited by a person, 2026-10-10. Drawn from: our bake log; the night team.">
verify · MATCH OR CHANGED
$ python3 scripts/provenance.py verify out/post.md
MATCH · post.md against its record of 2026-10-10
(a line added to the post after it was stamped)
$ (a line added to the post after it was stamped)
verify · MATCH OR CHANGED
$ python3 scripts/provenance.py verify out/post.md
CHANGED · post.md against its record of 2026-10-10
ledger · EVERY OUTPUT: RECORDED, CHANGED OR NO RECORD
$ python3 scripts/provenance.py ledger out
NO RECORD menu.md
CHANGED post.md
2 outputs · 0 recorded and unchanged · 2 to stamp or re-stamp
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?
Stamp <file> --model --by · the record. It asks first for the file, the model, who directed it, whether a person edited it, and the sources.
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. The record is plain JSON beside the file, not a cryptographic signature or a content-credential standard; anyone can write one, so it is honesty made easy, not proof. Where a platform or a law asks for a particular disclosure, its wording governs. Not legal advice.
What will it never do?
It will never publish AI-made work as if no AI touched it; never call a plain record a signed credential; never stamp a file it has not hashed.
