THE METHODS · THE STUDIO ROOM · Nº 22 · EDITION 2 · LAUNCHING SOON

LUND CARDS · THE METHODSNº 22

THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE ONE UPLOAD CARD · The publishing seat: a folder packed once into one file with its manifest, checked before it leaves.

WAKES WHEN A folder is about to be uploaded and nobody can say afterwards which files were in it. · A packed file came back changed and nobody knows which file moved. · An upload bounced for size and the line was not known in advance. · A key file nearly went out inside a pack.

THE LOOP

Write the manifest: every file, its hash
Check: SECRET, OVER THE LINE, before packing
Pack once, the same bytes every time
Verify on the far side: MISSING, CHANGED

NEVER

Never packs a file matching a secret pattern
Never packs without a manifest
Never packs over the line the person set
Never claims a certainty it does not have

IT MAKES manifest — every file under DIR with its relative path, size and sha256, sorted; the exclusion patterns and the files and folders they left out recorded; totals; INSIDE THE FOLDER (exit 1) when --out lies under DIR; check — SECRET per file whose name matches .env, .env.*, *.pem, *.key, id_rsa*, contains secret or token, or a pattern given, or whose contents hold -----BEGIN, sk_live or an AKIA key id (the pattern and line named, never the value); OVER THE LINE when the folder's bytes exceed N, UNDER THE LINE otherwise, NO LINE SET without N; exit 1 on SECRET or OVER THE LINE; pack — the deterministic zip of the folder with MANIFEST.json inside and X.MANIFEST.json beside, its sha256 printed; refused on SECRET, OVER THE LINE (the finished zip over N; nothing is trimmed or written), STALE MANIFEST (the folder no longer matches the manifest), INSIDE THE FOLDER, NAME TAKEN (the folder holds its own MANIFEST.json), each exit 1; NO MANIFEST exit 2; verify — the folder against the manifest, file by file, the manifest's exclusions re-applied: MISSING, CHANGED (both sizes and hashes), EXTRA; exit 1 on any; inspect — every entry with its sizes and date; the manifest inside compared with the entries: MANIFEST MISMATCH per file, NO MANIFEST INSIDE when there is none, DATES VARY when any entry is not dated 1980-01-01; the zip's sha256; exit 1 on any flag.

THE LAW One folder, one file, one manifest. Every file in the pack is listed with its hash before the pack is made; a file that matches a secret pattern stops the pack; a pack over the line the person set is refused. The pack is written the same way every time, so the same folder gives the same bytes and the hash on the manifest is the hash on the far side.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/onepack.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (9 tests) · references/ (schema + fictional demo) · START-HERE.md · system/ doors · MY-LEDGER.md · LICENSE-NOTE.md · card.svg · card.json · card.html · AUDIT.md · MANIFEST.md · WITNESS.md · SELFTEST.md.

PROOF SELFTEST 16/16 · witnessed in Claude 2026-10-14 on fictional fixtures · the test prompts in fresh chat, 9/9 · Edition 2.

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. LICENSE-NOTE.md rides in the packet and is the licence.

THE PUNCH · SHA-256 OF SKILL.MD · 7249AC638434B1D01E59EEDD

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

THE ONE UPLOAD CARD

The publishing seat: a folder packed once into one file with its manifest, checked before it leaves.

MANIFEST · CHECK · PACK · VERIFY · INSPECT

LEGENDARYWITNESSEDIN 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: 98 of 100 · LEGENDARY · WITNESSED
EDITION: E1 · witnessed 2026-10-14
MACHINE: scripts/onepack.py · 5 commands · selftest 16/16
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: 7249AC638434B1D01E59EEDD · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE ONE UPLOAD CARD, Edition 2. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=one-upload-card. Punch 7249AC638434B1D01E59EEDD. Retrieved 2026-10-14.

What it is.

Use when a folder of files must leave the house as one upload: a manifest with hashes, a check for secrets and size, a deterministic pack, a verify on the other side. Not for building the files.

