THE SUCCESSION CARD · a model retired, its promises kept honestly
WAKES WHEN a model, an agent or an AI product is being retired, and its users must be told
THE LOOP
write the plan: dates, export, migration
list every promise made to users
check · six parts; mend every fault
notices · the schedule, date by date
promises · each one's fate, then announce
NEVER
Move memories without each user's choice
Leave a promise with no fate
Shorten notice below ninety days
IT MAKES check — six parts: notice, told, export, migration, promises, data; notices — the notice schedule, date by date; promises — every open promise and its fate.
THE STANDARD ninety days at least; users can leave; moved by choice; every promise has a fate; deleted on a date; a check, not counsel.
PROOF SELFTEST 8/8 · witnessed in Claude 2026-10-11 · 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 · 8A98217033B9E4A7D73B5E7D
CITE THIS CARDTHE SUCCESSION CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=succession-card. Punch 8A98217033B9E4A7D73B5E7D. Retrieved 2026-10-11.
What it is.
Checks the retirement of a model, an agent or an AI product, so its users' memories, agents and promises are moved or ended honestly. check reads a retirement plan for six parts: notice (90 days at least), users told, an export open from 30 days before the retirement until it, in an open format, covering all that moves, a migration path saying what moves and what stays, memories moved only by each user's choice, every promise with a fate, and data deleted or moved with consent by set dates; notices builds the notice schedule from the announcement to backups cleared, with reminders at 90, 60, 30, 14, 7 and 1 days; promises lists every open promise and its fate (honoured, transferred, ended with notice, refunded) and names any without one. It waits on model lifecycles that carry memories and agents for years; today it checks any retirement.
It carries a machine that shows its working: check — six parts: notice, told, export, migration, promises, data; notices — the notice schedule, date by date; promises — every open promise and its fate — 8 checks in its selftest, every command on the record. It will never move memories without each user's choice; never leave a promise with no fate; never shorten notice below ninety days.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
NINETY DAYS AT LEASTFrom announcement to retirement; a plan may give more, and the floor is never lowered.
USERS CAN LEAVEAn export opens 30 days before the retirement at least, stays open until it, in an open format, and covers everything that would move.
MOVED BY CHOICEMemories, agents and conversations move to a successor only by each user's choice, and the plan says what does not move.
EVERY PROMISE HAS A FATEHonoured before the retirement, transferred to a successor that accepts it, ended with ninety days' notice, or refunded.
DELETED ON A DATEData is deleted, or moved with consent, by a written date after the export closes, and backups by a later one.
A CHECK, NOT COUNSELIt reads the plan as written; what users were promised and the law where they live may ask for more.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-SUCCESSION.md
THE MACHINEsuccession.py · three commandscheck — six parts: notice, told, export, migration, promises, data; notices — the notice schedule, date by date; promises — every open promise and its fate. 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.
check Six parts: notice, told, export, migration, promises, data
notices The notice schedule, date by date
promises Every open promise and its fate
On the record A plan giving 182 days of notice passes all six parts; a rushed plan fails five (60 days of notice, an export closing before the retirement and leaving out what moves, memories moved without each user's choice, three promises without an honest fate, data moved without consent and no backup date). The schedule holds 14 notices from 2036-01-15 to 2036-10-30, the 90-day reminder on 2036-04-16; four promises hold and one closed before the announcement, while the rushed list has three faults; a 30-day floor is refused.
What it will never do.
It will never move memories without each user's choice; never leave a promise with no fate; never shorten notice below ninety days.
It checks a plan as written, not whether the export works or the successor keeps what it accepted. Its floors (90 days of notice, an export open 30 days before) are the card's, not the law's; a contract or a law may ask for more. It waits on model lifecycles of decades, with memories and agents that outlive a model; today it checks the retirement of any product, agent or model version. 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-SUCCESSION.md — the guide in references/, in the card's own voice
scripts/succession.py — the machine: check · notices · promises, 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-11 · EDITION 1 · PUNCH 8A98217033B9E4A7D73B5E7D
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º 1182 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-11
succession.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.
check
six parts: notice, told, export, migration, promises, data
notices
the notice schedule, date by date
promises
every open promise and its fate
selftest
8 checks that prove the machine; it must print 8/8
check · SIX PARTS: NOTICE, TOLD, EXPORT, MIGRATION, PROMISES, DATA
$ python3 scripts/succession.py check plan.json --promises promises.csv
plan.json · helper-3 retires 2036-07-15 · 6 parts checked
PASS · NOTICE 182 days from the announcement (2036-01-15) to the retirement (2036-07-15); 90 at least
PASS · TOLD users are told by: in the app, a letter to every account holder
PASS · EXPORT open 2036-01-15 to 2036-08-14 (182 days before the retirement, 30 after), as json, markdown; covers memories, agents, settings, conversations
PASS · MIGRATION to helper-4: moves memories, agents, settings; does not move: voice samples; by each user's choice
PASS · PROMISES every open promise has an honest fate (4)
PASS · DATA deleted, none moved or kept, by 2036-08-31; backups cleared by 2036-10-30
PASS · an honest retirement, as written
A check of a plan, not legal advice: the notice your users were promised, and the law where they live, may ask for more.
check · SIX PARTS: NOTICE, TOLD, EXPORT, MIGRATION, PROMISES, DATA
$ python3 scripts/succession.py check rushed.json --promises rushed-promises.csv
rushed.json · helper-3 retires 2036-07-15 · 6 parts checked
FAULT · NOTICE 60 days from the announcement (2036-05-16) to the retirement (2036-07-15); 90 at least
PASS · TOLD users are told by: in the app
FAULT · EXPORT it closes on 2036-07-01, before the retirement; what moves must also export, and it leaves out: memories, agents
FAULT · MIGRATION memories, agents and conversations move only by each user's choice
FAULT · PROMISES 3 of 4 open promises without an honest fate: P01, P02, P04
FAULT · DATA data moves only with each user's consent; no date by which backups are cleared
FAIL · 5 parts to mend before it is announced
A check of a plan, not legal advice: the notice your users were promised, and the law where they live, may ask for more.
notices · THE NOTICE SCHEDULE, DATE BY DATE
$ python3 scripts/succession.py notices plan.json --out notices.csv
plan.json · the notice schedule for helper-3 · 14 notices · told by in the app, a letter to every account holder
2036-01-15 182 days before announce: helper-3 retires on 2036-07-15; what moves, what stays, how to export
2036-01-15 182 days before the export opens: memories, agents, settings, conversations, as json, markdown
2036-02-01 165 days before moving to helper-4 opens, by each user's choice
2036-04-16 90 days before reminder: 90 days left; export and move now
2036-05-16 60 days before reminder: 60 days left; export and move now
2036-06-15 30 days before reminder: 30 days left; export and move now
2036-07-01 14 days before reminder: 14 days left; export and move now
2036-07-08 7 days before reminder: 7 days left; export and move now
2036-07-14 1 day before reminder: 1 day left; export and move now
2036-07-15 retirement day helper-3 retires today; the export stays open until 2036-08-14
2036-08-07 23 days after reminder: the export closes in 7 days
2036-08-14 30 days after the export closes today
2036-08-31 47 days after confirm: the retired model's copy of users' data is deleted
2036-10-30 107 days after confirm: backups are cleared; the succession is complete
wrote notices.csv (14 rows)
promises · EVERY OPEN PROMISE AND ITS FATE
$ python3 scripts/succession.py promises promises.csv --plan plan.json
promises.csv · 5 promises · helper-3 retires 2036-07-15 · notice 90 days at least
P01 · every account · memories kept for the life of the account · until ongoing
holds · transferred to helper-4, which accepts it
P02 · team plans · a named agent kept running for each team · until 2036-12-31
holds · ended with notice: told 2036-01-15, ends 2036-07-15, 182 days
P03 · annual plans · a year of service paid in advance · until 2036-11-30
holds · refunded on 2036-07-15, for the part not given
P04 · researchers · the same answers to the same prompts · until 2036-06-30
holds · honoured in full: it ends 2036-06-30, on or before the retirement
P05 · early users · a free month · until 2035-12-31
closed · ended 2035-12-31, before the announcement
4 open: 4 hold, 0 faults · 1 closed before the announcement
promises · EVERY OPEN PROMISE AND ITS FATE
$ python3 scripts/succession.py promises rushed-promises.csv --plan rushed.json
rushed-promises.csv · 5 promises · helper-3 retires 2036-07-15 · notice 90 days at least
P01 · every account · memories kept for the life of the account · until ongoing
FAULT · no fate: it runs on and the plan does not say what becomes of it
P02 · team plans · a named agent kept running for each team · until 2036-12-31
FAULT · ended with 30 days' notice (told 2036-06-15, ends 2036-07-15), under 90
P03 · annual plans · a year of service paid in advance · until 2036-11-30
holds · refunded on 2036-07-15, for the part not given
P04 · researchers · the same answers to the same prompts · until 2036-09-30
FAULT · it cannot be honoured: it runs past the retirement (2036-07-15); transfer it or end it with notice
P05 · early users · a free month · until 2035-12-31
closed · ended 2035-12-31, before the announcement
4 open: 1 hold, 3 faults · 1 closed before the announcement
promises · EVERY OPEN PROMISE AND ITS FATE
$ python3 scripts/succession.py promises promises.csv --plan plan.json --min-notice 30
--min-notice is a whole number of days, 90 or more: it may raise the floor, never lower it
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?
Write the plan: dates, export, migration. It asks first for the retirement plan (the model, the announcement and retirement dates, how users are told, the export, the migration path, what happens to data) and every promise made to users, with its fate.
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. It checks a plan as written, not whether the export works or the successor keeps what it accepted. Its floors (90 days of notice, an export open 30 days before) are the card's, not the law's; a contract or a law may ask for more. It waits on model lifecycles of decades, with memories and agents that outlive a model; today it checks the retirement of any product, agent or model version. Not legal advice.
What will it never do?
It will never move memories without each user's choice; never leave a promise with no fate; never shorten notice below ninety days.
