THE LIFELONG COMPANION CARD · the rules for an AI kept for decades
WAKES WHEN someone asks what their AI will remember, or what happens to it when they die
THE LOOP
template · a policy with all five parts
write the person's own rules into it
check · the five parts, each named
calendar · yearly and life-event reviews
review it, and check it again
NEVER
Keep, read or print a memory
Pass a period of "forever"
Call a check of a policy legal advice
IT MAKES check — the five parts, each PASS or FAIL with its reason; calendar — the yearly reviews and what each must clear away; template — a complete policy to start from.
THE STANDARD a policy, not a store; every kind has a period; the person reads first; forget and take away; every ending planned; reviewed, on the day.
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 · 88E2380D87AC0D29DEE72396
CITE THIS CARDTHE LIFELONG COMPANION CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=lifelong-companion-card. Punch 88E2380D87AC0D29DEE72396. Retrieved 2026-10-11.
What it is.
The rules for an AI companion kept for decades, written down and checked before anyone needs them. It waits on assistants that persist for decades; today it checks the policy of any AI that remembers. check reads a companion policy, in JSON or in Markdown with named sections, for the five parts it must have: a retention schedule with a real period for each kind of thing kept, the readers (the person among them) and the heirs, forget on request within a stated number of days, an export right with a format and a time, and an ending plan for death, for the person ending it and for the provider closing. calendar writes the yearly reviews, and the life events that call for one, with what each review must clear away, as a calendar file. template writes a complete policy to start from. It is not a memory store and keeps none.
It carries a machine that shows its working: check — the five parts, each PASS or FAIL with its reason; calendar — the yearly reviews and what each must clear away; template — a complete policy to start from — 8 checks in its selftest, every command on the record. It will never keep, read or print a memory; never pass a period of "forever"; never call a check of a policy legal advice.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
A POLICY, NOT A STOREThe card checks the written rules and keeps no memories; a memory found in a policy file is counted and never printed.
EVERY KIND HAS A PERIODEach kind of thing kept has N days, weeks, months or years, "until" an event, or "for life"; "forever" is not a period.
THE PERSON READS FIRSTThe person is always among the readers, and the heirs are named, or "none" is written.
FORGET AND TAKE AWAYForgetting and a full export are on the person's request, each within a stated number of days.
EVERY ENDING PLANNEDThere is a plan for death, for the person ending it, and for the provider closing.
REVIEWED, ON THE DAYA review every year, on 28 February in a common year for a 29 February start, and within 30 days of a life event.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-COMPANION-POLICY.md
THE MACHINEcompanion.py · three commandscheck — the five parts, each PASS or FAIL with its reason; calendar — the yearly reviews and what each must clear away; template — a complete policy to start from. 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 The five parts, each PASS or FAIL with its reason
calendar The yearly reviews and what each must clear away
template A complete policy to start from
On the record The template policy passes all five parts in JSON and in Markdown alike; an older policy fails four (conversations kept "forever", no heirs, no time limit on forgetting, no plan for the person ending it or the provider closing), and the one memory left in it is counted and never printed. Begun on 29 Feb 2028, the reviews fall on 28 Feb 2029, 2030 and 2031 and on 29 Feb 2032, each naming what should be gone by then, and go into a calendar of 4 all-day reviews.
What it will never do.
It will never keep, read or print a memory; never pass a period of "forever"; never call a check of a policy legal advice.
It waits on assistants that persist for decades; until then it checks the policies of AI products that remember. It reads what a policy says, not what a product does, so it cannot see whether forgetting or deletion really happened. A Markdown policy is read by its headings and a few words in each. Not a memory store; 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-COMPANION-POLICY.md — the guide in references/, in the card's own voice
scripts/companion.py — the machine: check · calendar · template, 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 88E2380D87AC0D29DEE72396
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º 1177 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
companion.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
the five parts, each PASS or FAIL with its reason
calendar
the yearly reviews and what each must clear away
template
a complete policy to start from
selftest
8 checks that prove the machine; it must print 8/8
template · A COMPLETE POLICY TO START FROM
$ python3 scripts/companion.py template --out policy.json
wrote policy.json · a starting policy in JSON with all five parts; every value is an example to replace with the person's own
template · A COMPLETE POLICY TO START FROM
$ python3 scripts/companion.py template --md --out policy.md
wrote policy.md · a starting policy in Markdown with all five parts; every value is an example to replace with the person's own
check · THE FIVE PARTS, EACH PASS OR FAIL WITH ITS REASON
$ python3 scripts/companion.py check policy.json
policy.json · the household companion · a companion policy
PASS · retention · 4 kinds, each with its period: everyday conversations 2 years · health notes the person asks it to keep until the person asks · the life story the person dictates for life · voice recordings 30 days
PASS · readers and heirs · 2 readers, the person among them · heirs: the executor the person names (export the life story, then delete everything)
PASS · forget on request · on request, within 30 days
PASS · export · on request, as JSON and plain text, within 30 days
PASS · ending · a plan when the person dies, when the person ends it, when the provider closes
note · the life story the person dictates is kept for life: the ending plan governs it
note · forget has exceptions: what the law requires to be kept, named to the person (each one must be a reason the person can read)
PASS · 5 of 5 parts in place
a check of a written policy, not legal advice · this card keeps no memories
check · THE FIVE PARTS, EACH PASS OR FAIL WITH ITS REASON
$ python3 scripts/companion.py check policy.md
policy.md · the household companion · a companion policy
PASS · retention · 4 kinds, each with its period: everyday conversations 2 years · health notes the person asks it to keep until the person asks · the life story the person dictates for life · voice recordings 30 days
PASS · readers and heirs · 2 readers, the person among them · heirs: the executor the person names: export the life story, then delete everything
PASS · forget on request · on request, within 30 days
PASS · export · on request, as JSON and plain text, within 30 days
PASS · ending · a plan when the person dies, when the person ends it, when the provider closes
note · the life story the person dictates is kept for life: the ending plan governs it
PASS · 5 of 5 parts in place
a check of a written policy, not legal advice · this card keeps no memories
check · THE FIVE PARTS, EACH PASS OR FAIL WITH ITS REASON
$ python3 scripts/companion.py check old.md
old.md · the old assistant · a companion policy
FAIL · retention · conversations: "forever" is not a period; write N days, weeks, months or years, "until <an event>", or "for life"
FAIL · readers and heirs · no heirs named: say who may read or receive it after death or incapacity, or write "none"
FAIL · forget on request · no time limit: say within how many days a request is carried out
PASS · export · on request, as a PDF, within 60 days
FAIL · ending · no ending plan for: when the person ends it, when the provider closes
note · the provider's people are among the readers: say when, why, and with whose yes
note · this file holds 1 memory; the card does not read, keep or print them: it checks policies, it is not a memory store
FAIL · 4 of 5 parts missing or unclear
a check of a written policy, not legal advice · this card keeps no memories
calendar · THE YEARLY REVIEWS AND WHAT EACH MUST CLEAR AWAY
$ python3 scripts/companion.py calendar policy.json --start 2028-02-29 --years 4 --out reviews.ics
policy.json · the household companion · yearly reviews from 2028-02-29, 4 years
review 1 · 2029-02-28 (Wed)
everyday conversations, kept 2 years: nothing is old enough yet
health notes the person asks it to keep, kept until the person asks: has that happened?
voice recordings, kept 30 days: anything from before 2029-01-29 should be gone
review 2 · 2030-02-28 (Thu)
everyday conversations, kept 2 years: nothing is old enough yet
health notes the person asks it to keep, kept until the person asks: has that happened?
voice recordings, kept 30 days: anything from before 2030-01-29 should be gone
review 3 · 2031-02-28 (Fri)
everyday conversations, kept 2 years: anything from before 2029-02-28 should be gone
health notes the person asks it to keep, kept until the person asks: has that happened?
voice recordings, kept 30 days: anything from before 2031-01-29 should be gone
review 4 · 2032-02-29 (Sun)
everyday conversations, kept 2 years: anything from before 2030-02-28 should be gone
health notes the person asks it to keep, kept until the person asks: has that happened?
voice recordings, kept 30 days: anything from before 2032-01-30 should be gone
and a review within 30 days of any of these: a birth or an adoption; a marriage, a partnership or a separation; a move of home or of country; a serious diagnosis; a death in the family; turning 18, if the companion began in childhood; retirement; the provider changes hands or changes its terms
wrote reviews.ics · 4 all-day reviews, opens in any calendar
a check of a written policy, not legal advice · this card keeps no memories
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?
Template · a policy with all five parts. It asks first for the companion's written policy (or the person's wishes, to write one from the template), the date it began, and the life events that should call a review.
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 waits on assistants that persist for decades; until then it checks the policies of AI products that remember. It reads what a policy says, not what a product does, so it cannot see whether forgetting or deletion really happened. A Markdown policy is read by its headings and a few words in each. Not a memory store; not legal advice.
What will it never do?
It will never keep, read or print a memory; never pass a period of "forever"; never call a check of a policy legal advice.
