THE HOME GROUND · THE MEETING HOUSE · Nº 1236 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE HOME GROUNDNº 1236

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE REGIONAL LAUNCH · One region's launch of a network, counted by weekly active users and the follow-ups that are due.

WAKES WHEN An operator is launching a network in a new region. · Someone asks how this week's active users compare with the goal. · Outreach follow-ups are slipping.

THE LOOP

Count weekly active users from activity
Board the weeks against the goal
List follow-ups that are due
Write the weekly report

NEVER

Never projects or forecasts
Never counts activity not recorded
Never drops a follow-up without a contact

IT MAKES wau — distinct users with recorded activity in that ISO week; board — WAU per week vs the goal, % of goal, best week, a text bar chart (the last --weeks weeks up to --today, not before start_week); follow-ups — outreach whose next_by has passed and that no later contact with the same person has superseded; report — the weekly report: WAU, change from the week before, outreach done, follow-ups due; export — goal, weekly WAU series and outreach as one JSON document.

THE LAW Count what happened. Weekly active users are distinct people with recorded activity in the week, and the board shows them against the goal without projections.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/regionop.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (8 tests) · references/ (schema + fictional demo) · START-HERE.md · system/ doors · MY-LEDGER.md · LICENSE-NOTE.md · card.svg · card.json · card.html · AUDIT.md · MANIFEST.md · WITNESS.md · SELFTEST.md.

PROOF SELFTEST 13/13 · witnessed in Claude 2026-10-13 on fictional fixtures · the test prompts in fresh chats owed · Edition 1.

THE SEAL 96 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 4

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. LICENSE-NOTE.md rides in the packet and is the licence.

THE PUNCH · SHA-256 OF SKILL.MD · 631B963D8034D90CD9DC9980

THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →

THE REGIONAL LAUNCH

One region's launch of a network, counted by weekly active users and the follow-ups that are due.

WAU · BOARD · FOLLOW-UPS · REPORT · EXPORT

LEGENDARYWITNESSEDIN CLAUDE IN LUNDR IN CHATGPT

WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →

THE SPEC SHEET · READ BEFORE YOU BUY · THE STANDARD EVERY CARD MEETS →

SEAL: 96 of 100 · LEGENDARY · WITNESSED
EDITION: E1 · witnessed 2026-10-13
MACHINE: scripts/regionop.py · 5 commands · selftest 13/13
RUNS: On your own computer. Standard library only, offline; no account, no key, no telemetry.
HOSTS: Claude · Claude Code · ChatGPT · Gemini · any AI that reads a file (START-HERE.md and system/ name each door)
LICENCE: One person, any number of their own AIs and computers · editions replace files · nothing renews · freeze, not loss
PUNCH: 631B963D8034D90CD9DC9980 · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE REGIONAL LAUNCH, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=regional-launch-card. Punch 631B963D8034D90CD9DC9980. Retrieved 2026-10-13.

What it is.

Use when an operator launches a network in one region and tracks weekly active users against a goal, plus outreach and follow-ups. Not for forecasts or projections.

It carries a machine that shows its working: wau — distinct users with recorded activity in that ISO week; board — WAU per week vs the goal, % of goal, best week, a text bar chart (the last --weeks weeks up to --today, not before start_week); follow-ups — outreach whose next_by has passed and that no later contact with the same person has superseded; report — the weekly report: WAU, change from the week before, outreach done, follow-ups due; export — goal, weekly WAU series and outreach as one JSON document — 13 checks in its selftest. It never projects or forecasts; never counts activity not recorded; never drops a follow-up without a contact.

The law, written into the card.

It is in the card itself, so the AI follows it.

THE LAWCount what happened. Weekly active users are distinct people with recorded activity in the week, and the board shows them against the goal without projections.

The method.

Set the region's goal and start week.
Count weekly active users: distinct people with at least one recorded activity in the ISO week. Weeks past the log print NOT IN LOG; the current week prints PARTIAL.
Board the weeks against the goal with the percentage and a plain bar.
List outreach follow-ups whose date has passed and that no later contact has answered.
Write the weekly report: active users, change, outreach done, follow-ups due.

What you bring.

Your region's goal and start week.
Your activity log.
Your outreach log.

Nothing of the studio's is needed; the data is yours.

What it does once your AI has it.

wau Distinct users with recorded activity in that ISO week
board WAU per week vs the goal, % of goal, best week, a text bar chart (the last --weeks weeks up to --today, not before start_week)
follow-ups Outreach whose next_by has passed and that no later contact with the same person has superseded
report The weekly report: WAU, change from the week before, outreach done, follow-ups due
export Goal, weekly WAU series and outreach as one JSON document

