THE HEADLESS PLATFORM CARD

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

SEAL

96 of 100 · LEGENDARY · WITNESSED

EDITION

E1 · witnessed 2026-10-13

MACHINE

scripts/headless.py · 4 commands · selftest 12/12

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

93B36427FC4538D9944B7F48 · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE HEADLESS PLATFORM CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=headless-platform-card. Punch 93B36427FC4538D9944B7F48. Retrieved 2026-10-13.COPY

What it is.

Use when a store or a catalogue needs to be served to any screen through a contract: a JSON feed, a check against it, and a front that reads it. Not for payments, themes or hosting.

It carries a machine that shows its working: contract — write the read-side contract: endpoints, fields, types, counts, a version from the catalogue; feed — cut the static JSON feed: products, one file per product, collections by tag, an index; check — check a feed against the contract; prints a flag per fault and exits 1 on any; front — write a single-file front: search, product pages, a browser cart; reads the feed, no key, no network beyond its own feed — 12 checks in its selftest. It never invents a price, stock or currency; never ships a key inside a front end; never calls a feed good before the check.

The law, written into the card.

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

The method.

1. Keep the catalogue as one plain CSV the person owns: a handle, a title, a price, a currency, a stock count, tags and a summary per row. The machine reads nothing else.
2. Write the contract first: every endpoint and what it returns, every field with its type and whether it is required, a version taken from the catalogue's own bytes. The front is built to the contract, never to a guess.
3. Cut the feed as static files any host can serve: one list, one file per product, one collection per tag, an index with the version. A missing price prints NO PRICE and the product is not sold; a repeated handle prints DUPLICATE HANDLE.
4. Check before anything goes live: fields, types, prices, currencies, every collection's handles, the version against the contract. Any fault is a line in capitals and exit 1; a passing check is the only green light.
5. Write the front as a single file that reads the feed: search, product pages, a cart in the browser tab, prices shown from the feed and never typed. Writes — a cart sent, an order, a payment — stay on a server behind a key that never rides in the front.

What you bring.

• Your catalogue as a CSV: handle, title, price, currency, stock, tags, summary, and an image path if you have one.
• A place to serve static files, or none: the front runs from disk with the feed inside it.
• Your own rule for what goes on sale: the machine marks what is not whole; you decide what to fix.

Planned as a separate seat, not in this box and not yet on sale: a feed and a front the studio runs for its own cards, from the same contract.

What it does once your AI has it.

• contract Write the read-side contract: endpoints, fields, types, counts, a version from the catalogue
• feed Cut the static JSON feed: products, one file per product, collections by tag, an index
• check Check a feed against the contract; prints a flag per fault and exits 1 on any
• front Write a single-file front: search, product pages, a browser cart; reads the feed, no key, no network beyond its own feed

What it will never do.

It never invents a price, stock or currency; never ships a key inside a front end; never calls a feed good before the check.

Where it hands off: Deciding whether the platform is ready to ship → THE GO-LIVE CARD; Reading the live pages before a launch → THE RELEASE READOUT; Taking money, orders and accounts → the store's own server-side systems, behind a key.

It is not a security guarantee. 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/headless.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 — any studio edition (planned, not yet on sale: a feed and a front the studio runs for its own cards, from the same contract). Also not in the box: any data you must bring, and advice of any kind (not a security guarantee).

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

Take it.

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.