THE PRODUCT LAUNCH CARD · counted back from the date; GO only on gates
WAKES WHEN someone plans a launch or a release, or runs a go/no-go, or wants the launch retro
THE LOOP
productlaunch.py plan · the T-minus list
an owner on every row; dates move, why
ready · late, blocked, unowned, every gate
go/no-go the day before, gates read aloud
retro by T+30, numbers first
NEVER
Ship with a gate open
Let "the team" be an owner
Hold a retro with no numbers
IT MAKES plan — the T-minus plan with dates and owner slots; ready — late, blocked, unowned; GO or NO-GO on the gates; retro — the retro sheet with the T+7 and T+30 numbers to collect.
THE STANDARD count back from the date; a gate is a gate; every row has an owner; gO is read aloud the day before; every claim in the announcement is true today, with its source; the retro collects numbers first.
PROOF SELFTEST 10/10 · witnessed in Claude 2026-10-09 · 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 · 7DB5289140B881C0CEFBFA7E
CITE THIS CARDTHE PRODUCT LAUNCH CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=product-launch-card. Punch 7DB5289140B881C0CEFBFA7E. Retrieved 2026-10-10.
What it is.
Runs a product or feature launch as a plan counted back from the date: eighteen items across product, positioning, pricing, enablement, support, legal, announcement and measurement, eleven of them gates, each with a due date, an owner slot and a status; a readiness check that names what is late, blocked or unowned and says GO only when every gate reads done; and a retro sheet with the T+7 and T+30 numbers to collect.
It carries a machine that shows its working: plan — the T-minus plan with dates and owner slots; ready — late, blocked, unowned; GO or NO-GO on the gates; retro — the retro sheet with the T+7 and T+30 numbers to collect — 10 checks in its selftest, every command on the record. It will never ship with a gate open; never let "the team" be an owner; never hold a retro with no numbers.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
COUNT BACK FROM THE DATEEvery item has a due date arithmetic gives it; the team moves it with a reason in the note.
A GATE IS A GATEThe thing works, there is a way to turn it off, the price is approved, counsel has read the claims, support can answer, the number is baselined. No gate open, no launch.
EVERY ROW HAS AN OWNEREvery row has an owner, a person; "the team" owns nothing.
GO IS READ ALOUD THE DAY BEFOREGO is read aloud the day before, gate by gate, done or not; a not-yet is nobody's fault, a broken launch is everybody's.
EVERY CLAIM IN THE ANNOUNCEMENT IS TRUE TODAY, WITH ITS SOURCETHE FIELD CARD's rule applies to what we say about ourselves.
THE RETRO COLLECTS NUMBERS FIRSTThe bar set before launch against what happened at T+7 and T+30.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/GATES-AND-WORKSTREAMS.md
THE MACHINEproductlaunch.py · three commandsplan — the T-minus plan with dates and owner slots; ready — late, blocked, unowned; GO or NO-GO on the gates; retro — the retro sheet with the T+7 and T+30 numbers to collect. Every command prints its working and refuses a bad input; 10 checks in its selftest, every command on the record.
What it does once your AI has it.
plan The T-minus plan with dates and owner slots
ready Late, blocked, unowned; GO or NO-GO on the gates
retro The retro sheet with the T+7 and T+30 numbers to collect
On the record A launch planned back from the 5th of November: eighteen items, eleven gates, the positioning item already late; nothing done was NO-GO; with every gate done but the kill switch blocked on infra it was still NO-GO, with the reason; and the retro sheet dated T+7 and T+30.
What it will never do.
It will never ship with a gate open; never let "the team" be an owner; never hold a retro with no numbers.
The dates are arithmetic back from the launch; the team moves them with reasons. GO from the machine means every gate row reads done, not that the launch will go well. The eighteen items are a starting list; a launch adds its own. 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
GATES-AND-WORKSTREAMS.md — the guide in references/, in the card's own voice
scripts/productlaunch.py — the machine: plan · ready · retro, standard library only, selftest 10/10
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 10/10 · 3 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-09 · EDITION 1 · PUNCH 7DB5289140B881C0CEFBFA7E
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º 847 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-09
productlaunch.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 T-minus plan with dates and owner slots
ready
late, blocked, unowned; GO or NO-GO on the gates
retro
the retro sheet with the T+7 and T+30 numbers to collect
selftest
10 checks that prove the machine; it must print 10/10
plan · THE T-MINUS PLAN WITH DATES AND OWNER SLOTS
$ python3 scripts/productlaunch.py plan --date 2026-11-05 --name "Audit log" --out plan.csv
LAUNCH PLAN · 2026-11-05 · Audit log · 18 items · 11 gates · counted back from the date, weekends skipped
2026-10-22 T-14 product the feature works on real accounts, with the failure cases tried · GATE
2026-10-26 T-10 product rollback or kill switch written down and tried · GATE
2026-10-08 T-28 positioning one-paragraph positioning: for whom, what, instead of what, why believe it · GATE
2026-10-15 T-21 positioning the three messages, in the customer's words, with proof for each
2026-10-15 T-21 pricing price and packaging approved by whoever owns the number · GATE
2026-10-26 T-10 pricing pricing page copy, with every claim sourced
2026-10-26 T-10 enablement sales walkthrough: the demo, the three questions, the objections and answers · GATE
2026-10-29 T-7 enablement field card (competitive) reviewed by counsel · GATE
2026-10-29 T-7 support help article and the first ten questions answered · GATE
2026-10-30 T-5 support macros and escalation path for the first week
2026-10-29 T-7 legal announcement, pricing page and claims read by counsel · GATE
2026-10-26 T-10 legal terms, privacy and data notes updated if anything changed
2026-10-29 T-7 announcement the announcement drafted, every claim true today, with its source · GATE
2026-11-02 T-3 announcement customer email and in-product note scheduled
2026-10-22 T-14 measurement the numbers that say it worked, baselined before launch (adoption, activation, tickets, revenue) · GATE
2026-10-30 T-5 measurement dashboard or sheet that shows them, owner named
2026-11-04 T-1 launch day go/no-go meeting the day before: every gate row done · GATE
2026-11-04 T-1 launch day the day-of checklist: who watches what, who speaks for us if something breaks
plan written · plan.csv · add owners, move dates with reasons, keep status current
ready · LATE, BLOCKED, UNOWNED; GO OR NO-GO ON THE GATES
$ python3 scripts/productlaunch.py ready plan.csv --today 2026-10-09
READINESS · as of 2026-10-09 · 0 of 18 items done · 11 gates, 11 open · NO-GO
GATE OPEN product the feature works on real accounts, with the failure cases tried · due 2026-10-22 · todo · NO OWNER
GATE OPEN product rollback or kill switch written down and tried · due 2026-10-26 · todo · NO OWNER
GATE OPEN positioning one-paragraph positioning: for whom, what, instead of what, why believ · due 2026-10-08 · todo · NO OWNER
GATE OPEN pricing price and packaging approved by whoever owns the number · due 2026-10-15 · todo · NO OWNER
GATE OPEN enablement sales walkthrough: the demo, the three questions, the objections and a · due 2026-10-26 · todo · NO OWNER
GATE OPEN enablement field card (competitive) reviewed by counsel · due 2026-10-29 · todo · NO OWNER
GATE OPEN support help article and the first ten questions answered · due 2026-10-29 · todo · NO OWNER
GATE OPEN legal announcement, pricing page and claims read by counsel · due 2026-10-29 · todo · NO OWNER
GATE OPEN announcement the announcement drafted, every claim true today, with its source · due 2026-10-29 · todo · NO OWNER
GATE OPEN measurement the numbers that say it worked, baselined before launch (adoption, act · due 2026-10-22 · todo · NO OWNER
GATE OPEN launch day go/no-go meeting the day before: every gate row done · due 2026-11-04 · todo · NO OWNER
LATE positioning one-paragraph positioning: for whom, what, instead of what, why believ · due 2026-10-08 · todo
NO OWNER 18 open item(s) have no owner
GO means every gate row reads done; it does not mean the launch will go well. The team decides, with this in front of it.
(three weeks later: every gate marked done except the kill switch, blocked on infra)
$ (three weeks later: every gate marked done except the kill switch, blocked on infra)
ready · LATE, BLOCKED, UNOWNED; GO OR NO-GO ON THE GATES
$ python3 scripts/productlaunch.py ready plan.csv --today 2026-11-04
READINESS · as of 2026-11-04 · 10 of 18 items done · 11 gates, 1 open · NO-GO
GATE OPEN product rollback or kill switch written down and tried · due 2026-10-26 · blocked · owner named
LATE product rollback or kill switch written down and tried · due 2026-10-26 · blocked
LATE positioning the three messages, in the customer's words, with proof for each · due 2026-10-15 · todo
LATE pricing pricing page copy, with every claim sourced · due 2026-10-26 · todo
LATE support macros and escalation path for the first week · due 2026-10-30 · todo
LATE legal terms, privacy and data notes updated if anything changed · due 2026-10-26 · todo
LATE announcement customer email and in-product note scheduled · due 2026-11-02 · todo
LATE measurement dashboard or sheet that shows them, owner named · due 2026-10-30 · todo
BLOCKED product rollback or kill switch written down and tried · T-10 · waiting on infra for the kill switch
NO OWNER 7 open item(s) have no owner
GO means every gate row reads done; it does not mean the launch will go well. The team decides, with this in front of it.
retro · THE RETRO SHEET WITH THE T+7 AND T+30 NUMBERS TO COLLECT
$ head -6 retro.md
# Launch retro · launched 2026-11-05 · held by T+30 (2026-12-05)
## The numbers (fill from the measurement sheet; baseline, T+7, T+30)
| measure | baseline | T+7 (2026-11-12) | T+30 (2026-12-05) | the bar we set before launch |
|---|---|---|---|---|
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?
Productlaunch.py plan · the T-minus list. It asks first for the launch date, what is launching, and who owns each workstream.
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 (10/10) 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 dates are arithmetic back from the launch; the team moves them with reasons. GO from the machine means every gate row reads done, not that the launch will go well. The eighteen items are a starting list; a launch adds its own.
What will it never do?
It will never ship with a gate open; never let "the team" be an owner; never hold a retro with no numbers.
