THE NEW STARTER CARD · a new colleague's first ninety days
WAKES WHEN someone new is joining, or a manager plans their first weeks
THE LOOP
plan --role --start · ninety days, owned
check · a buddy, real work, thirty days
due · what is owed today, by owner
the conversations at 30, 60 and 90
ask them what to change for the next
NEVER
Leave a first-day item without an owner
Plan a first week with no real work
Keep anyone's personal details
IT MAKES plan — the plan as item, owner, due, done; due — what is due or overdue, by owner; check — owners, dates, a buddy, real work in week one, the thirty-day conversation.
THE STANDARD planned before they arrive; every item has an owner and a date; real work in the first week; three conversations; a first day is a working day; the plan is a start.
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 · 9B0BE192DF0B878BA67427DB
CITE THIS CARDTHE NEW STARTER CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=new-starter-card. Punch 9B0BE192DF0B878BA67427DB. Retrieved 2026-10-10.
What it is.
Plans and keeps a new colleague's first ninety days: plan writes the plan from the role and the first day — before day one (accounts, equipment, a buddy named, the welcome note), day one, week one (the role explained, a first real piece of work, what was confusing), the paperwork, and the conversations at thirty, sixty and ninety days — each item owned by a role and dated in working days, as a CSV; due names what is due today or overdue, by owner; check reads any plan for an owner and a date on every item, a buddy, real work in the first week, a thirty-day conversation and accounts made before day one.
It carries a machine that shows its working: plan — the plan as item, owner, due, done; due — what is due or overdue, by owner; check — owners, dates, a buddy, real work in week one, the thirty-day conversation — 8 checks in its selftest, every command on the record. It will never leave a first-day item without an owner; never plan a first week with no real work; never keep anyone's personal details.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
PLANNED BEFORE THEY ARRIVEAccounts, equipment, a buddy and a welcome note are done before day one, owned and dated.
EVERY ITEM HAS AN OWNER AND A DATEOwners are roles — the manager, the buddy, IT, the people team — never a person's details.
REAL WORK IN THE FIRST WEEKA small, finishable piece of work, handed over by day five.
THREE CONVERSATIONSAt thirty, sixty and ninety days: what is working, owning a piece end to end, the role for the next quarter.
A FIRST DAY IS A WORKING DAYA start on a weekend is refused.
THE PLAN IS A STARTThe manager changes it for the person; the check keeps the parts every plan needs.
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 MACHINEstarter.py · three commandsplan — the plan as item, owner, due, done; due — what is due or overdue, by owner; check — owners, dates, a buddy, real work in week one, the thirty-day conversation. 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.
plan The plan as item, owner, due, done
due What is due or overdue, by owner
check Owners, dates, a buddy, real work in week one, the thirty-day conversation
On the record Ninety days planned from the first day, owned by roles and dated in working days; the plan checked clean; on day two, what was due and overdue by owner; a thin hand-written plan checked and named for its unowned item, no buddy, no first-week work, no thirty-day conversation and no accounts before day one.
What it will never do.
It will never leave a first-day item without an owner; never plan a first week with no real work; never keep anyone's personal details.
The plan is a template for a desk role; a role on shifts, in the field or part-time needs its own items. The card keeps no personal details of the starter or anyone else — paperwork lives in the people team's own system. Not legal or employment advice: what a starter must sign, and when, is local law's. 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/starter.py — the machine: plan · due · check, 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 9B0BE192DF0B878BA67427DB
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º 1099 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
starter.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 plan as item, owner, due, done
due
what is due or overdue, by owner
check
owners, dates, a buddy, real work in week one, the thirty-day conversation
selftest
8 checks that prove the machine; it must print 8/8
plan · THE PLAN AS ITEM, OWNER, DUE, DONE
$ python3 scripts/starter.py plan --role pastry cook --start 2026-11-02 --manager the head baker --out plan.csv
the first ninety days · pastry cook · first day 2026-11-02
2026-10-26 IT accounts made: email, chat, the tools of the role
2026-10-26 IT equipment ordered and set up
2026-10-28 the head baker buddy named and told
2026-10-29 the head baker welcome note sent with the first-day plan
2026-11-02 the head baker first-day welcome: the team, the space, the plan
2026-11-02 buddy lunch or coffee with the buddy
2026-11-02 IT sign-in to every account checked
2026-11-04 the head baker the role explained: what good looks like at 30, 60, 90 days
2026-11-06 the head baker first real piece of work handed over, small and finishable
2026-11-09 buddy end of week one: what was confusing
2026-11-20 people team paperwork and policies complete
2026-12-14 the head baker 30-day conversation: what is working, what is not
2027-01-25 the head baker 60-day conversation: owning a piece of work end to end
2027-03-08 the head baker 90-day conversation: the role, agreed for the next quarter
written: plan.csv · 14 items
check · OWNERS, DATES, A BUDDY, REAL WORK IN WEEK ONE, THE THIRTY-DAY CONVERSATION
$ python3 scripts/starter.py check plan.csv
14 items · the plan has what a first ninety days needs
due · WHAT IS DUE OR OVERDUE, BY OWNER
$ python3 scripts/starter.py due plan.csv --today 2026-11-03
IT equipment ordered and set up · 8 days overdue
IT accounts made: email, chat, the tools of the role · 8 days overdue
IT sign-in to every account checked · 1 day overdue
buddy lunch or coffee with the buddy · 1 day overdue
the head baker buddy named and told · 6 days overdue
the head baker welcome note sent with the first-day plan · 5 days overdue
the head baker first-day welcome: the team, the space, the plan · 1 day overdue
7 items due or overdue on 2026-11-03
(a thin plan written by hand)
$ (a thin plan written by hand)
check · OWNERS, DATES, A BUDDY, REAL WORK IN WEEK ONE, THE THIRTY-DAY CONVERSATION
$ python3 scripts/starter.py check thin-plan.csv
row 2 · no owner · first-day welcome
missing · a buddy named
missing · real work in the first week
missing · a 30-day conversation
missing · accounts made before day one
2 items · 5 to mend
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 --role --start · ninety days, owned. It asks first for the role, the first day, and the manager's role.
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 plan is a template for a desk role; a role on shifts, in the field or part-time needs its own items. The card keeps no personal details of the starter or anyone else — paperwork lives in the people team's own system. Not legal or employment advice: what a starter must sign, and when, is local law's.
What will it never do?
It will never leave a first-day item without an owner; never plan a first week with no real work; never keep anyone's personal details.
