THE HOUSE · THE STANDARD · READ BEFORE YOU BUY
The standard every card meets.
What a card is and is not, how it is scored and proven, where it runs, what it costs you in trust, and what the studio will never do. Ten minutes to evaluate any card against it. Lund Studio LLC, Westminster, Colorado.
1 · What a card is
A card is a packet of files you give to the AI you already use. It is not software you install on a server and not a service you subscribe to. Every card on this site is cut to one anatomy, LSC-1: a door the AI reads first (SKILL.md), the card itself (CARD.md: who it is, its laws, its loop, when it says no, what it carries), references in the card’s own voice, a machine where one is warranted (one standard-library Python script with a self-test), and the papers — the tin, the clauses, the licence note, the ledger the card keeps on your machine, and a manifest with every file hashed.
2 · The seal
Every card is scored on THE HUNDRED, five criteria out of five, from evidence: Trigger (does the door say when to use it, in the third person, with a role), Machinery (is there a machine, does its self-test pass when run here, is every command on the witnessed record), Law (is the anatomy whole, with references, the laws and the limit), Portability (standard library, no network, a door for every host), Proof (the witnessed run, the punch, the manifest). Four times the sum, capped at 98: LEGENDARY from 92, EPIC from 68, COMMON below. A card’s seal and its five criteria are printed on its room. The scale, in full →
3 · Proof on the record
A machine card ships WITNESS.md: its self-test and its commands run on real inputs, pasted as they printed, dated. The punch on the face is the first 96 bits of the SHA-256 of SKILL.md; the room prints it, the register lists it, and any downloaded file can be checked against it in the browser, offline. Figures in the runs that are invented for the record are marked FAKE; published figures are named with their sources.
The studio seal
Since 12.357.91 every punch a room prints is signed by the studio’s own key. The private half is held by the studio, off every server; the public half is printed here and carried in the theme. Under the punch check in every room the browser reads the signature on record for that punch and verifies it with WebCrypto — STUDIO SEAL · VERIFIED, FAILS or NONE ON RECORD — and nothing leaves the machine. A room that prints a punch with no seal on record, or a seal that fails, is not the studio’s.
- Key
LS-SEAL-1 · Ed25519 · 521E24D4311293F9B186827FAE7B670394BED32D62546BEECEBD9F18F308A6E4- Signed
- the bytes
LUNDR STUDIO SEAL v1, a newline, then the 24-hex punch as the room prints it - Index
- the-seal.json — 1,183 signatures at build 12.357.101, one for every punch on the floor, with the key
- Register
- the register is a hash chain: its rows oldest first, each link the SHA-256 of the previous link and the row’s Nº, card, handle, edition and punch (price, check and till left out, they change when a card is cleared). 994 rows · head
DD07B120371A65E318FF1C679AD9F0F141F8E91594027B92066239DE4F5EF44E· signed with the key above. Every build signs its head; a changed, removed or re-cut row moves it. - Offline
seal.pyin the build’s tools verifies the index and the chain with the standard library alone, and any Ed25519 library does the same with the key above.
What the seal proves and what it does not. It proves the studio signed this punch. It does not score the card — the scale in section 2 does that — and it does not make a file good. A copied card changes its SKILL.md, so it changes its punch, and no seal on record matches it; a card that keeps the punch is byte for byte the studio’s file.
4 · Where it runs
The words run wherever an AI reads a text file. The machine runs on your own computer: Python’s standard library only, no third-party package, no network call, no account, no key, no telemetry. Nothing in a packet sends anything anywhere. Where a card declares a reach — a test harness that starts a command line, a query it writes for you to open — the reach is named on its face and its room.
5 · Hosts
Each packet carries HOSTS.md, a door for each host: Claude (the app, desktop and mobile), Claude Code, ChatGPT (a Project or a GPT), Gemini (a Gem), and any other AI by its system prompt. Those names are the hosts’ own; no affiliation is claimed and none should be read in. The card never assumes a tool by name; it works with what the host has and says what it could not run.
6 · Licence and editions
One payment, one person, any number of their own AIs and computers. No resale, no redistribution, no sublicence. Editions replace files; nothing renews itself and nobody is charged again. When a term ends, the files on your computer stay readable — freeze, not loss. THE-CLAUSES.md rides in every packet and is part of the licence: an AI can be wrong; your work and your decisions are yours; nothing hidden, nothing kept; third-party services are their own companies’; no promise of a result; not legal, tax, medical or financial advice. The terms, in plain words →
7 · Security posture
Before a packet ships, THE PACKET WATCH reads it: what its machine reaches for (the network, a shell, eval, the home folder, deletes), what rides in its files (a secret, a key, a build path, a price, a forbidden word), what the zip itself does, and whether the punch agrees with the record. A packet that fails is held and read by hand. You can run the same gate yourself on anything you download — ours or anyone’s — with THE PACKET SCAN CARD, which reads a packet without running it and says, on every verdict, that a pass is not a proof.
8 · What the studio never does
- Never names, imitates or profiles a real person — no name, likeness, title, employer or private detail, anywhere in a card or a room.
- Never types a secret, a key, a price or a build path into a packet.
- Never helps make, grow, enhance or spread a pathogen or a toxin; never weapon, missile or attack help; never a bypass of a scanner or a watermark.
- Never writes a line it has not measured: a trigger line is proven by running the same prompts again on every model it is sold for (the field report).
- Never calls a card safe, certified or a substitute for a professional: it sits at your elbow, never the boss.
9 · Evaluate a card in ten minutes
- Open the room. Read the spec sheet: the seal and its five criteria, the edition, the machine, the punch.
- Read What it will never do and the laws. If a line you need is missing, the card is not for you.
- Download the packet. Run
python3 scripts/<machine>.py selftest; it must print the number the room prints. - Check the punch: drop the file on the punch check, or hash
SKILL.mdyourself. - Open
WITNESS.md. The runs are pasted as printed; compare one against the machine on your own input. - Scan it with THE PACKET SCAN CARD, or any scanner you trust.
- Give it to your AI and say the card’s name. THE WELCOME TEAM, free with every package, walks the first run with you.
- Tell the studio how it did: the line back takes under a minute and feeds the next edition.
A card against the alternatives
| a card | a SaaS tool | a prompt you wrote | |
|---|---|---|---|
| Where it runs | your own AI and your own computer | the vendor's servers | your own AI |
| Your data | stays where it is; nothing is sent | uploaded, under the vendor's terms | stays with your AI provider |
| Proof it works | self-test and witnessed runs in the packet; the punch; the seal | the vendor's word, a demo, a trial | none until you test it |
| What breaks when the vendor changes | nothing; the files are yours at their edition | the tool, the price, the terms | nothing, but nothing is maintained either |
| Lock-in | none: text and one standard-library script | the account, the export, the integrations | none |
| Cost model | one payment; editions replace files; nothing renews | a subscription per seat per month | your time |
| Who can change it | you, in a text editor; the studio by edition | the vendor | you |
| What it cannot do | run on its own, call a service, be a certificate | work offline, show its working, stay the same | carry a machine, a test or a record |
10 · Teams and procurement
A seat is one person. For a team, buy one seat per person, or write to the studio through the store’s contact page for team terms, an invoice, or a written agreement; nothing on this site is priced for a team by default and no price is typed in a packet. Every purchase is delivered digitally with a receipt; the register on this site lists every card with its punch so an auditor can tie a file to its room. The studio is Lund Studio LLC, Westminster, Colorado.
Team terms, an invoice, a written agreement
A seat is one person. For a team, a purchase order, an invoice, or an agreement with your own terms, write to the studio through the store's own contact form; nothing else is collected and no price is typed here. One reply, from the studio.
The sheet, in one table
| A card is | a packet of text and one standard-library script, read by the AI you already use |
|---|---|
| A card is not | a model, an app, a server, a subscription, a certificate, or advice |
| It sends | nothing, anywhere |
| It needs | an AI that reads a file; Python 3 for the machine |
| It is proven by | its self-test, its witnessed runs, its punch, its manifest — all in the packet |
| It is scored by | THE HUNDRED, five criteria from evidence, printed on the room |
| It is licensed to | one person, on any number of their own AIs and computers |
| It can be wrong | yes — it is an AI reading a text file; check what matters against your own records and the source |