LUND CARDS · OUTSIDE THE DECKNº — PROPOSED
THE CARD AS TEXT · FOR EYES AND FOR MACHINES
THE SAMAN CARD · One build from many layers
WAKES WHEN Two or more backend layers must become one deployable: one migration in order, one Worker entry in precedence, one composed client, one total proof.
THE LOOP
- Name the card · ask which build and what it must agree with
- build.json: layers in order, precedence, erase[], auth, cron, hooks, tests
- assemble → prove on a FRESH database → cascade
- read PROOF.md and CASCADE.md · fix UNCOVERED · hand over saman-out/
NEVER
- Guess an order
- Say PROVEN without suites
- Hand-patch a generated file
- Deploy
- Hand off: a deploy, a live database and every credential stay with the builder
IN THE BOX
- saman.mjs · assemble · prove · cascade · selftest 9/9
- audit.py · twelve checks
- a two-layer fixture
- the SideRep build's shape as the worked example
PROOF WITNESSED IN CLAUDE 2026-09-14 — six layers assembled, 17 tables on a fresh database, 212 passed 0 failed, 16 tables covered, 0 uncovered.
THE PUNCH · SHA-256 OF SKILL.MD · 29ED06D4F1D438F1B1C9BFD1
THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →
THE SAMAN CARD
One build from many layers
MANY LAYERS · ONE BUILD · ONE PROOF
LEGENDARYWITNESSEDIN CLAUDEIN LUNDRIN CHATGPT
WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →
What it is.
One build from many backend layers. Give it N layers — each with a schema, a worker module, a client and a suite — and a build.json naming their order, and SAMAN writes the combined migration, the unified Worker entry, the composed client and the wrangler file, then proves the whole on a fresh database: every suite run, every user-bearing table checked for erasure coverage. It assembles and proves; it does not deploy, and it proves only what your suites test.
WAKES WHEN Two or more backend layers must become one deployable: one migration in order, one Worker entry in precedence, one composed client, one total proof.
The loop.
- Name the card · ask which build and what it must agree with
- build.json: layers in order, precedence, erase[], auth, cron, hooks, tests
- assemble → prove on a FRESH database → cascade
- read PROOF.md and CASCADE.md · fix UNCOVERED · hand over saman-out/
It makes.
- one combined migration, in the manifest's dependency order
- one Worker entry, webhooks first, then the layers in precedence
- one composed client
- PROOF.md — every suite run on a fresh database — and CASCADE.md — every user-bearing table covered
Never.
- Guess an order
- Say PROVEN without suites
- Hand-patch a generated file
- Deploy
- Hand off: a deploy, a live database and every credential stay with the builder
What’s in the buy.
- scripts/saman.mjs — assemble · prove · cascade · selftest 9/9 · scripts/audit.py — the twelve checks
- assets/fixture — a two-layer build to run first · assets/saman.siderep.json — a six-layer build’s shape as the worked example (the shape only; no layer source)
- CARD.md + SKILL.md · TIN · LICENCE + LEDGER · MANIFEST, every file hashed · AUDIT, the twelve checks · the two faces, card.json, card.html · the doors for other hosts
YOU NEED Node 22.5 or later; your own layers (schema, worker module, client and suite each); a build.json naming their order.
PROOF · WITNESSED IN CLAUDE 2026-09-14 — six layers assembled, 17 tables on a fresh database, 212 passed 0 failed, 16 tables covered, 0 uncovered. · PUNCH 29ED06D4F1D438F1B1C9BFD1
ON EVERY DOOR · A CARD FOR YOUR AI, A FILE FOR YOUR COMPUTER
This card is an Agent Skill on the open standard: the same folder loads unmodified in Claude, ChatGPT and Codex, Copilot and VS Code, Cursor, Gemini CLI, Goose, OpenCode and the rest of the showcase. Its words are Markdown, so any chat with an instructions box holds them, any local model runs them offline, and any MCP client can load them — the doors ride in this card’s box. And card.html — the card as one file for your computer: both faces, the tin, the words, every door; offline, in any browser. The host marks →
Take it.
Nº — 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 legal, tax, medical or financial advice, and not a licence to practise. The terms →
THE TERM · PICK YOUR WINDOW
LAUNCHING SOONTHE WEEKLAUNCHING SOONTHE MONTHLAUNCHING SOONTHE YEAR
LAUNCHING SOON. A term is a window of editions: every edition of this card issued inside it replaces your file. When the window closes, the file you hold keeps working — freeze, not loss. Nothing auto-renews.
← THE ENGINES · THE SHELF, RANKED · THE DECK