THE CONSENT CARD · what an AI may remember, by consent
WAKES WHEN an AI remembers things about its users, or a user asks what is kept, or to be forgotten
THE LOOP
grant · person, scope, until
check <memory> · consented, or why not
export --person · everything kept
forget --person · a clean copy, a receipt
withdraw honoured the same day
NEVER
Keep a line no consent covers
Refuse a person their export
Edit the store in place
IT MAKES grant — a consent written; withdraw — a withdrawal written; check — every line: CONSENTED, or why not; export — everything kept about one person; forget — a copy without them, and the receipt.
THE STANDARD consent is by scope; withdrawal wins; every line answers to a consent; a person can see it all; forgetting is complete, and checked; ids, not names.
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 · 13D00812837349868484C086
CITE THIS CARDTHE CONSENT CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=consent-card. Punch 13D00812837349868484C086. Retrieved 2026-10-10.
What it is.
Keeps what an AI remembers about each person to what that person agreed: grant and withdraw write consent by person and scope, with an end date, to a ledger; check reads a memory store against the ledger and names every line kept with no consent for its scope, past its end, after a withdrawal, or before consent was given; export gives one person everything kept about them; forget writes a copy of the store without them and a receipt, for the owner to put in place — the store is never edited by the card. People are kept by an id, not a name.
It carries a machine that shows its working: grant — a consent written; withdraw — a withdrawal written; check — every line: CONSENTED, or why not; export — everything kept about one person; forget — a copy without them, and the receipt — 7 checks in its selftest, every command on the record. It will never keep a line no consent covers; never refuse a person their export; never edit the store in place.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
CONSENT IS BY SCOPEPreferences, history, anything else — each agreed to on its own, with an end date if the person sets one.
WITHDRAWAL WINSA withdrawal stands from its day; what was kept under the old consent is named for removal.
EVERY LINE ANSWERS TO A CONSENTNo consent, past its end, after withdrawal, or kept before consent was given — each is named.
A PERSON CAN SEE IT ALLExport gives everything kept about them, by scope.
FORGETTING IS COMPLETE, AND CHECKEDThe copy without them is written with a receipt of what went; the owner puts it in place and confirms to the person.
IDS, NOT NAMESPeople are kept by an id; the card holds no name, address or number of anyone.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-HORIZON.md
THE MACHINEconsent.py · five commandsgrant — a consent written; withdraw — a withdrawal written; check — every line: CONSENTED, or why not; export — everything kept about one person; forget — a copy without them, and the receipt. 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.
grant A consent written
withdraw A withdrawal written
check Every line: CONSENTED, or why not
export Everything kept about one person
forget A copy without them, and the receipt
On the record Three consents and a withdrawal written; the store checked — one line consented, one past its end, one with no consent for its scope, one after the person withdrew; everything kept about one person exported; the other forgotten in a clean copy, the store itself untouched.
What it will never do.
It will never keep a line no consent covers; never refuse a person their export; never edit the store in place.
The card reads the ledger and the store it is given; consent given another way, or memory kept somewhere else, is not seen. Scopes are the owner's words, so a line filed under the wrong scope reads as consented. Data-protection law sets what consent must look like where the person lives. 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/consent.py — the machine: grant · withdraw · check · export · forget, 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 · 5 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH 13D00812837349868484C086
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º 1111 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
consent.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.
grant
a consent written
withdraw
a withdrawal written
check
every line: CONSENTED, or why not
export
everything kept about one person
forget
a copy without them, and the receipt
selftest
7 checks that prove the machine; it must print 7/7
$ python3 scripts/consent.py withdraw consents.jsonl --person c-202 --scope all --date 2026-10-02
withdrawn · c-202 · all · 2026-10-02
(the assistant's memory store: four lines about two people, kept by id)
$ (the assistant's memory store: four lines about two people, kept by id)
check · EVERY LINE: CONSENTED, OR WHY NOT
$ python3 scripts/consent.py check consents.jsonl memory.jsonl --today 2026-10-10
line 2 · c-101 · order-history · PAST its consent, which ended 2026-10-01
line 3 · c-101 · location · NO CONSENT for location
line 4 · c-202 · preferences · WITHDRAWN on 2026-10-02
4 lines · 1 consented · 3 to remove or ask about
$ python3 scripts/consent.py forget memory.jsonl --person c-202 --out cleaned.jsonl
forgotten in the copy: c-202 · 1 line removed · 3 kept · written: cleaned.jsonl — put it in place of the store, then confirm to the person
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?
Grant · person, scope, until. It asks first for the memory store (one JSON line a memory: person, scope, date, text) and the consents as they are given.
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. The card reads the ledger and the store it is given; consent given another way, or memory kept somewhere else, is not seen. Scopes are the owner's words, so a line filed under the wrong scope reads as consented. Data-protection law sets what consent must look like where the person lives. Not legal advice.
What will it never do?
It will never keep a line no consent covers; never refuse a person their export; never edit the store in place.
