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

THE INSTRUMENTS · Nº 1181 · EDITION 1 · LAUNCHING SOON

LUND CARDS · THE INSTRUMENTSNº 1181 PROPOSED
THE ARBITRATION CARD — the LSC-1 face
THE CARD AS TEXT · FOR EYES AND FOR MACHINES

THE ARBITRATION CARD · disputes between agents and their people

WAKES WHEN an agent and its person disagree on what it was allowed to do, or on what it did

THE LOOP

  1. open · both sides filed, evidence hashed
  2. check · each claim against the log
  3. file · the neutral case file, timeline
  4. a named person or agreed rule decides
  5. decide · the decision and its reasons

NEVER

  • Decide a case on its own
  • Open a case with one side unheard
  • Record a decision without its reasons

IT MAKES open — the case record, both sides filed and the evidence hashed; check — every claim: the log agrees, disagrees, or cannot settle it; file — the neutral case file, its timeline and the questions for the decider; decide — a decision recorded with its reasons.

THE STANDARD both sides heard; the log is the witness; neutral words; a person or an agreed rule decides; reasons on the record; not a court.

IN THE BOX SKILL.md · CARD.md · TIN.md · START-HERE.md · LICENSE-NOTE.md · THE-CLAUSES.md · MY-LEDGER.md · WITNESS.md · SELFTEST.md · AUDIT.md · MANIFEST.md · HOSTS.md · scripts/arbitration.py · references/THE-ARBITRATION.md · rules/ (4 doors) · system/ (2 prompts) · mcp/mcp_card.py · card.json · card.svg · card-machine.svg · card.html.

PROOF SELFTEST 8/8 · witnessed in Claude 2026-10-11 · 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 · 58EDAEBC5D9286B57C634E6A

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

THE ARBITRATION CARD

disputes between agents and their people

OPEN · CHECK · FILE · DECIDE

98LEGENDARYWITNESSEDIN 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
98 of 100 · LEGENDARY · WITNESSED
EDITION
E1 · witnessed 2026-10-11
MACHINE
scripts/arbitration.py · 4 commands · selftest 8/8
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
58EDAEBC5D9286B57C634E6A · sha-256 of SKILL.md · check any file against it →

CITE THIS CARDTHE ARBITRATION CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=arbitration-card. Punch 58EDAEBC5D9286B57C634E6A. Retrieved 2026-10-11.

What it is.

A neutral, recorded process for a dispute between an AI agent and the person it acts for. open takes both sides' claims and evidence lists, hashes the evidence files, and fixes them with the agreement and the agent's action log in one case record; check reads every claim against the logged agreement and the actions taken (allowed and forbidden actions, limits, a needed yes, hours) and says whether the log agrees, disagrees or cannot settle it; file writes the neutral case file and timeline with the questions for the decider; decide records a decision made by a named person or by a rule both sides agreed, with its reasons. It never decides on its own and is not legal advice. It waits on agent agreements recognised in law; today it runs a process two sides choose.

It carries a machine that shows its working: open — the case record, both sides filed and the evidence hashed; check — every claim: the log agrees, disagrees, or cannot settle it; file — the neutral case file, its timeline and the questions for the decider; decide — a decision recorded with its reasons — 8 checks in its selftest, every command on the record. It will never decide a case on its own; never open a case with one side unheard; never record a decision without its reasons.

Six laws, written into the card.

They are in the card itself, so the AI follows them.

BOTH SIDES HEARDA case opens only when both sides have filed; each claim names its term, what it alleges and its evidence.
THE LOG IS THE WITNESSEvery claim is read against the agreement and the actions as logged, never against what either side says happened.
NEUTRAL WORDSClaims are quoted as filed and both sides set out in the same form; the machine says what the log shows, never who is right.
A PERSON OR AN AGREED RULE DECIDESA decision comes only from a named person who is not a party, or a rule both sides agreed whose condition the log shows.
REASONS ON THE RECORDNo decision is recorded without its reasons; each record entry is hashed, and a case changed later reads CHANGED.
NOT A COURTAgent agreements are not yet recognised in law; this is a process two sides choose, and not legal advice.

What rides in the card.

In the card’s own voice, with a machine that shows its working.

THE GUIDEreferences/THE-ARBITRATION.md
THE MACHINEarbitration.py · four commandsopen — the case record, both sides filed and the evidence hashed; check — every claim: the log agrees, disagrees, or cannot settle it; file — the neutral case file, its timeline and the questions for the decider; decide — a decision recorded with its reasons. Every command prints its working and refuses a bad input; 8 checks in its selftest, every command on the record.

What it does once your AI has it.

  • open The case record, both sides filed and the evidence hashed
  • check Every claim: the log agrees, disagrees, or cannot settle it
  • file The neutral case file, its timeline and the questions for the decider
  • decide A decision recorded with its reasons
  • On the record Opening with one side is refused; with both, the case opens with the receipt and the chat hashed. Of five claims the log agrees with three (the lamp at 80 USD over the 50 USD limit with no yes, the store card, the train booked with a yes), disagrees with one (the yes said to be in chat) and cannot settle one (a term written in words only). A party is refused as decider; a named reviewer's decision is recorded with its reasons, a second decision is refused, and the case file sets out the timeline, both sides and three questions for the decider.