What it will never do.

It never projects or forecasts; never counts activity not recorded; never drops a follow-up without a contact.

Where it hands off: Volunteer events → THE VOLUNTEER DAY; Local partners → THE LOCAL BENCH; Forecasts → an analyst.

It is not a forecast. It is an AI reading a text file: it can be wrong, so check what matters against your own records and the source. The holder brings their own AI; no endorsement by Anthropic or any other AI company is claimed.

What’s in the buy.

SKILL.md — the card your AI reads: when it wakes, the loop, the never-lines, the hand-offs.
CARD.md — the whole card in ten sections: face, law, method, machine, what you bring, never, tests, seal, term.
scripts/regionop.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
tests/EVALS.json and scripts/evals.py — 8 test prompts and the offline runner that scores your AI's answers.
references/ — the data schema and FICTIONAL demo files, invented to show the machine, not real.
MY-LEDGER.md — your own record of what you asked and what you decided.
START-HERE.md, system/short-prompt.md, system/rules.md — the doors, for any AI with or without skills.
card.svg, card.json, card.html, AUDIT.md, MANIFEST.md, WITNESS.md, SELFTEST.md — the faces and the proof.
NOT IN THE BOX — nothing of the studio's is needed; the data is yours. Also not in the box: any data you must bring, and advice of any kind (not a forecast).

PROOF · SELFTEST 13/13 · WITNESSED IN CLAUDE 2026-10-13 ON FICTIONAL FIXTURES · THE TEST PROMPTS IN FRESH CHATS OWED · EDITION 1 · PUNCH 631B963D8034D90CD9DC9980

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º 1236 — 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 · NOTHING RENEWS ITSELF

OFFLINE · ONE LICENCE · PUNCH-CHECKABLE · THE STANDARD

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 CARD’S OWN SELFTEST.MD

regionop.py, every command showing its working.

A small Python program, standard library only. Your AI runs it; you can too. The block below is pasted from the card’s own SELFTEST.md, as printed when it was run from inside the packet.

`wau`	distinct users with recorded activity in that ISO week
`board`	WAU per week vs the goal, % of goal, best week, a text bar chart (the last --weeks weeks up to --today, not before start_week)
`follow-ups`	outreach whose next_by has passed and that no later contact with the same person has superseded
`report`	the weekly report: WAU, change from the week before, outreach done, follow-ups due
`export`	goal, weekly WAU series and outreach as one JSON document
`selftest`	13 checks that prove the machine; it must print selftest 13/13

THE SELFTEST, AS PRINTED

ok  1  wau: distinct users only (u1 active 3 days counts once); ISO week includes 2025-12-29
ok  2  wau: rows in other weeks never counted
ok  3  wau: a week after the log ends is NOT IN LOG, never 0
ok  4  board: % of goal, best week, bar with goal marker
ok  5  board: an empty week inside the log says 'no activity recorded'; later weeks NOT IN LOG
ok  6  board: the week in progress is marked PARTIAL and not used as best week
ok  7  board/report: no projection words anywhere
ok  8  follow-ups: overdue listed with days late; a later contact supersedes; blank next_by skipped
ok  9  follow-ups: next_by equal to today is DUE TODAY
ok  10  report: WAU, change from the week before, outreach done, follow-ups due by week end
ok  11  report: the start week says NO PRIOR WEEK
ok  12  export: JSON series stops at the log's end, same bytes twice
ok  13  bad input exits 2 (2025-W53 does not exist / bad format)
selftest 13/13

THE RUN IS PASTED FROM THE CARD’S OWN SELFTEST.MD AS PRINTED. ITS FIXTURES ARE FICTIONAL, INVENTED FOR THE TEST; NO PRIVATE PERSON IS NAMED.

QUESTIONS AT THE TABLE

Asked before the wire.

What does it need from me?

Your region's goal and start week. Your activity log. Your outreach log. If something it needs is missing, it says what is missing and stops there.

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 machine's selftest (13/13), run from inside the packet in Claude on 2026-10-13 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: The 8 test prompts asked in fresh chats with the card installed. Until they are run and scored, the tests are owed. Any run on real data. Every demo file is fictional. 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 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. LICENSE-NOTE.md rides in the packet and is the licence. It is not a forecast.

What will it never do?

It never projects or forecasts; never counts activity not recorded; never drops a follow-up without a contact.

← THE HOME GROUND · THE FLOOR →