THE COMPRESSOR CARD · a theme kept under its caps, nothing lost
WAKES WHEN a Liquid file nears 256 KB, a theme zip 50 MB or a room on a theme is stored twice
THE LOOP
measure · every file against the cap
scan · read the store's way, before a zip
fold · a room stored once, read back
frame · one head, one foot, shared
split · parts under the cap, in order
NEVER
Delete a file to make room
Change what a page renders
Minify or rewrite a room's words
Upload or publish for you
IT MAKES measure — every Liquid file against the cap, the biggest first, the files over the cap and inside the guard, the theme's unzipped weight against the 50 MB zip line; scan — every Liquid file read the store's way: a tag or output that never closes, an unknown tag, an unbalanced block, an else or when outside its block, JSON that does not parse; PASS or the faults by file; fold — a room that stands twice (index + page, the same but for the canonical line) stored once in snippets/rm-<h>.liquid, both templates one-line stubs; each fold read back as both originals first; --dry only says; frame — rooms whose head or foot has the same shape share one fx-/fy- snippet and keep only their own words; the frame with the words put back must be the room's own text, or the room is left whole; split — a snippet split into parts under the cap at block boundaries (details, section, article, div), rendered back in order; head + parts + tail read back as the original or the split is refused.
THE STANDARD nothing lost; measure before and after; the guard under the cap; scan before every zip; split at a boundary a browser cannot see; the store is the judge.
PROOF SELFTEST 13/13 · witnessed in Claude 2026-10-10 · 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 · 6772E65095BD2859D5CD9F10
CITE THIS CARDTHE COMPRESSOR CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=compressor-card. Punch 6772E65095BD2859D5CD9F10. Retrieved 2026-10-10.
What it is.
Keeps a Shopify theme under the lines the store enforces — 256 KB for a Liquid file, 50 MB for the theme zip — with nothing lost: it measures every file against the cap, reads every Liquid file the way the store's parser does before a zip, stores a room that stands twice once, shares one head and one foot between rooms of the same shape, and splits a snippet that has outgrown the line into parts at a boundary a browser cannot see; every move is proven by reading the originals back byte for byte, or refused.
It carries a machine that shows its working: measure — every Liquid file against the cap, the biggest first, the files over the cap and inside the guard, the theme's unzipped weight against the 50 MB zip line; scan — every Liquid file read the store's way: a tag or output that never closes, an unknown tag, an unbalanced block, an else or when outside its block, JSON that does not parse; PASS or the faults by file; fold — a room that stands twice (index + page, the same but for the canonical line) stored once in snippets/rm-<h>.liquid, both templates one-line stubs; each fold read back as both originals first; --dry only says; frame — rooms whose head or foot has the same shape share one fx-/fy- snippet and keep only their own words; the frame with the words put back must be the room's own text, or the room is left whole; split — a snippet split into parts under the cap at block boundaries (details, section, article, div), rendered back in order; head + parts + tail read back as the original or the split is refused — 13 checks in its selftest, every command on the record. It will never delete a file to make room; never change what a page renders; never minify or rewrite a room's words; never upload or publish for you.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
NOTHING LOSTEvery move is a rearrangement of the same bytes, read back against the original before it is written; what cannot be read back is left alone and named.
MEASURE BEFORE AND AFTEREvery file against the cap, the biggest first, with the headroom; a move that saves nothing is not made.
THE GUARD UNDER THE CAPThe studio keeps 6 KB under the 256 KB line, so a cut never lands on it; a file inside the guard is folded or split before the next cut.
SCAN BEFORE EVERY ZIPEvery Liquid file is read the way the store's parser reads it; a theme is zipped only after the scan passes.
SPLIT AT A BOUNDARY A BROWSER CANNOT SEEBetween whole blocks only, rendered back in order; a block that needs the parent's variables is refused, not split.
THE STORE IS THE JUDGEThe caps are the store's as of the cut date; the card is the measure and the method, never a promise that an upload will take.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-METHOD.md
THE MACHINEnocap.py · five commandsmeasure — every Liquid file against the cap, the biggest first, the files over the cap and inside the guard, the theme's unzipped weight against the 50 MB zip line; scan — every Liquid file read the store's way: a tag or output that never closes, an unknown tag, an unbalanced block, an else or when outside its block, JSON that does not parse; PASS or the faults by file; fold — a room that stands twice (index + page, the same but for the canonical line) stored once in snippets/rm-<h>.liquid, both templates one-line stubs; each fold read back as both originals first; --dry only says; frame — rooms whose head or foot has the same shape share one fx-/fy- snippet and keep only their own words; the frame with the words put back must be the room's own text, or the room is left whole; split — a snippet split into parts under the cap at block boundaries (details, section, article, div), rendered back in order; head + parts + tail read back as the original or the split is refused. Every command prints its working and refuses a bad input; 13 checks in its selftest, every command on the record.
What it does once your AI has it.
measure Every Liquid file against the cap, the biggest first, the files over the cap and inside the guard, the theme's unzipped weight against the 50 MB zip line
scan Every Liquid file read the store's way: a tag or output that never closes, an unknown tag, an unbalanced block, an else or when outside its block, JSON that does not parse; PASS or the faults by file
fold A room that stands twice (index + page, the same but for the canonical line) stored once in snippets/rm-<h>.liquid, both templates one-line stubs; each fold read back as both originals first; --dry only says
frame Rooms whose head or foot has the same shape share one fx-/fy- snippet and keep only their own words; the frame with the words put back must be the room's own text, or the room is left whole
split A snippet split into parts under the cap at block boundaries (details, section, article, div), rendered back in order; head + parts + tail read back as the original or the split is refused
On the record A small shop written for the record: three rooms that stand twice, one pair that differs beyond its canonical line, a menu of nine houses and one broken snippet. The measure names the menu over a 16 KB cap; the scan names the broken snippet and passes once it is out; the dry fold names three pairs and leaves the fourth with its reason; the fold stores the three rooms once with both templates as one-line stubs, each read back as both originals; the frame gives the three rooms one shared foot; the split cuts the menu into parts under 12 KB, rendered in order and read back whole; the second measure shows nothing over the cap.
What it will never do.
It will never delete a file to make room; never change what a page renders; never minify or rewrite a room's words; never upload or publish for you.
It measures and rearranges; it cannot make a single block smaller than the cap, and it does not touch pictures, fonts or JavaScript assets — those belong in the store's Files or stay as they are. The caps it names are the store's on the cut date; the uploader is the judge. 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-METHOD.md — the guide in references/, in the card's own voice
scripts/nocap.py — the machine: measure · scan · fold · frame · split, standard library only, selftest 13/13
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 13/13 · 5 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-10 · EDITION 1 · PUNCH 6772E65095BD2859D5CD9F10
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º 960 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-10
nocap.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.
measure
every Liquid file against the cap, the biggest first, the files over the cap and inside the guard, the theme's unzipped weight against the 50 MB zip line
scan
every Liquid file read the store's way: a tag or output that never closes, an unknown tag, an unbalanced block, an else or when outside its block, JSON that does not parse; PASS or the faults by file
fold
a room that stands twice (index + page, the same but for the canonical line) stored once in snippets/rm-<h>.liquid, both templates one-line stubs; each fold read back as both originals first; --dry only says
frame
rooms whose head or foot has the same shape share one fx-/fy- snippet and keep only their own words; the frame with the words put back must be the room's own text, or the room is left whole
split
a snippet split into parts under the cap at block boundaries (details, section, article, div), rendered back in order; head + parts + tail read back as the original or the split is refused
selftest
13 checks that prove the machine; it must print 13/13
(a small shop written for the record: three rooms that stand twice, one pair that differs, a menu of nine hous
$ (a small shop written for the record: three rooms that stand twice, one pair that differs, a menu of nine houses, one broken snippet)
measure · EVERY LIQUID FILE AGAINST THE CAP, THE BIGGEST FIRST, THE FILES OVER THE CAP AND INSIDE
$ python3 scripts/nocap.py measure shop --cap 16 --guard 2
MEASURE · shop · 10 Liquid files · 26,743 bytes of Liquid · the cap 16 KB, the guard 2 KB under it
20,953 127.9% of the cap snippets/menu.liquid
902 5.5% of the cap templates/index.ash.liquid
902 5.5% of the cap templates/index.elm.liquid
902 5.5% of the cap templates/index.oak.liquid
902 5.5% of the cap templates/page.ash.liquid
902 5.5% of the cap templates/page.elm.liquid
902 5.5% of the cap templates/page.oak.liquid
163 1.0% of the cap templates/index.fir.liquid
over the cap: 1 — snippets/menu.liquid
inside the guard: 0
the theme weighs 26,770 bytes unzipped; the zip line is 50,000,000 · UNDER
formula: headroom = cap − size; a file inside the guard is split or folded before the next cut
limit: the caps are the store's as of the cut date; the uploader is the judge, this is the measure
(the cap set to 16 KB for the record, so the small menu stands over it the way a real menu stands over 256)
$ (the cap set to 16 KB for the record, so the small menu stands over it the way a real menu stands over 256)
scan · EVERY LIQUID FILE READ THE STORE'S WAY: A TAG OR OUTPUT THAT NEVER CLOSES, AN UNKNOWN TA
$ python3 scripts/nocap.py scan shop
SCAN · 10 Liquid files read the store's way · FAIL in 1 file
snippets/broken.liquid · if at 0 never closed
limit: the scan reads syntax, not meaning; a tag that parses can still render the wrong thing
(the broken snippet named; it is taken out of the shop before the next step, as a scan failure must be)
$ (the broken snippet named; it is taken out of the shop before the next step, as a scan failure must be)
scan · EVERY LIQUID FILE READ THE STORE'S WAY: A TAG OR OUTPUT THAT NEVER CLOSES, AN UNKNOWN TA
$ python3 scripts/nocap.py scan shop
SCAN · 9 Liquid files read the store's way · PASS
limit: the scan reads syntax, not meaning; a tag that parses can still render the wrong thing
fold · A ROOM THAT STANDS TWICE (INDEX + PAGE, THE SAME BUT FOR THE CANONICAL LINE) STORED ONCE
$ python3 scripts/nocap.py fold shop --dry
FOLD (dry) · 3 rooms stored once · 1 left as they were · 1,806 bytes saved
ash → snippets/rm-ash.liquid, both templates one line
elm → snippets/rm-elm.liquid, both templates one line
oak → snippets/rm-oak.liquid, both templates one line
left · fir · differs beyond the canonical line
proof: each fold was read back as both originals, byte for byte, before anything was written
limit: only a pair that differs in its canonical line alone is folded; anything else is named and left
fold · A ROOM THAT STANDS TWICE (INDEX + PAGE, THE SAME BUT FOR THE CANONICAL LINE) STORED ONCE
$ python3 scripts/nocap.py fold shop
FOLD · 3 rooms stored once · 1 left as they were · 1,806 bytes saved
ash → snippets/rm-ash.liquid, both templates one line
elm → snippets/rm-elm.liquid, both templates one line
oak → snippets/rm-oak.liquid, both templates one line
left · fir · differs beyond the canonical line
proof: each fold was read back as both originals, byte for byte, before anything was written
limit: only a pair that differs in its canonical line alone is folded; anything else is named and left
frame · ROOMS WHOSE HEAD OR FOOT HAS THE SAME SHAPE SHARE ONE FX-/FY- SNIPPET AND KEEP ONLY THEI
$ python3 scripts/nocap.py frame shop
FRAME · heads: 3 rooms share 1 · feet: 3 rooms share 1 · -39 bytes saved
proof: a room keeps only its own words; the shared frame with those words put back is the room's own text, or the room is left as it was
limit: a handle that sits outside a Liquid string literal cannot become a variable; that room keeps its own frame
split · A SNIPPET SPLIT INTO PARTS UNDER THE CAP AT BLOCK BOUNDARIES (DETAILS, SECTION, ARTICLE,
$ python3 scripts/nocap.py split shop/snippets/menu.liquid --cap 12
SPLIT · menu.liquid → 2 parts at <details> boundaries, rendered back in order
menu-1.liquid 11,605 bytes 5 blocks
menu-2.liquid 9,284 bytes 4 blocks
menu.liquid 106 bytes (the head, the renders, the tail)
proof: head + parts + tail read back as the original, byte for byte
limit: a part is rendered without the parent's variables; blocks that need them are refused, not split
measure · EVERY LIQUID FILE AGAINST THE CAP, THE BIGGEST FIRST, THE FILES OVER THE CAP AND INSIDE
$ python3 scripts/nocap.py measure shop --cap 16 --guard 2
MEASURE · shop · 16 Liquid files · 25,193 bytes of Liquid · the cap 16 KB, the guard 2 KB under it
11,605 70.8% of the cap snippets/menu-1.liquid
9,284 56.7% of the cap snippets/menu-2.liquid
1,133 6.9% of the cap snippets/rm-ash.liquid
1,133 6.9% of the cap snippets/rm-elm.liquid
1,133 6.9% of the cap snippets/rm-oak.liquid
163 1.0% of the cap templates/index.fir.liquid
163 1.0% of the cap templates/page.fir.liquid
141 0.9% of the cap snippets/fx-1.liquid
over the cap: 0
inside the guard: 0
the theme weighs 25,220 bytes unzipped; the zip line is 50,000,000 · UNDER
formula: headroom = cap − size; a file inside the guard is split or folded before the next cut
limit: the caps are the store's as of the cut date; the uploader is the judge, this is the measure
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?
Measure · every file against the cap. It asks first for the theme folder as exported from the store (assets, config, layout, locales, sections, snippets, templates) — or the one snippet that is over the line.
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 (13/13) 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 measures and rearranges; it cannot make a single block smaller than the cap, and it does not touch pictures, fonts or JavaScript assets — those belong in the store's Files or stay as they are. The caps it names are the store's on the cut date; the uploader is the judge.
What will it never do?
It will never delete a file to make room; never change what a page renders; never minify or rewrite a room's words; never upload or publish for you.
