THE TRUST REGISTRY CARD · who is certified for what, and by whom
WAKES WHEN someone asks whether an agent, model or card is certified, by whom, and still valid
THE LOOP
key · each issuer's key, kept private
issue · a claim signed, evidence hashed
verify · as signed, standing today
expired · what has lapsed, what lapses
evidence · the report against its hash
NEVER
Certify anything itself
Print an issuer's key
Erase a claim instead of revoking it
IT MAKES key — a new key for an issuer; only its fingerprint is printed; issue — a signed claim; revoke — withdrawn by its own issuer, kept on the record; verify — valid, expired, revoked, or the signature fails; expired — what has lapsed and what lapses soon; evidence — the file against the hash on record.
THE STANDARD the card certifies nothing; signed by the issuer; evidence by hash; dates hold; revoked, not erased; keys are secret.
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 · DFD5B25D9C7E4408B4946218
CITE THIS CARDTHE TRUST REGISTRY CARD, Edition 1. Lund Studio LLC, Westminster, Colorado. https://lundr.tech/?view=trust-registry-card. Punch DFD5B25D9C7E4408B4946218. Retrieved 2026-10-11.
What it is.
Keeps a registry of claims about agents, models and AI skill cards: who holds the claim, what it says, who issued it, the SHA-256 of its evidence, the date and the expiry, each entry signed with the issuer's key (HMAC-SHA256). key makes an issuer's key and prints only its fingerprint; issue adds a signed claim; revoke withdraws one, signed by the same issuer, and keeps it on the record; verify proves an entry is as its issuer signed it and says whether it stands, has expired, is not yet valid or was revoked; expired lists what has lapsed and what lapses soon; evidence checks a file against the hash on record. The card certifies nothing: every claim is its issuer's. It waits on shared certification across companies; today it keeps a registry within one company or between partners who share keys.
It carries a machine that shows its working: key — a new key for an issuer; only its fingerprint is printed; issue — a signed claim; revoke — withdrawn by its own issuer, kept on the record; verify — valid, expired, revoked, or the signature fails; expired — what has lapsed and what lapses soon; evidence — the file against the hash on record — 8 checks in its selftest, every command on the record. It will never certify anything itself; never print an issuer's key; never erase a claim instead of revoking it.
Six laws, written into the card.
They are in the card itself, so the AI follows them.
THE CARD CERTIFIES NOTHINGEvery claim is its issuer's; the card refuses to be an issuer and says so on every verify.
SIGNED BY THE ISSUEREach entry is signed with its issuer's key (HMAC-SHA256); a word changed, or another key, reads SIGNATURE FAILS.
EVIDENCE BY HASHThe SHA-256 of the evidence is on record; a match proves the file is the one hashed, not that what it says is true.
DATES HOLDA claim stands through its expiry date and lapses the day after; before its issue date it is not yet valid.
REVOKED, NOT ERASEDOnly the claim's own issuer can revoke it; the claim stays on the record, and a revocation by anyone else is named and not honoured.
KEYS ARE SECRETA key is printed only as a fingerprint; anyone who holds an issuer's key can sign as that issuer.
What rides in the card.
In the card’s own voice, with a machine that shows its working.
THE GUIDEreferences/THE-TRUST-REGISTRY.md
THE MACHINEtrustregistry.py · six commandskey — a new key for an issuer; only its fingerprint is printed; issue — a signed claim; revoke — withdrawn by its own issuer, kept on the record; verify — valid, expired, revoked, or the signature fails; expired — what has lapsed and what lapses soon; evidence — the file against the hash on record. 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.
key A new key for an issuer; only its fingerprint is printed
issue A signed claim
revoke Withdrawn by its own issuer, kept on the record
verify Valid, expired, revoked, or the signature fails
expired What has lapsed and what lapses soon
evidence The file against the hash on record
On the record Two issuers get keys, printed only as fingerprints, and the card refuses a key in its own name. Two claims are issued and both verify on 2036-06-15, the report matching its hash; on 2036-07-02 the accessibility claim has lapsed and the red-team claim stands 242 more days. Revoked by its own issuer, the red-team claim reads REVOKED; with one word deleted from it, SIGNATURE FAILS; a report with one digit changed does not match the hash on record.
What it will never do.
It will never certify anything itself; never print an issuer's key; never erase a claim instead of revoking it.
HMAC-SHA256 proves an entry only to someone who holds the issuer's key, and anyone who holds it can also sign: it is not a public-key signature, and the registry is not public proof. It records what issuers claim and checks signatures, dates and hashes; it tests no agent, model or card, and a claim is only as good as its issuer. It waits on shared certification across companies, and on public-key signatures, which the standard library does not carry; today it serves one company or partners who share keys. A record of claims, not a certification. 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-TRUST-REGISTRY.md — the guide in references/, in the card's own voice
scripts/trustregistry.py — the machine: key · issue · revoke · verify · expired · evidence, 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 · 6 COMMANDS ON THE RECORD · WITNESSED IN CLAUDE 2026-10-11 · EDITION 1 · PUNCH DFD5B25D9C7E4408B4946218
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º 1183 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-11
trustregistry.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.
key
a new key for an issuer; only its fingerprint is printed
issue
a signed claim
revoke
withdrawn by its own issuer, kept on the record
verify
valid, expired, revoked, or the signature fails
expired
what has lapsed and what lapses soon
evidence
the file against the hash on record
selftest
8 checks that prove the machine; it must print 8/8
key · A NEW KEY FOR AN ISSUER; ONLY ITS FINGERPRINT IS PRINTED
$ python3 scripts/trustregistry.py key keys.json north-test-lab
keys.json · a new 256-bit key for north-test-lab · fingerprint ca376cb0d5b8ea91
The key itself is never printed. Keep keys.json private: anyone who holds a key can sign as its issuer.
key · A NEW KEY FOR AN ISSUER; ONLY ITS FINGERPRINT IS PRINTED
$ python3 scripts/trustregistry.py key keys.json east-review-board
keys.json · a new 256-bit key for east-review-board · fingerprint 3e5cb878d7f3bf9e
The key itself is never printed. Keep keys.json private: anyone who holds a key can sign as its issuer.
key · A NEW KEY FOR AN ISSUER; ONLY ITS FINGERPRINT IS PRINTED
$ python3 scripts/trustregistry.py key keys.json 'THE TRUST REGISTRY CARD'
the card certifies nothing and holds no key: an issuer is the body that tested the holder
issue · A SIGNED CLAIM
$ python3 scripts/trustregistry.py issue registry.json --keys keys.json --issuer north-test-lab --holder triage-agent-2 --claim 'passed the red-team suite v3 with no critical findings' --evidence report.txt --expires 2037-03-01 --on 2036-03-01
registry.json · TR-0001 issued by north-test-lab on 2036-03-01
holder triage-agent-2
claim passed the red-team suite v3 with no critical findings
evidence report.txt · 74 bytes · sha256 144113f5e9244c0574c9f7a76350609b9a1a411f314b66e6676cc9ffad2ddfa5
stands through 2037-03-01 · signed HMAC-SHA256 with the key ca376cb0d5b8ea91
A record of what each issuer claims, checked; the card certifies nothing itself.
issue · A SIGNED CLAIM
$ python3 scripts/trustregistry.py issue registry.json --keys keys.json --issuer east-review-board --holder help-card --claim 'meets the accessibility review, twelve checks' --evidence review.txt --expires 2036-06-30 --on 2035-07-01
registry.json · TR-0002 issued by east-review-board on 2035-07-01
holder help-card
claim meets the accessibility review, twelve checks
evidence review.txt · 54 bytes · sha256 2fa807eefec8e00d7a9836ad28c76b3f47f70f8ab9f7f7990fe20cf483e54ce0
stands through 2036-06-30 · signed HMAC-SHA256 with the key 3e5cb878d7f3bf9e
A record of what each issuer claims, checked; the card certifies nothing itself.
verify · VALID, EXPIRED, REVOKED, OR THE SIGNATURE FAILS
$ python3 scripts/trustregistry.py verify registry.json --keys keys.json --on 2036-06-15
registry.json · 2 claims verified on 2036-06-15
TR-0001 · triage-agent-2 · passed the red-team suite v3 with no critical findings · by north-test-lab
VALID · stands through 2037-03-01 (259 days left)
TR-0002 · help-card · meets the accessibility review, twelve checks · by east-review-board
VALID · stands through 2036-06-30 (15 days left)
2 valid of 2
A record of what each issuer claims, checked; the card certifies nothing itself.
verify · VALID, EXPIRED, REVOKED, OR THE SIGNATURE FAILS
$ python3 scripts/trustregistry.py verify registry.json --keys keys.json --id TR-0001 --evidence report.txt --on 2036-06-15
registry.json · 1 claim verified on 2036-06-15
TR-0001 · triage-agent-2 · passed the red-team suite v3 with no critical findings · by north-test-lab
VALID · stands through 2037-03-01 (259 days left)
evidence report.txt · sha256 144113f5e9244c05 · MATCHES the hash on record
1 valid of 1
A record of what each issuer claims, checked; the card certifies nothing itself.
expired · WHAT HAS LAPSED AND WHAT LAPSES SOON
$ python3 scripts/trustregistry.py expired registry.json --on 2036-07-02 --within 365
registry.json · 2 claims · on 2036-07-02 · dates as written (verify proves them)
expired: 1
TR-0002 · help-card · east-review-board · lapsed after 2036-06-30
lapse within 365 days: 1
TR-0001 · triage-agent-2 · north-test-lab · stands through 2037-03-01 (242 days)
standing longer: 0
revoke · WITHDRAWN BY ITS OWN ISSUER, KEPT ON THE RECORD
$ python3 scripts/trustregistry.py revoke registry.json --keys keys.json --id TR-0001 --reason 'the suite was found to miss a class of attack' --on 2036-08-01
registry.json · TR-0003 revokes TR-0001 · by north-test-lab on 2036-08-01 · the suite was found to miss a class of attack
The claim stays on the record, marked revoked; nothing is erased.
verify · VALID, EXPIRED, REVOKED, OR THE SIGNATURE FAILS
$ python3 scripts/trustregistry.py verify registry.json --keys keys.json --on 2036-09-01
registry.json · 2 claims verified on 2036-09-01
TR-0001 · triage-agent-2 · passed the red-team suite v3 with no critical findings · by north-test-lab
REVOKED · revoked by north-test-lab on 2036-08-01: the suite was found to miss a class of attack
TR-0002 · help-card · meets the accessibility review, twelve checks · by east-review-board
EXPIRED · lapsed after 2036-06-30, 63 days ago
0 valid of 2 · read each line above
A record of what each issuer claims, checked; the card certifies nothing itself.
verify · VALID, EXPIRED, REVOKED, OR THE SIGNATURE FAILS
$ python3 scripts/trustregistry.py verify registry-edited.json --keys keys.json --id TR-0001 --on 2036-06-15
registry-edited.json · 1 claim verified on 2036-06-15
TR-0001 · triage-agent-2 · passed the red-team suite v3 with no findings · by north-test-lab
SIGNATURE FAILS · the entry is not as north-test-lab signed it: changed after signing, or signed with another key
0 valid of 1 · read each line above
A record of what each issuer claims, checked; the card certifies nothing itself.
evidence · THE FILE AGAINST THE HASH ON RECORD
$ python3 scripts/trustregistry.py evidence registry.json TR-0001 report.txt
report.txt · 74 bytes · sha256 144113f5e9244c0574c9f7a76350609b9a1a411f314b66e6676cc9ffad2ddfa5
MATCHES · on record for TR-0001 (report.txt): 144113f5e9244c0574c9f7a76350609b9a1a411f314b66e6676cc9ffad2ddfa5
A match proves the file is the one the issuer hashed, not that what it says is true.
evidence · THE FILE AGAINST THE HASH ON RECORD
$ python3 scripts/trustregistry.py evidence registry.json TR-0001 report-edited.txt
report-edited.txt · 74 bytes · sha256 69d62d821c49f33c5adc5bdd7ead31acfdfd5fd2bef6ff41fd556afa85a223db
DOES NOT MATCH · on record for TR-0001 (report.txt): 144113f5e9244c0574c9f7a76350609b9a1a411f314b66e6676cc9ffad2ddfa5
A match proves the file is the one the issuer hashed, not that what it says is true.
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?
Key · each issuer's key, kept private. It asks first for the issuer's name and the keys file, the holder (the agent, model or card), the claim in words, the evidence file, and the expiry date.
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. HMAC-SHA256 proves an entry only to someone who holds the issuer's key, and anyone who holds it can also sign: it is not a public-key signature, and the registry is not public proof. It records what issuers claim and checks signatures, dates and hashes; it tests no agent, model or card, and a claim is only as good as its issuer. It waits on shared certification across companies, and on public-key signatures, which the standard library does not carry; today it serves one company or partners who share keys. A record of claims, not a certification.
What will it never do?
It will never certify anything itself; never print an issuer's key; never erase a claim instead of revoking it.
