THE ADOPTION CARD · are they using what they bought?
WAKES WHEN customer accounts are reviewed, a renewal nears, or someone asks who is at risk
THE LOOP
read <events> --seats · each account
flags · who to call, and why
call: what is in the way?
cohort · are newer accounts doing better?
read again next week
NEVER
Read a name out of the usage export
Count a week not yet reached as lost
Flag an account without its reason
IT MAKES read — per account: week, month, seats, features, trend; flags — the accounts to call, each with its reason; cohort — accounts active by week since their first, by starting week.
THE STANDARD usage, not opinion; pseudonymous ids only; every flag carries its reason; the lines are the owner's; cohorts are honest about time; a flag is a reason to call, not a verdict.
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 · 1570FBD142DD54A087526DA6
CITE THIS CARDTHE ADOPTION CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=adoption-card. Punch 1570FBD142DD54A087526DA6. Retrieved 2026-10-10.
What it is.
Reads whether customers are using what they bought, from the product's own usage export: read gives each account its active people in the last week and month against the seats it pays for, the features it touched of all there are, and the trend over four weeks; flags names the accounts to call — under the seat line, too narrow, falling three weeks running, or never used — each with its reason; cohort groups accounts by the week they started and counts them active week by week since, leaving weeks not yet reached blank.
It carries a machine that shows its working: read — per account: week, month, seats, features, trend; flags — the accounts to call, each with its reason; cohort — accounts active by week since their first, by starting week — 8 checks in its selftest, every command on the record. It will never read a name out of the usage export; never count a week not yet reached as lost; never flag an account without its reason.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
USAGE, NOT OPINIONAdoption is read from what the product recorded: who was active, when, on what.
PSEUDONYMOUS IDS ONLYThe card counts the user ids the export gives and reads no names; the account is the unit.
EVERY FLAG CARRIES ITS REASONUnder the seat line, too narrow, falling three weeks running, or never used — said in figures.
THE LINES ARE THE OWNER'SForty percent of seats and three features by default; the team sets its own.
COHORTS ARE HONEST ABOUT TIMEA week an account has not yet reached is blank, not zero.
A FLAG IS A REASON TO CALL, NOT A VERDICTThe conversation finds what is in the way.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-ONBOARDING-TEAM.md
THE MACHINEadoption.py · three commandsread — per account: week, month, seats, features, trend; flags — the accounts to call, each with its reason; cohort — accounts active by week since their first, by starting week. 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.
read Per account: week, month, seats, features, trend
flags The accounts to call, each with its reason
cohort Accounts active by week since their first, by starting week
On the record Three accounts read: one healthy across four features; one falling from four people to one, narrow and under its seats; one never used — the last two flagged with every reason; the cohorts counted week by week, the weeks not yet reached left blank.
What it will never do.
It will never read a name out of the usage export; never count a week not yet reached as lost; never flag an account without its reason.
The card reads the export it is given; an export that drops events, or counts a person twice under two ids, gives wrong counts. Activity is not value: an account can be busy and unhappy, or quiet and content. Today defaults to the last date in the export. 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-ONBOARDING-TEAM.md — the guide in references/, in the card's own voice
scripts/adoption.py — the machine: read · flags · cohort, 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-10 · EDITION 1 · PUNCH 1570FBD142DD54A087526DA6
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º 1098 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
adoption.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.
read
per account: week, month, seats, features, trend
flags
the accounts to call, each with its reason
cohort
accounts active by week since their first, by starting week
selftest
8 checks that prove the machine; it must print 8/8
(a month of usage exported for two accounts, pseudonymous ids; seats for three)
$ (a month of usage exported for two accounts, pseudonymous ids; seats for three)
read · PER ACCOUNT: WEEK, MONTH, SEATS, FEATURES, TREND
flags · THE ACCOUNTS TO CALL, EACH WITH ITS REASON
$ python3 scripts/adoption.py flags events.csv --seats seats.csv --today 2026-10-31
CALL · Birch 4 of 12 seats active this month (33%, under 40%) · 1 feature of 4 touched this month · active people falling three weeks running: 4 → 3 → 2 → 1
CALL · Cedar no one has used it
2 of 3 accounts to call
cohort · ACCOUNTS ACTIVE BY WEEK SINCE THEIR FIRST, BY STARTING WEEK
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?
Read <events> --seats · each account. It asks first for the usage export (date, account, user id, feature) and the seats each account pays for.
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 card reads the export it is given; an export that drops events, or counts a person twice under two ids, gives wrong counts. Activity is not value: an account can be busy and unhappy, or quiet and content. Today defaults to the last date in the export.
What will it never do?
It will never read a name out of the usage export; never count a week not yet reached as lost; never flag an account without its reason.