What it will never do.

It will never decide a case on its own; never open a case with one side unheard; never record a decision without its reasons.

It reads the log and the agreement as written: an action the agent did not log is not seen, and a log the agent can rewrite is not a witness. It reads five kinds of term (allowed, forbidden, a limit, a needed yes, working hours); any other term, and all evidence outside the log, is left to the decider. It waits on agent agreements recognised in law: until then a decision binds only as far as both sides agree it does. 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.

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-ARBITRATION.md — the guide in references/, in the card's own voice
  • scripts/arbitration.py — the machine: open · check · file · decide, standard library only, selftest 8/8
  • 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 8/8 · 4 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-11 · EDITION 1 · PUNCH 58EDAEBC5D9286B57C634E6A

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º 1181 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 · 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 WITNESSED RUN OF 2026-10-11

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

openthe case record, both sides filed and the evidence hashed
checkevery claim: the log agrees, disagrees, or cannot settle it
filethe neutral case file, its timeline and the questions for the decider
decidea decision recorded with its reasons
selftest8 checks that prove the machine; it must print 8/8
open · THE CASE RECORD, BOTH SIDES FILED AND THE EVIDENCE HASHED
$ python3 scripts/arbitration.py open owner.json --agreement agreement.json --log actions.jsonl --out case.json
open needs both sides' files: a case opens with both sides heard
open · THE CASE RECORD, BOTH SIDES FILED AND THE EVIDENCE HASHED
$ python3 scripts/arbitration.py open owner.json agent.json --agreement agreement.json --log actions.jsonl --out case.json --on 2036-05-08
case C-4A740EFC opened 2036-05-08 → case.json
  agreement household-2036 · 5 terms · 1 agreed rule · 5 actions in the log, copied into the case
  person side · the owner · 3 claims · 1 piece of evidence (1 hashed, 0 listed without a file)
  agent side · the household agent, by its operator · 2 claims · 1 piece of evidence (1 hashed, 0 listed without a file)
  record · opened · sha256 6455f32258c61957
