THE STATION CARD · a brand's site as one ship of decks
WAKES WHEN someone wants a site built as decks of a ship, from one roster file where the crew lives
THE LOOP
law · the eleven clauses of the deck law
roster · write it; check it until clean
build · the station, one file
qr · a pass for each dock code
split · the heavy scene; then the gate
NEVER
Rebuild the studio's own station or crew
Hand-write a list the roster can emit
Type a price into a station
IT MAKES law — THE DECK LAW, eleven clauses; roster — every finding, or clean; build — the station, one file, from the roster; qr — a QR pass, read back; split — the static and actor layers.
THE STANDARD the roster is the truth; generate, never hand-write; nobody is better; one door; the studio's station is sealed; the gate decides.
PROOF SELFTEST 8/8 · witnessed in Claude 2026-10-11 · 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 · E5635291411FED2C9239B03C
CITE THIS CARDTHE STATION CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=station-card. Punch E5635291411FED2C9239B03C. Retrieved 2026-10-11.
What it is.
The Station's build method as a card, for anyone building their own brand a site in this style. law gives THE DECK LAW, eleven clauses (one page of numbered decks, a front deck that turns, one door for every buy control, a heavy scene shipped cheap, a phone budget with a lifeboat, arrivals by QR, the crew as data, the gate). roster checks a roster file (keys, colours, ink that reads at 4.5:1, every member's stats summing to one constant, cases, dock codes); build writes a single-file station from it: the front deck, the rack, the stand with dossiers, the open cases, the elements, the questions, the cart drawer, docking passes, booth mode and the lifeboat; qr makes a docking pass's QR code and reads it back; split cuts a heavy SVG scene into a static layer and actor layers, filters out.
It carries a machine that shows its working: law — THE DECK LAW, eleven clauses; roster — every finding, or clean; build — the station, one file, from the roster; qr — a QR pass, read back; split — the static and actor layers — 8 checks in its selftest, every command on the record. It will never rebuild the studio's own station or crew; never hand-write a list the roster can emit; never type a price into a station.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
THE ROSTER IS THE TRUTHThe buyer's roster file is the source; nothing is built from a roster with a finding open.
GENERATE, NEVER HAND-WRITEEvery list the roster can emit is built from it, so a colour added appears everywhere.
NOBODY IS BETTEREvery member's three stats sum to one constant; only different, never better.
ONE DOOREvery buy control calls one function into one cart; no price is typed, the store sets it at checkout.
THE STUDIO'S STATION IS SEALEDIts crew, names, art, lore and copy are not in this card; build the buyer's from the buyer's roster.
THE GATE DECIDESNothing ships unless the gate says so (THE ARMADA CARD), and a pass is read back before it is printed.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-BUILD.md
THE MACHINEstation.py · five commandslaw — THE DECK LAW, eleven clauses; roster — every finding, or clean; build — the station, one file, from the roster; qr — a QR pass, read back; split — the static and actor layers. 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.
law THE DECK LAW, eleven clauses
roster Every finding, or clean
build The station, one file, from the roster
qr A QR pass, read back
split The static and actor layers
On the record A three-crew roster sums to 10 for every member and is clean (its price set aside), and builds a one-file station with four buy controls through one door; a member summing to 15 and a capitalised dock code are caught and nothing is built; a docking pass encodes at version 3 and reads back, and 130 bytes at level H are refused (at most 119); a two-floor scene splits into a static layer and two actor layers with both filters out and the fast loop stepped.
What it will never do.
It will never rebuild the studio's own station or crew; never hand-write a list the roster can emit; never type a price into a station.
A rebuild of the Sep 8 2026 card from its record, one machine where the first cut carried several: the deck law, the recipe and the roster are the record's; build writes a smaller station than the first generator (six decks on a white page, no animated building, no theme files); the theme baker, the worker and the gate are not in this machine. QR codes are byte mode, versions 1 to 10, checked by the card's own reader, so scan one printed pass first. split finds what moves by animation elements and CSS animation rules, and leaves the neon blur's stroked twin to the builder. A method and a tool, not a certification. 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-BUILD.md — the guide in references/, in the card's own voice
scripts/station.py — the machine: law · roster · build · qr · split, 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 · 5 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-11 · EDITION 1 · PUNCH E5635291411FED2C9239B03C
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º 1165 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-11
station.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.
law
THE DECK LAW, eleven clauses
roster
every finding, or clean
build
the station, one file, from the roster
qr
a QR pass, read back
split
the static and actor layers
selftest
8 checks that prove the machine; it must print 8/8
law · THE DECK LAW, ELEVEN CLAUSES
$ python3 scripts/station.py law
THE DECK LAW · eleven clauses, for any crew, any product, any name
1 · One page, many decks. The home page is the whole ship: numbered decks, each a section with its own hash route; any standalone page can also be reached as a twin of the home page (/?view=<name>), so nothing waits on an admin making pages.
2 · The front deck turns. Three decks under one roof (the product, the humans, the faces) take turns on a clock; a dial pins one; ?hero= overrides. The buy button stays above the fold.
3 · One door. Every buy control (menu, front deck, rack, product page, an arrival by ?add=) calls one function that adds and opens the cart; the cart is a drawer with checkout pinned to its foot; express-pay scripts never load on phones.
4 · One grammar for buying. Every buy control speaks the same states (live, dropping, sold, gone); scarcity is counted from stock, never invented. A control that lies about stock is a defect.
5 · Rotation. Content turns on clocks the visitor cannot see: the day, the band of the day, the visit count; a seeded offer never repeats within a visit.
6 · A heavy scene, cheaply. A big animated scene ships inert behind a same-shape skeleton, is stamped on approach and rests off-screen; it is split into a static layer painted once and actor layers of only what moves, filters out, fast loops in steps.
7 · Low orbit. Under 640 px wide: a still sky, no blur, no filters on product photos, lazy decks, no provider scripts. A page that dies twice comes up the third time in the lifeboat, with a way back on screen.
8 · Arrivals. ?dock=<code> shows a pass once (the QR on the table); ?booth=1 is kiosk mode with a 90-second reset; ?add= lands in the cart; ?lifeboat=1 is the minimal deck; ?fullstation=1 clears it.
9 · The crew is data. One roster file drives every list: the rack, the faces, the stand, the cases, the elements, the passes. Add a colour and it appears everywhere. Stats sum to one constant: nobody is better, only different.
10 · The voice. Kickers in capitals with deck numbers; no maker's name but the manufacturer's; the signature number lives in the product's name, never claimed on the object; every page, the 404 too, wears the mark.
11 · The gate. Nothing ships unless the gate says so (THE ARMADA CARD): every template on every screen, the visitor's walk on every device, the one-door law on every control.
roster · EVERY FINDING, OR CLEAN
$ python3 scripts/station.py roster orchard.json
note · product.price is set aside: the store sets the price at checkout and the station never types one
roster clean · 3 crew · 1 inbound · 1 unverified · every member's three stats sum to 10 · 3 dock codes
roster · EVERY FINDING, OR CLEAN
$ python3 scripts/station.py roster broken.json
FINDING · the stats do not sum to one constant (green 10, red 10, yellow 15): nobody may be better, only different
FINDING · dock codes are lower-case words like expo, for ?dock=expo
note · product.price is set aside: the store sets the price at checkout and the station never types one
2 findings: nothing is built from this roster until it is clean
build · THE STATION, ONE FILE, FROM THE ROSTER
$ python3 scripts/station.py build orchard.json --out orchard.html
note · product.price is set aside: the store sets the price at checkout and the station never types one
orchard.html written: 12,546 bytes, one file · 3 crew on the rack, 1 inbound, 1 unverified
six decks: arrivals, the rack, the stand, the cases, the elements, questions · 4 buy controls, one door
arrivals: ?add=v-<key>, ?dock=<code> (3 codes), ?booth=1, ?lifeboat=1, ?hero=product|humans|faces
the gate comes next: nothing ships until it says so (THE ARMADA CARD)
build · THE STATION, ONE FILE, FROM THE ROSTER
$ python3 scripts/station.py build broken.json --out broken.html
refused: the roster has 2 findings; run roster and fix it first: the stats do not sum to one constant (green 10, red 10, yellow 15): nobody may be better, only different
qr · A QR PASS, READ BACK
$ python3 scripts/station.py qr "the orchard pass ?dock=expo" --out pass.svg
pass.svg written: version 3, 29 × 29 modules plus a quiet zone of 4, level M, mask 0
read back by the card's own reader: "the orchard pass ?dock=expo" · every block's check bytes agree
a check by its own reader, not a phone: scan one printed pass before printing the run
qr · A QR PASS, READ BACK
$ python3 scripts/station.py qr "<130 letters>" --out long.svg --ec H
refused: too long: at most 119 bytes at level H in this machine (versions 1 to 10); this is 130
split · THE STATIC AND ACTOR LAYERS
$ python3 scripts/station.py split scene.svg --out layers --css theme.css
static.svg: 259 bytes, painted once, 0 animations left in it
actors-garage.svg: only what moves on garage
actors-field-house.svg: only what moves on field-house
2 actors · 2 filters taken out · 1 fast loop turned to steps
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?
Law · the eleven clauses of the deck law. It asks first for the brand, the product and its crew as a roster (or three sentences to write one from), the dock codes, and any heavy SVG scene.
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. A rebuild of the Sep 8 2026 card from its record, one machine where the first cut carried several: the deck law, the recipe and the roster are the record's; build writes a smaller station than the first generator (six decks on a white page, no animated building, no theme files); the theme baker, the worker and the gate are not in this machine. QR codes are byte mode, versions 1 to 10, checked by the card's own reader, so scan one printed pass first. split finds what moves by animation elements and CSS animation rules, and leaves the neon blur's stroked twin to the builder. A method and a tool, not a certification.
What will it never do?
It will never rebuild the studio's own station or crew; never hand-write a list the roster can emit; never type a price into a station.
