THE INSTALLER · puts the card where your AI reads it
WAKES WHEN a card has to be put where an AI reads it, or an AI does not seem to see the card
THE LOOP
hosts · every door, which ones are here
place · the card into the host's folder
check · read back: door, machine, Python
say · the name, then what you have
hand over · to the first run
NEVER
Write outside the folder you point it at
Send anything anywhere
Change a card, or speak for one
IT MAKES hosts — every door, where a card goes in each, and which of the folder hosts exist on this computer; place — the card unpacked into the host's skills folder (a project's own, with --into); the exact path said; --dry only says; check — the placed card read back: the door's name and description, the machine's self-test run here, Python, the record — READY or NOT READY, and what to say to begin.
THE STANDARD every door named; only where you point it; read back before READY; dry first if you like; it hands over.
PROOF SELFTEST 9/9 · witnessed in Claude 2026-10-09 · 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 · 76A81396D6098C9EB880773B
CITE THIS CARDTHE INSTALLER, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=installer-card. Punch 76A81396D6098C9EB880773B. Retrieved 2026-10-10.
What it is.
Of THE WELCOME TEAM: it knows every door — the Claude app, Claude Code, Cursor, Codex, Gemini, ChatGPT, MCP hosts — says where a card goes in each, puts the card there for the hosts that take a folder, and reads it back to check it took: the door, the machine, Python, the self-test, and what to say to begin.
It carries a machine that shows its working: hosts — every door, where a card goes in each, and which of the folder hosts exist on this computer; place — the card unpacked into the host's skills folder (a project's own, with --into); the exact path said; --dry only says; check — the placed card read back: the door's name and description, the machine's self-test run here, Python, the record — READY or NOT READY, and what to say to begin — 9 checks in its selftest, every command on the record. It will never write outside the folder you point it at; never send anything anywhere; never change a card, or speak for one.
Five laws, written into the card.
They are in the card itself, so the AI follows them.
EVERY DOOR NAMEDThe hosts that take a folder, the ones that take an upload, the one that runs a server — each with where the card goes, plainly.
ONLY WHERE YOU POINT IT`place` writes into the one skills folder you chose and nowhere else, and never over a card already there unless you say --replace.
READ BACK BEFORE READYA placed card is READY only after its door, its machine and its self-test were read back on this computer.
DRY FIRST IF YOU LIKE`--dry` says exactly what would be written and writes nothing.
IT HANDS OVERREADY ends with the words to say to your AI and the name of the next of the team.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-DOORS.md
THE MACHINEinstaller.py · three commandshosts — every door, where a card goes in each, and which of the folder hosts exist on this computer; place — the card unpacked into the host's skills folder (a project's own, with --into); the exact path said; --dry only says; check — the placed card read back: the door's name and description, the machine's self-test run here, Python, the record — READY or NOT READY, and what to say to begin. Every command prints its working and refuses a bad input; 9 checks in its selftest, every command on the record.
What it does once your AI has it.
hosts Every door, where a card goes in each, and which of the folder hosts exist on this computer
place The card unpacked into the host's skills folder (a project's own, with --into); the exact path said; --dry only says
check The placed card read back: the door's name and description, the machine's self-test run here, Python, the record — READY or NOT READY, and what to say to begin
On the record Every door named with where a card goes; a dry run saying exactly where the card would land; the card placed in the project's own skills folder; a second placing refused; the placed card read back — the door, the machine's self-test run here, Python, the record — READY, with the words to say.
What it will never do.
It will never write outside the folder you point it at; never send anything anywhere; never change a card, or speak for one.
It places for the hosts that read a folder (Claude Code, a project); for the Claude app, ChatGPT and the rest it can only say where the upload goes. It reads your home folder's own skills folder to say whether it exists and nothing else there. 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 file.
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-DOORS.md — the guide in references/, in the card's own voice
scripts/installer.py — the machine: hosts · place · check, standard library only, selftest 9/9
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 9/9 · 3 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-09 · EDITION 1 · PUNCH 76A81396D6098C9EB880773B
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º 944 PROPOSED — FREE
Given as is under the clauses 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 →
FREE · TAKE IT NOW · NOTHING TO SIGN, NOTHING TO PAY
One file, installer-card.skill.zip. Upload it to Claude as it is — START-HERE.md inside walks you through it — or load its files in ChatGPT, Gemini or any AI. The whole team rides with every package the studio delivers and is free here; the newest edition is always in this room. No account, no email.
FREE, NOT A TRIAL: NOTHING TO RENEW, NOTHING TO CANCEL, NOBODY IS CHARGED. THE FILE STAYS ON YOUR COMPUTER AND STAYS READABLE — FREEZE, NOT LOSS.
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-09
installer.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.
hosts
every door, where a card goes in each, and which of the folder hosts exist on this computer
place
the card unpacked into the host's skills folder (a project's own, with --into); the exact path said; --dry only says
check
the placed card read back: the door's name and description, the machine's self-test run here, Python, the record — READY or NOT READY, and what to say to begin
selftest
9 checks that prove the machine; it must print 9/9
(a real card of the house, THE ROBOTAXI, and an empty project folder)
$ (a real card of the house, THE ROBOTAXI, and an empty project folder)
hosts · EVERY DOOR, WHERE A CARD GOES IN EACH, AND WHICH OF THE FOLDER HOSTS EXIST ON THIS COMPU
$ python3 scripts/installer.py hosts
THE DOORS · where a card goes, host by host
- Claude app · the .skill.zip as it is, where skills are added in the app's settings; nothing to unpack
- Claude Code · a folder per card in the skills folder: ~/.claude/skills/<handle>/ for every project, or <project>/.claude/skills/<handle>/ for one · ON THIS COMPUTER: the skills folder exists at ~/.claude/skills
- Cursor · rules/.cursorrules from the packet copied into the project as .cursorrules (or into .cursor/rules/), and the packet folder beside it
- Codex · rules/AGENTS.md from the packet copied into the project as AGENTS.md, and the packet folder beside it
- Gemini CLI · rules/GEMINI.md from the packet copied into the project as GEMINI.md, and the packet folder beside it
- ChatGPT · the packet's files uploaded into a project, with system/short-prompt.md pasted as the instructions
- MCP hosts · mcp/mcp_card.py run as a server; the host lists the card's commands as tools
Python here: 3.13.16 · Linux
place · THE CARD UNPACKED INTO THE HOST'S SKILLS FOLDER (A PROJECT'S OWN, WITH --INTO); THE EXAC
$ python3 scripts/installer.py place the-card.skill.zip --host project --into project --dry
would place THE ROBOTAXI · 25 files · at robotaxi-card
place · THE CARD UNPACKED INTO THE HOST'S SKILLS FOLDER (A PROJECT'S OWN, WITH --INTO); THE EXAC
$ python3 scripts/installer.py place the-card.skill.zip --host project --into project
placed THE ROBOTAXI · 25 files · at robotaxi-card
place · THE CARD UNPACKED INTO THE HOST'S SKILLS FOLDER (A PROJECT'S OWN, WITH --INTO); THE EXAC
$ python3 scripts/installer.py place the-card.skill.zip --host project --into project
already there: robotaxi-card (say --replace to put the new edition over it)
(refused: the card is already there; --replace puts a new edition over it)
$ (refused: the card is already there; --replace puts a new edition over it)
check · THE PLACED CARD READ BACK: THE DOOR'S NAME AND DESCRIPTION, THE MACHINE'S SELF-TEST RUN
$ python3 scripts/installer.py check project/.claude/skills/robotaxi-card
THE DOOR · SKILL.md names the card (robotaxi-card) and says when it wakes
THE MACHINE · scripts/av_robotaxi.py · self-test did not pass here: /usr/bin/python3: can't open file 'av_robotaxi.py': [Errno 2] No such file or directory
PYTHON · 3.13.16 on Linux
THE RECORD · card.json, WITNESS.md and MANIFEST.md are in the box
NOT READY · THE MENDER reads the line above and says what to do
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?
Hosts · every door, which ones are here. It asks first for the card's packet and the host you use; for a project host, the project folder.
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 (9/9) 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. It places for the hosts that read a folder (Claude Code, a project); for the Claude app, ChatGPT and the rest it can only say where the upload goes. It reads your home folder's own skills folder to say whether it exists and nothing else there.
What will it never do?
It will never write outside the folder you point it at; never send anything anywhere; never change a card, or speak for one.