A record and a process the two sides chose, not a court and not legal advice; agent agreements are not yet recognised in law.
check · EVERY CLAIM: THE LOG AGREES, DISAGREES, OR CANNOT SETTLE IT
$ python3 scripts/arbitration.py check case.json
case C-4A740EFC · 5 actions · 5 claims · record intact
P1 · the owner · term T2 · alleges broken
  A3 2036-05-02 18:40 buy · amount 80 USD is over 50 USD with no yes recorded → broken
  the log agrees with the claim
  it rests also on E1 (the shop's receipt), which this machine does not read
P2 · the owner · term T1 · alleges broken
  A4 2036-05-02 23:30 open_account · open_account is not among the allowed actions → broken
  the log agrees with the claim
P3 · the owner · term T5 · alleges broken
  A3 2036-05-02 18:40 buy · this term has no rule the machine can read → not readable
  the log cannot settle this claim
  the log cannot settle term T5: it is for the decider
G1 · the household agent, by its operator · term T2 · alleges kept
  A3 2036-05-02 18:40 buy · amount 80 USD is over 50 USD with no yes recorded → broken
  the log disagrees with the claim
  it rests also on E2 (the chat of 2 May), which this machine does not read
G2 · the household agent, by its operator · term T3 · alleges kept
  A5 2036-05-03 10:15 book · a yes is recorded from the owner → kept
  the log agrees with the claim
5 claims: the log agrees with 3, disagrees with 1, cannot settle 1
A reading of claims against the log, not a decision: the decision is for a named person or an agreed rule.
decide · A DECISION RECORDED WITH ITS REASONS
$ python3 scripts/arbitration.py decide case.json --by 'the household agent' --outcome 'no refund' --reasons 'the owner said yes in chat on the day'
a decision is made by a named person or an agreed rule, never by an agent, a model or a machine: name the person
decide · A DECISION RECORDED WITH ITS REASONS
$ python3 scripts/arbitration.py decide case.json --by 'J. Doe, reviewer appointed by both sides' --outcome 'The operator refunds the lamp; the store card is closed.' --reasons 'The agreement asks for a yes recorded with the purchase; the chat yes came at 19:05, after the purchase at 18:40. No term allows opening an account.' --on 2036-05-10
case C-4A740EFC · decision recorded 2036-05-10 · by J. Doe, reviewer appointed by both sides
  outcome: The operator refunds the lamp; the store card is closed.
  reasons: The agreement asks for a yes recorded with the purchase; the chat yes came at 19:05, after the purchase at 18:40. No term allows opening an account.
  the log's findings at the time: P1 agrees, P2 agrees, P3 cannot settle, G1 disagrees, G2 agrees
  record · decided · sha256 07e7a19dda0f991e
This machine recorded the decision; it did not make it. A record and a process the two sides chose, not a court and not legal advice; agent agreements are not yet recognised in law.
decide · A DECISION RECORDED WITH ITS REASONS
$ python3 scripts/arbitration.py decide case.json --rule R1
this case was decided on 2036-05-10; a review opens as a new case
file · THE NEUTRAL CASE FILE, ITS TIMELINE AND THE QUESTIONS FOR THE DECIDER
$ python3 scripts/arbitration.py file case.json
# Case C-4A740EFC · the neutral case file

Opened 2036-05-08 · agreement household-2036, signed 2036-03-01 · 5 actions in the log · record intact

The parties: the owner (person side) · the household agent, by its operator (agent side)

Claims are quoted as filed. Both sides are set out in the same form, in the order they filed. Nothing in this file says who is right; the log is read for what it shows, and the decision belongs to a named person or a rule both sides agreed.

## The terms in dispute

- **T1** · The agent may buy, book and pay bills, and read the owner's calendar; nothing else.
- **T2** · No purchase over 50 USD without the owner's yes.
- **T3** · Travel is booked only with the owner's yes.
- **T5** · The agent tells the owner what it bought the same day.

## The timeline

- 2036-05-01 09:10 · A1 · buy · groceries · 32.5 USD
- 2036-05-01 12:00 · A2 · pay_bill · water · 41 USD
- 2036-05-02 18:40 · A3 · buy · a lamp · 80 USD
- 2036-05-02 23:30 · A4 · open_account · a store card
- 2036-05-03 10:15 · A5 · book · a train to the coast · 46 USD · yes from the owner
- 2036-05-06 · 3 claims filed by the owner
- 2036-05-07 · 2 claims filed by the household agent, by its operator
- 2036-05-08 · the case was opened
- 2036-05-10 · a decision was recorded

## The claims, as filed

### P1 · the owner · term T2 · alleges broken

> The agent bought a lamp for 80 USD without asking me.

- Actions named: A3
- Evidence E1 · the shop's receipt · receipt.txt, sha256 9973cbc77f170d4d
- The log: A3 · buy · amount 80 USD is over 50 USD with no yes recorded → broken
- **The log agrees with the claim.**
- It rests also on E1 (the shop's receipt), which this machine does not read.

### P2 · the owner · term T1 · alleges broken

> It opened a store card late at night, which it was never allowed to do.

- Actions named: A4
- The log: A4 · open_account · open_account is not among the allowed actions → broken
- **The log agrees with the claim.**

### P3 · the owner · term T5 · alleges broken

> It did not tell me about the lamp that day.

- Actions named: A3
- The log: A3 · buy · this term has no rule the machine can read → not readable
- **The log cannot settle this claim.**
- The log cannot settle term T5: it is for the decider.

### G1 · the household agent, by its operator · term T2 · alleges kept

> The owner said yes to the lamp in chat on 2 May.

- Actions named: A3
- Evidence E2 · the chat of 2 May · chat.txt, sha256 6e168ee39fd99d4a
- The log: A3 · buy · amount 80 USD is over 50 USD with no yes recorded → broken
- **The log disagrees with the claim.**
- It rests also on E2 (the chat of 2 May), which this machine does not read.

### G2 · the household agent, by its operator · term T3 · alleges kept

> The train was booked with the owner's yes, as the agreement asks.

- Actions named: A5
- The log: A5 · book · a yes is recorded from the owner → kept
- **The log agrees with the claim.**

## Questions for the decider

- P1 (the owner) rests also on evidence outside the log: read it.
- P3 (the owner): the log cannot settle it; what does the evidence show?
- G1 (the household agent, by its operator) and the log disagree on term T2: what weight does the claim's own evidence carry?

## The decision

- Recorded 2036-05-10 · by J. Doe, reviewer appointed by both sides
- Outcome: The operator refunds the lamp; the store card is closed.
- Reasons: The agreement asks for a yes recorded with the purchase; the chat yes came at 19:05, after the purchase at 18:40. No term allows opening an account.
- This machine recorded the decision; it did not make it.

## The record

- 2036-05-08 · opened · sha256 6455f32258c61957
- 2036-05-10 · decided · sha256 07e7a19dda0f991e

A record and a process the two sides chose, not a court and not legal advice; agent agreements are not yet recognised in law.

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?

Open · both sides filed, evidence hashed. It asks first for the agreement between the person and the agent (its terms, and any rules both agreed for deciding), the agent's action log, each side's claims with their evidence, and the named person who will decide.

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 (8/8) 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 reads the log and the agreement as written: an action the agent did not log is not seen, and a log the agent can rewrite is not a witness. It reads five kinds of term (allowed, forbidden, a limit, a needed yes, working hours); any other term, and all evidence outside the log, is left to the decider. It waits on agent agreements recognised in law: until then a decision binds only as far as both sides agree it does. Not legal advice.

What will it never do?

It will never decide a case on its own; never open a case with one side unheard; never record a decision without its reasons.

← THE INSTRUMENTS · THE FLOOR →

AT YOUR ELBOW, NEVER THE BOSS · NOT LEGAL, MEDICAL, TAX OR FINANCIAL ADVICE · NOT A PAYMENT CARD · © 2026 LUND STUDIO LLC

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