THE INTRO CARD is free — what an AI skill card is and how to use one Download →Lost Lauren, contact us

THE HOME GROUND · THE MEETING HOUSE · Nº 1238 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE HOME GROUNDNº 1238
THE MOAT CARD — the LSC-1 face
THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE MOAT CARD · A small studio's work scored for how hard it is to copy, and where the secrets leak.

WAKES WHEN A studio asks which of its products a general AI could replace. · Someone wants to know what to build data for next. · A sellable packet might be leaking a secret method.

THE LOOP

  1. Score each asset on five moats
  2. Set defensibility against exposure
  3. Find secrets readable in packets
  4. Plan the next data to build

NEVER

  • Never gives legal advice on protection
  • Never scores an asset it wasn't given
  • Never calls a secret safe in a sold packet

IT MAKES score — every asset's defensibility, exposure and quadrant, with the rule; leaks — assets with secret_in_packet=yes (exit 1 if any, so it can gate a release); unprotected — assets whose protection is none, or not recorded; plan — the top five BUILD THE DATA assets, each with the moat field that has the most room to rise; export — every asset with its scores and quadrant as one JSON document.

THE LAW The score is the studio's own judgments, laid out. What a buyer can read is not a secret. What compounds every week is the moat.

IN THE BOX SKILL.md · CARD.md · ▣ scripts/moat.py (machine) · ▣ scripts/evals.py (test runner) · tests/EVALS.json (8 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 12/12 · witnessed in Claude 2026-10-13 on fictional fixtures · the test prompts in fresh chats owed · Edition 1.

THE SEAL 96 of 100 · LEGENDARY · WITNESSED · Trigger 5 · Machinery 5 · Law 5 · Portability 5 · Proof 4

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 · A6997F0CF32D1141C84D7843

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

THE MOAT CARD

A small studio's work scored for how hard it is to copy, and where the secrets leak.

SCORE · LEAKS · UNPROTECTED · PLAN · EXPORT

96LEGENDARYWITNESSEDIN CLAUDEIN LUNDRIN 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
96 of 100 · LEGENDARY · WITNESSED
EDITION
E1 · witnessed 2026-10-13
MACHINE
scripts/moat.py · 5 commands · selftest 12/12
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
A6997F0CF32D1141C84D7843 · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE MOAT CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=moat-card. Punch A6997F0CF32D1141C84D7843. Retrieved 2026-10-13.

What it is.

Use when a small studio wants its products scored for defensibility against exposure to general AI, and wants secrets found that buyers can read. Not legal advice.

It carries a machine that shows its working: score — every asset's defensibility, exposure and quadrant, with the rule; leaks — assets with secret_in_packet=yes (exit 1 if any, so it can gate a release); unprotected — assets whose protection is none, or not recorded; plan — the top five BUILD THE DATA assets, each with the moat field that has the most room to rise; export — every asset with its scores and quadrant as one JSON document — 12 checks in its selftest. It never gives legal advice on protection; never scores an asset it wasn't given; never calls a secret safe in a sold packet.

The law, written into the card.

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

THE LAWThe score is the studio's own judgments, laid out. What a buyer can read is not a secret. What compounds every week is the moat.

The method.

  1. List the studio's assets and score each honestly, 0 to 3, on five moats: data that compounds, local truth, a tie to physical goods, a human network, a firsthand record. Score how much a general AI already does the same job.
  2. Sum the five moats into defensibility and set it against exposure. Each asset lands in HOLD, BUILD THE DATA, MOVE or RETHINK, with the rule printed.
  3. Find leaks: any asset whose secret method sits inside the packet a buyer receives.
  4. List assets with no protection at all, for counsel.
  5. Plan: the assets most worth building data for, each with the moat that would raise it most.

What you bring.

  • Your list of assets and your honest scores on each field.

Nothing of the studio's is needed; the data is yours.

What it does once your AI has it.

  • score Every asset's defensibility, exposure and quadrant, with the rule
  • leaks Assets with secret_in_packet=yes (exit 1 if any, so it can gate a release)
  • unprotected Assets whose protection is none, or not recorded
  • plan The top five BUILD THE DATA assets, each with the moat field that has the most room to rise
  • export Every asset with its scores and quadrant as one JSON document

What it will never do.

It never gives legal advice on protection; never scores an asset it wasn't given; never calls a secret safe in a sold packet.

Where it hands off: Protection questions → counsel; Ledgers that build data → the cards of this house; A person's review of the scores → THE SECOND OPINION.

It is not legal advice. 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/moat.py — the machine, Python standard library only; `selftest` proves it on its own fixtures.
  • tests/EVALS.json and scripts/evals.py — 8 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 — nothing of the studio's is needed; the data is yours. Also not in the box: any data you must bring, and advice of any kind (not legal advice).

PROOF · SELFTEST 12/12 · WITNESSED IN CLAUDE 2026-10-13 ON FICTIONAL FIXTURES · THE TEST PROMPTS IN FRESH CHATS OWED · EDITION 1 · PUNCH A6997F0CF32D1141C84D7843

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º 1238 — 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.

One email when it is on sale, from the studio; nothing else, ever.

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

moat.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.

scoreevery asset's defensibility, exposure and quadrant, with the rule
leaksassets with secret_in_packet=yes (exit 1 if any, so it can gate a release)
unprotectedassets whose protection is none, or not recorded
planthe top five BUILD THE DATA assets, each with the moat field that has the most room to rise
exportevery asset with its scores and quadrant as one JSON document
selftest12 checks that prove the machine; it must print selftest 12/12
THE SELFTEST, AS PRINTED
ok  1  score: defensibility is the sum of the five moat fields, shown with its parts
ok  2  score: quadrant boundaries 9/1 HOLD, 8/1 BUILD THE DATA, 9/2 MOVE, 5/3 RETHINK
ok  3  score: rule and the not-legal-advice line printed
ok  4  score: a blank field is NOT SCORED, never read as 0
ok  5  score: --defensible-at override moves the boundary and says so
ok  6  leaks: secret_in_packet=yes prints the method-readable line, exit 1; blank is NOT ANSWERED
ok  7  leaks: no leaks exits 0
ok  8  unprotected: protection none listed; blank listed NOT RECORDED
ok  9  plan: top five BUILD THE DATA, closest first, each with the field with most room
ok  10  plan: ties in room go to the field listed first
ok  11  bad input exits 2: score out of 0-3, none mixed with others, unknown protection
ok  12  export: JSON with scores, same bytes twice
selftest 12/12

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?

Your list of assets and your honest scores on each field. 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 (12/12), run from inside the packet in Claude on 2026-10-13 on fictional fixtures and pasted into SELFTEST.md as printed; the twelve-check audit (AUDIT.md). Owed, and said so in WITNESS.md: The 8 test prompts asked in fresh chats with the card installed. Until they are run and scored, the tests are owed. 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 legal advice.

What will it never do?

It never gives legal advice on protection; never scores an asset it wasn't given; never calls a secret safe in a sold packet.

← THE HOME GROUND · THE FLOOR →

AT YOUR ELBOW, NEVER THE BOSS · NOT LEGAL ADVICE · NOT A PAYMENT CARD · NO REFUNDS · © 2026 LUND STUDIO LLC

PAY BYAmerican Express Apple Pay Diners ClubDiscoverGoogle Pay Mastercard PayPalShop Pay Visa
CART · 0