It carries a machine that shows its working: manifest — every file under DIR with its relative path, size and sha256, sorted; the exclusion patterns and the files and folders they left out recorded; totals; INSIDE THE FOLDER (exit 1) when --out lies under DIR; check — SECRET per file whose name matches .env, .env.*, *.pem, *.key, id_rsa*, contains secret or token, or a pattern given, or whose contents hold -----BEGIN, sk_live or an AKIA key id (the pattern and line named, never the value); OVER THE LINE when the folder's bytes exceed N, UNDER THE LINE otherwise, NO LINE SET without N; exit 1 on SECRET or OVER THE LINE; pack — the deterministic zip of the folder with MANIFEST.json inside and X.MANIFEST.json beside, its sha256 printed; refused on SECRET, OVER THE LINE (the finished zip over N; nothing is trimmed or written), STALE MANIFEST (the folder no longer matches the manifest), INSIDE THE FOLDER, NAME TAKEN (the folder holds its own MANIFEST.json), each exit 1; NO MANIFEST exit 2; verify — the folder against the manifest, file by file, the manifest's exclusions re-applied: MISSING, CHANGED (both sizes and hashes), EXTRA; exit 1 on any; inspect — every entry with its sizes and date; the manifest inside compared with the entries: MANIFEST MISMATCH per file, NO MANIFEST INSIDE when there is none, DATES VARY when any entry is not dated 1980-01-01; the zip's sha256; exit 1 on any flag — 16 checks in its selftest. It never packs a file matching a secret pattern; never packs without a manifest; never packs over the line the person set; never claims a certainty it does not have.

The law, written into the card.

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

THE LAWOne folder, one file, one manifest. Every file in the pack is listed with its hash before the pack is made; a file that matches a secret pattern stops the pack; a pack over the line the person set is refused. The pack is written the same way every time, so the same folder gives the same bytes and the hash on the manifest is the hash on the far side.

The method.

Write the manifest from the folder: path, size and hash for every file, the exclusions listed; sorted.
Check before packing: files matching the secret patterns (keys, tokens, env files) stop the pack with SECRET; a total over the line is OVER THE LINE.
Pack deterministically: sorted paths, fixed timestamps, one compression, so the pack's hash can be compared build to build.
Verify a folder against a manifest on the far side: MISSING, CHANGED and EXTRA, file by file.
Keep the manifest beside the pack and in it; the two must agree or the pack is not the one made.

What you bring.

The folder to pack.
The size line the destination allows.
The secret patterns the house adds to the defaults.

Planned as a separate seat, not in this box and not yet on sale: the studio's own packs for its theme and kit uploads.

What it does once your AI has it.

manifest Every file under DIR with its relative path, size and sha256, sorted; the exclusion patterns and the files and folders they left out recorded; totals; INSIDE THE FOLDER (exit 1) when --out lies under DIR
check SECRET per file whose name matches .env, .env.*, *.pem, *.key, id_rsa*, contains secret or token, or a pattern given, or whose contents hold -----BEGIN, sk_live or an AKIA key id (the pattern and line named, never the value); OVER THE LINE when the folder's bytes exceed N, UNDER THE LINE otherwise, NO LINE SET without N; exit 1 on SECRET or OVER THE LINE
pack The deterministic zip of the folder with MANIFEST.json inside and X.MANIFEST.json beside, its sha256 printed; refused on SECRET, OVER THE LINE (the finished zip over N; nothing is trimmed or written), STALE MANIFEST (the folder no longer matches the manifest), INSIDE THE FOLDER, NAME TAKEN (the folder holds its own MANIFEST.json), each exit 1; NO MANIFEST exit 2
verify The folder against the manifest, file by file, the manifest's exclusions re-applied: MISSING, CHANGED (both sizes and hashes), EXTRA; exit 1 on any
inspect Every entry with its sizes and date; the manifest inside compared with the entries: MANIFEST MISMATCH per file, NO MANIFEST INSIDE when there is none, DATES VARY when any entry is not dated 1980-01-01; the zip's sha256; exit 1 on any flag

What it will never do.

It never packs a file matching a secret pattern; never packs without a manifest; never packs over the line the person set; never claims a certainty it does not have.

Where it hands off: Masking personal data before it leaves → THE PRIVACY CARD; A card folder into the one file a loader reads → THE PACKAGE CARD; Naming the files so they cannot be confused → THE NAMING CARD.

It is not a security review. 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/onepack.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
tests/EVALS.json and scripts/evals.py — 9 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: the studio's own packs for its theme and kit uploads). Also not in the box: any data you must bring, and advice of any kind (not a security review).

PROOF · SELFTEST 16/16 · WITNESSED IN CLAUDE 2026-10-14 ON FICTIONAL FIXTURES · THE 9 TEST PROMPTS ASKED IN A FRESH CHAT HOLDING ONLY THE CARD · 9/9 · EDITION 2 · PUNCH 7249AC638434B1D01E59EEDD

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º 22 — 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 · 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.

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 CARD’S OWN SELFTEST.MD

onepack.py, every command showing its working.

A small Python program, standard library only. Your AI runs it; you can too. The block below is pasted from the card’s own SELFTEST.md, as printed when it was run from inside the packet.

