THE FIRST VALUE CARD · the days from signature to first value
WAKES WHEN an onboarding plan is written or reviewed, or someone asks how long first value takes
THE LOOP
plan --start --milestones · working days
status <plan> · ON TRACK, AT RISK, LATE
act on AT RISK before it is LATE
ttv <accounts> · the median, the waiting
shorten the slowest step next
NEVER
Count a weekend as a working day
Call an open milestone done
Hide a late account in an average
IT MAKES plan — the dated plan; status — each milestone and the account's verdict; ttv — days to first value per account, the median, the waiting.
THE STANDARD first value is the milestone that matters; working days; aT RISK before LATE; late is counted, not softened; the waiting are named; the plan is the team's.
PROOF SELFTEST 9/9 · 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 · 91129E716C0B5DFFD89A3E5A
CITE THIS CARDTHE FIRST VALUE CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=first-value-card. Punch 91129E716C0B5DFFD89A3E5A. Retrieved 2026-10-10.
What it is.
Plans and counts the days between a customer's signature and the first time they get what they paid for: plan lays out the onboarding milestones in working days from the start date and writes them as a CSV; status reads an account's plan against today, each milestone DONE, DONE LATE, DUE SOON, OPEN or LATE with its working days, and the account ON TRACK, AT RISK or LATE; ttv reads every account's start and first-value dates and gives the days to first value for each, the median, the slowest, and the accounts still waiting with their days so far.
It carries a machine that shows its working: plan — the dated plan; status — each milestone and the account's verdict; ttv — days to first value per account, the median, the waiting — 9 checks in its selftest, every command on the record. It will never count a weekend as a working day; never call an open milestone done; never hide a late account in an average.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
FIRST VALUE IS THE MILESTONE THAT MATTERSThe plan ends at the first time the customer gets what they paid for; everything before it serves it.
WORKING DAYSMilestones are counted Monday to Friday; holidays are the owner's to add.
AT RISK BEFORE LATEA milestone two working days from due and not done puts the account AT RISK, so it is acted on in time.
LATE IS COUNTED, NOT SOFTENEDA milestone past its date is LATE by its working days; a done one late is DONE LATE by its days.
THE WAITING ARE NAMEDTime to first value is the median of those who reached it, and every account still waiting is named with its days so far.
THE PLAN IS THE TEAM'SThe card dates and reads it; the team decides it.
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 MACHINEfirstvalue.py · three commandsplan — the dated plan; status — each milestone and the account's verdict; ttv — days to first value per account, the median, the waiting. Every command prints its working and refuses a bad input; 9 checks in its selftest, every command on the record.
What it does once your AI has it.
plan The dated plan
status Each milestone and the account's verdict
ttv Days to first value per account, the median, the waiting
On the record Four milestones dated in working days; the kept plan read AT RISK with one done late and one due soon, then LATE once the report passed its date; time to first value read across four accounts — the median, the slowest, and the one still waiting.
What it will never do.
It will never count a weekend as a working day; never call an open milestone done; never hide a late account in an average.
What counts as first value is the team's definition, written as a milestone; the card counts days to it, not whether the customer agrees they got it. Public holidays are not known to the card. A median over a handful of accounts moves a lot with one more. 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/firstvalue.py — the machine: plan · status · ttv, standard library only, selftest 9/9
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 9/9 · 3 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH 91129E716C0B5DFFD89A3E5A
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º 1097 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
firstvalue.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.
plan
the dated plan
status
each milestone and the account's verdict
ttv
days to first value per account, the median, the waiting
selftest
9 checks that prove the machine; it must print 9/9
plan · THE DATED PLAN
$ python3 scripts/firstvalue.py plan --start 2026-10-12 --milestones access=2,data=5,first-report=8,first-value=12 --out plan.csv
2026-10-14 Wed access
2026-10-19 Mon data
2026-10-22 Thu first-report
2026-10-28 Wed first-value
4 milestones · first value on 2026-10-28, 12 working days from the start
written: plan.csv
(the plan kept: two done, one of them late)
$ (the plan kept: two done, one of them late)
status · EACH MILESTONE AND THE ACCOUNT'S VERDICT
$ python3 scripts/firstvalue.py status plan.csv --today 2026-10-21
DONE access due 2026-10-14
DONE LATE data due 2026-10-19 · 2 working days late
DUE SOON first-report due 2026-10-22 · 1 working day left
OPEN first-value due 2026-10-28 · 5 working days left
AT RISK · 2 of 4 milestones done · read on 2026-10-21
status · EACH MILESTONE AND THE ACCOUNT'S VERDICT
$ python3 scripts/firstvalue.py status plan.csv --today 2026-10-26
DONE access due 2026-10-14
DONE LATE data due 2026-10-19 · 2 working days late
LATE first-report due 2026-10-22 · 2 working days over
DUE SOON first-value due 2026-10-28 · 2 working days left
LATE · 2 of 4 milestones done · read on 2026-10-26
(four accounts' start and first-value dates)
$ (four accounts' start and first-value dates)
ttv · DAYS TO FIRST VALUE PER ACCOUNT, THE MEDIAN, THE WAITING
$ python3 scripts/firstvalue.py ttv accounts.csv --today 2026-10-10
Alder 14 days to first value
Cedar 21 days to first value
Birch 35 days to first value
Dogwood still waiting · 19 days so far
3 reached first value · median 21 days · slowest Birch at 35 · 1 still waiting
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?
Plan --start --milestones · working days. It asks first for the start date and the milestones with their working days; for a review, each account's plan or start and first-value dates.
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 (9/9) 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. What counts as first value is the team's definition, written as a milestone; the card counts days to it, not whether the customer agrees they got it. Public holidays are not known to the card. A median over a handful of accounts moves a lot with one more.
What will it never do?
It will never count a weekend as a working day; never call an open milestone done; never hide a late account in an average.
