Does it need the Shopify connection?

No. Without it the machine works from the store's product list pasted in and cuts files the store imports. With it on, the card creates the drafts and reads the catalog itself, and says what it did.

Will it publish for me?

It makes drafts freely and publishes a product only when you name it; a batch is listed first. That is the law on the face.

Where do prices come from?

From you, on the ladder or off it. The card never prints a price it was not given and the store's price is the only true one.

Can it attach the files?

No — that door is the app's and yours. It checks the app's list against the record by name and bytes, and the room's punch check proves a downloaded copy.

How the house's own ticket finds a product: the handle first, then a handle or title that carries exactly its words. The card runs the same reading on the store's list so the ticket is never surprised.

No. It is a card at your elbow — a person with a machine and, when you allow it, a connection. It stores nothing, runs no server and holds no key of its own.

THE INSTRUMENTS · Nº 686 · EDITION 2 · METHOD + TESTS

LUND CARDS · THE INSTRUMENTSNº 686 PROPOSED

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE MONOLITH CARD · one file, many parts, and back to one

WAKES WHEN a single-file React app must be split to work on; join my components back into one file; check my one-file app for duplicate components

THE LOOP

NAME — `This is THE MONOLITH CARD.`
ASK — the app file.
CHECK — duplicates and the default export.
SPLIT — one file per component, with a manifest.
JOIN — back to one file, byte for byte, or the parts that changed named.
LEDGER — write the ledger line.

NEVER

a component refactored
a bundle built
a join that is not byte for byte

THE SEAL 68 of 100 · EPIC · MANIFEST · the method and 4 tests aboard; not yet witnessed

IT CAN BE WRONG an AI reading a text file: it can be wrong; check what matters. THE-CLAUSES.md rides in the packet and is part of the licence.

THE PUNCH · SHA-256 OF SKILL.MD · D5A3F2E78832988E775DDC5C

THE FACE, FULL SIZE → · THE MACHINE FACE → · card.json →

THE MONOLITH CARD

one file, many parts, and back to one

SPLIT TO WORK · JOINED BYTE FOR BYTE

EPICMANIFESTIN CLAUDE IN LUNDR IN CHATGPT

WITNESSED — the studio saw this card run and produce what its tin promises, and wrote the date down. What the marks mean →

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

SEAL: 68 of 100 · EPIC · MANIFEST
EDITION: E2
MACHINE: scripts/evals.py · 1 command · selftest 9/9
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 (HOSTS.md names each door)
LICENCE: One person, any number of their own AIs and computers · editions replace files · nothing renews · freeze, not loss
PUNCH: D5A3F2E78832988E775DDC5C · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE MONOLITH CARD, Edition 2. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=monolith-card. Punch D5A3F2E78832988E775DDC5C. Retrieved 2026-10-10.

What it is.

A single-file React app is easiest to ship and hardest to read. The card splits it into its top-level components, one file each with a manifest, refuses a duplicate component or a missing default export, and joins the parts back byte for byte.

The join is proven against the source.

Its laws, written into the card.

Parts are cut at top-level declarations; nothing inside a component is touched.
A duplicate component name is refused before any cut.
The join is proven against the hash of the source.

How it works, once your AI has it.

NAME — `This is THE MONOLITH CARD.`
ASK — the app file.
CHECK — duplicates and the default export.
SPLIT — one file per component, with a manifest.
JOIN — back to one file, byte for byte, or the parts that changed named.
LEDGER — write the ledger line.

When it says no.

Refactoring or renaming a component.
Bundling or transpiling.
Splitting a file with two components of one name → THE STATE CARD reads the same file for its storage calls.

What’s in the buy.

CARD.md — the whole card · SKILL.md — the door your AI reads first · START-HERE.md — the first five minutes
references/THE-METHOD.md · EVALS.json · EVALS.md · scripts/evals.py — the method, its template, and the tests with their runner
MY-LEDGER.md · TIN.md · LICENSE-NOTE.md · THE-CLAUSES.md · card.svg + card-machine.svg + card.json · card.html · the doors for ChatGPT, Gemini, Cursor, Copilot and the rest, and an MCP door

PROOF · 4 TESTS ABOARD · RUNNER SELFTEST 9/9 · AUDIT 12/12 · NOT YET WITNESSED · EDITION 2 · PUNCH D5A3F2E78832988E775DDC5C

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º 686 PROPOSED · ONE PAYMENT

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. The terms →

ONE PAYMENT · NOTHING RENEWS ITSELF

OFFLINE · ONE LICENCE · PUNCH-CHECKABLE · THE STANDARD

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.

ONE PAYMENT — NOTHING RENEWS ITSELF. CHECKOUT IS SHOPIFY’S OWN; YOUR CARD COMES BY EMAIL AFTER IT.

← THE INSTRUMENTS · THE FLOOR →