`manifest`	every file under DIR with its relative path, size and sha256, sorted; the exclusion patterns and the files and folders they left out recorded; totals; INSIDE THE FOLDER (exit 1) when --out lies under DIR
`check`	SECRET per file whose name matches .env, .env., .pem, .key, id_rsa, contains secret or token, or a pattern given, or whose contents hold -----BEGIN, sk_live or an AKIA key id (the pattern and line named, never the value); OVER THE LINE when the folder's bytes exceed N, UNDER THE LINE otherwise, NO LINE SET without N; exit 1 on SECRET or OVER THE LINE
`pack`	the deterministic zip of the folder with MANIFEST.json inside and X.MANIFEST.json beside, its sha256 printed; refused on SECRET, OVER THE LINE (the finished zip over N; nothing is trimmed or written), STALE MANIFEST (the folder no longer matches the manifest), INSIDE THE FOLDER, NAME TAKEN (the folder holds its own MANIFEST.json), each exit 1; NO MANIFEST exit 2
`verify`	the folder against the manifest, file by file, the manifest's exclusions re-applied: MISSING, CHANGED (both sizes and hashes), EXTRA; exit 1 on any
`inspect`	every entry with its sizes and date; the manifest inside compared with the entries: MANIFEST MISMATCH per file, NO MANIFEST INSIDE when there is none, DATES VARY when any entry is not dated 1980-01-01; the zip's sha256; exit 1 on any flag
`selftest`	16 checks that prove the machine; it must print selftest 16/16

THE SELFTEST, AS PRINTED

ok   1  manifest lists every file sorted with its size and sha256, records the exclusion pattern and the file it left out, and the totals; exit 0
ok   2  manifest refuses INSIDE THE FOLDER (exit 1) when --out lies under the root, and writes nothing there
ok   3  check on a clean folder: 0 SECRET, NO LINE SET without a limit (exit 0), UNDER THE LINE with one above the total (exit 0), the excluded file listed
ok   4  check names SECRET per file by name (.env, *.pem, a name holding token) and by content (-----BEGIN, sk_live, an AKIA key id) with the line, exits 1, and never prints the value
ok   5  check takes the house's own patterns: a name glob (*.bak) and a text (HOUSE-KEY) each flag SECRET and say they were given
ok   6  check flags OVER THE LINE when the folder's bytes exceed --limit-bytes, with both figures, and exits 1
ok   7  pack writes the zip with MANIFEST.json inside and X.MANIFEST.json beside (the same bytes), sorted paths, every entry dated 1980-01-01, the manifest's exclusions honoured, and prints the pack's sha256
ok   8  the same folder packs to byte-identical zips twice, even after the files' dates and mode bits change, and the printed sha256 is the same
ok   9  pack refuses SECRET (exit 1): every matching file named by its pattern, no zip and no beside-manifest written
ok   10  pack refuses OVER THE LINE (exit 1) when the finished zip is over --limit-bytes: refused, not trimmed, nothing written
ok   11  pack never packs without a manifest: a missing, absent or misshapen manifest is NO MANIFEST (exit 2) and no zip is written
ok   12  pack refuses STALE MANIFEST (exit 1) when a file changed since the manifest, naming it; INSIDE THE FOLDER (exit 1) when the zip would land in the root; an --out not ending .zip is bad input (exit 2)
ok   13  verify: a folder matching its manifest is 3 match, 0 MISSING, 0 CHANGED, 0 EXTRA (exit 0); after an edit, a removal and an addition it names CHANGED, MISSING and EXTRA (exit 1), and the excluded notes.log is not EXTRA
ok   14  inspect lists every entry with its sizes and date, prints the zip's sha256, and finds the manifest inside matching every file (exit 0)
ok   15  inspect flags MANIFEST MISMATCH per file (changed, in the zip only, in the manifest only), NO MANIFEST INSIDE for a zip without one, and DATES VARY for entries not dated 1980-01-01 (each exit 1)
ok   16  a root that is not a folder, and a zip that is not a zip, are bad input (exit 2)
selftest 16/16

THE RUN IS PASTED FROM THE CARD’S OWN SELFTEST.MD AS PRINTED. ITS FIXTURES ARE FICTIONAL, INVENTED FOR THE TEST; NO PRIVATE PERSON IS NAMED.

QUESTIONS AT THE TABLE

Asked before the wire.

What does it need from me?

The folder to pack. The size line the destination allows. The secret patterns the house adds to the defaults. If something it needs is missing, it says what is missing and stops there.

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 machine's selftest (16/16), run from inside the packet in Claude on 2026-10-14 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: Any run on real data. Every demo file is fictional. 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 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. LICENSE-NOTE.md rides in the packet and is the licence. It is not a security review.

What will it never do?

It never packs a file matching a secret pattern; never packs without a manifest; never packs over the line the person set; never claims a certainty it does not have.

← THE METHODS · THE FLOOR →