THE HOME GROUND · THE MARKET ROW · Nº 1225 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE HOME GROUNDNº 1225

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE MAKER'S DROP · A product drop with honest scarcity: holds numbered, limits kept, only the true count said.

WAKES WHEN A maker opens holds for a limited drop. · Marketing copy says 'only a few left' and needs checking. · The drop is over and needs its report.

THE LOOP

Take holds in order, inside the limits
Show only the true remaining count
Release holds that lapse
Check the copy and report the drop

NEVER

Never states scarcity the counter can't back
Never holds past the units or the limit
Never takes payment

IT MAKES hold — add a hold with the next hold number; refuses before opens_at, past the units left or past the per-person limit; counter — the true remaining count per SKU and for the drop; release — mark held (unpaid) holds older than H hours as released; report — held, paid, released, sell-through, and time to sell out if it did; check-copy — flag scarcity claims the counter cannot support, in digits or words (one to twenty, "a couple"), and vague ones ("a few", "limited") as VAGUE; a line naming a SKU (its code, or a name in drop.json "names") is checked against that SKU, any other line against --sku or the whole drop (FILE: a .csv copy deck with a text column, or plain text); export — drop, counter and holds as JSON.

THE LAW Scarcity is a count, not a mood. The only scarcity words the card will write are the true remaining number, and it checks the maker's copy for claims the counter cannot back.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/drop.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 19/19 · 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 · 53A49CC226C5B097D280B68C

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

THE MAKER'S DROP

A product drop with honest scarcity: holds numbered, limits kept, only the true count said.

HOLD · COUNTER · RELEASE · REPORT · CHECK-COPY · 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/drop.py · 6 commands · selftest 19/19
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: 53A49CC226C5B097D280B68C · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE MAKER'S DROP, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=makers-drop-card. Punch 53A49CC226C5B097D280B68C. Retrieved 2026-10-13.

What it is.

Use when a maker runs a limited drop or presale: numbered holds, per-person limits, the true remaining count, and checking copy for scarcity claims. Not for taking payment.

It carries a machine that shows its working: hold — add a hold with the next hold number; refuses before opens_at, past the units left or past the per-person limit; counter — the true remaining count per SKU and for the drop; release — mark held (unpaid) holds older than H hours as released; report — held, paid, released, sell-through, and time to sell out if it did; check-copy — flag scarcity claims the counter cannot support, in digits or words (one to twenty, "a couple"), and vague ones ("a few", "limited") as VAGUE; a line naming a SKU (its code, or a name in drop.json "names") is checked against that SKU, any other line against --sku or the whole drop (FILE: a .csv copy deck with a text column, or plain text); export — drop, counter and holds as JSON — 19 checks in its selftest. It never states scarcity the counter can't back; never holds past the units or the limit; never takes payment.

The law, written into the card.

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

THE LAWScarcity is a count, not a mood. The only scarcity words the card will write are the true remaining number, and it checks the maker's copy for claims the counter cannot back.

The method.

Set the drop: when it opens, units by SKU and the per-person limit.
Take holds in order and number them. A hold past the units remaining or past a person's limit is refused.
Show the counter: units minus held minus paid. That number is the only scarcity the card states.
Release holds that lapse.
Check marketing copy for scarcity claims and set every number in it against the counter.
Report the drop: held, paid, released, sell-through and time to sell out.

What you bring.

Your units by SKU and the per-person limit.
Your hold list.
Your marketing copy, to check.

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

What it does once your AI has it.

hold Add a hold with the next hold number; refuses before opens_at, past the units left or past the per-person limit
counter The true remaining count per SKU and for the drop
release Mark held (unpaid) holds older than H hours as released
report Held, paid, released, sell-through, and time to sell out if it did
check-copy Flag scarcity claims the counter cannot support, in digits or words (one to twenty, "a couple"), and vague ones ("a few", "limited") as VAGUE; a line naming a SKU (its code, or a name in drop.json "names") is checked against that SKU, any other line against --sku or the whole drop (FILE: a .csv copy deck with a text column, or plain text)
export Drop, counter and holds as JSON

What it will never do.

It never states scarcity the counter can't back; never holds past the units or the limit; never takes payment.

Where it hands off: Taking payment → your store's checkout; Product codes → THE VESSEL KEY; Booth selling → THE EXPO BOOTH.

It is not legal advice. 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/drop.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 legal advice).

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

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º 1225 — 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

drop.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.

`hold`	add a hold with the next hold number; refuses before opens_at, past the units left or past the per-person limit
`counter`	the true remaining count per SKU and for the drop
`release`	mark held (unpaid) holds older than H hours as released
`report`	held, paid, released, sell-through, and time to sell out if it did
`check-copy`	flag scarcity claims the counter cannot support, in digits or words (one to twenty, "a couple"), and vague ones ("a few", "limited") as VAGUE; a line naming a SKU (its code, or a name in drop.json "names") is checked against that SKU, any other line against --sku or the whole drop (FILE: a .csv copy deck with a text column, or plain text)
`export`	drop, counter and holds as JSON
`selftest`	19 checks that prove the machine; it must print selftest 19/19

THE SELFTEST, AS PRINTED

ok  1  hold assigns hold numbers 1 then 2 and writes holds.csv beside drop.json
ok  2  hold refuses before opens_at
ok  3  hold refuses past the units left (B: 0 left)
ok  4  hold refuses past the per-person limit (p1 holds 2, limit 3)
ok  5  hold rejects a SKU not in the drop with exit 2
ok  6  counter: remaining = units - held - paid; released units come back (A 3 left, B 0 left)
ok  7  report: B sold out 20m after opening; A NOT SOLD OUT; sell-through B 100.0%
ok  8  release frees the old unpaid hold, never the paid one, and keeps '#' notes
ok  9  check-copy flags 'only 2 left' when the counter says 5
ok  10  check-copy flags 'selling fast', 'last chance' and a bare 'limited'
ok  11  check-copy supports true numbers ('5 left', 'limited to 7') and counts them
ok  12  check-copy passes clean copy with a true 'sold out' (exit 0)
ok  13  check-copy reads a .csv copy deck and names the row and place
ok  14  'Three left!' is read as 3 and flagged when the counter says 7
ok  15  'Only a handful remain!' is flagged VAGUE with the true count
ok  16  'Sand is sold out.' (no --sku) is checked against SCT-SAND, 0 left, and passes
ok  17  a true '7 left' passes; 2 supported, 2 flagged in all
ok  18  names for a SKU not in units is bad input (exit 2)
ok  19  export gives the same bytes twice
selftest 19/19

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 units by SKU and the per-person limit. Your hold list. Your marketing copy, to check. 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 (19/19), 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 legal advice.

What will it never do?

It never states scarcity the counter can't back; never holds past the units or the limit; never takes payment.

← THE HOME GROUND · THE FLOOR →