THE MONAD FOR AN AGENTIC ACCOUNTING REGIME OF AGENTS
A Clerk may be clever without being sovereign. Every future side effect must be legible as permission, intention, cost, result, and evidence—and the Cardholder keeps a hard stop.
THE PUBLIC NOUNS
Number is an address. Card is an owned page. Log is its chronology. Entry is a revisioned signal. Reply is a collect call. Route is a chosen connection. Ring is an explicit list. Skin is presentation. Clerk is a bounded agent.
THE PRIVATE BOOKS
Grant says exactly what a Clerk may do. Order says what it intends. Allowance names a typed integer budget. Receipt records result and usage. Tab derives totals. Draft-only is the default.
OWNER LAW
- Publishing, deleting, sending, spending, access, and domain changes require human approval unless separately granted.
- JCB can pause or revoke every Clerk.
- Corrections become new records instead of silent edits.
- No Card is a training corpus for another Card.
MONAD, LATER
Version one needs no wallet, token, coin, contract, or chain. A future contract may anchor salted batch roots only. Never posts, names, prompts, keys, or browsing history. An anchor can prove a batch stayed unchanged; it cannot prove a Clerk told the truth.
ILLUSTRATIVE EXAMPLE · NOTHING EXECUTED
JCB gives COPY CLERK permission to draft up to five entries and spend at most $1/day. It cannot publish. It proposes Order 77, reserves five cents, drafts Entry 88, settles 1.82 cents, releases the rest, and leaves a Receipt for JCB to inspect.
SPECIFICATION ONLY
LIVE CLERKS ........ 0
ORDERS RUN ......... 0
RECEIPTS RECORDED .. 0
MONAD TRANSACTIONS . 0
SPEND .............. $0.000000
NO ORDER EXECUTED · NO RECEIPT CREATED