One stack, read from the bottom up: how a single agent action becomes signed bytes, a record, a log
entry, both sides' evidence, a judgment, a history and a report. Select a layer to see what it does and every page
about it. New here? Start with the problem: a stranger node.
01 COSE + deterministic encoding
published RFC
Every record and checkpoint is signed as a COSE_Sign1 (RFC 9052). A signature over a digest checks only if the verifier hashes the same bytes the signer hashed, so JSON records are canonicalized with JCS (RFC 8785).
RFC 9995, the COSE Hash Envelope, signs the digest of a preimage held elsewhere; the COSE deterministic encodings Internet-Draft, in preparation, names the deterministic CBOR encoding behind that preimage.
Pages
Specifications
Status from explain/03, section 6 Specs: RFC 9052, RFC 8785, RFC 9995; COSE deterministic encodings is an Internet-Draft in preparation (repository link only).
02 CPB · canonical payload binding
Internet-Draft
A Signed Statement names, from a registry, the canonicalization its payload digest was computed under, so the construction is declared by name and never guessed.
The capsule format is one payload profile that uses this binding and declares jcs.
Pages
Specifications
Status from explain/04, section 6 Specs.
03 AAC capsule
Internet-Draft library released
A Capsule is a JSON record of one agent action that commits to what went in and what came out by digest, never by content; its identity, the capsule_id, is the SHA-256 of its own canonical bytes.
explain 13 lists every capsule type the mesh plugin seals; build b2 walks the record format field by field.
Pages
Specifications
Status from explain/02 and build/b2, Specs; build/b5, section 5 Status: capsule-emit 0.0.6 on crates.io, tagged live.
04 Composition
Internet-Draft designed
Composition keeps each format separate and joins them by a shared action digest: who authorized it (WHO), was it permitted (CAN), what the agent did (WHAT), did the runtime enforce it (AUDIT). A capsule fills the WHAT slot, so this layer sits beside the capsule and reads it, rather than under it.
Matching digests alone do not show that the action was authorized or that the record set is complete (accountability-composition-01 §6.2). One WHAT-to-WHO vector set is built; the CAN and AUDIT slots are designed.
Pages
Specifications
Status from build/b7, banner and section 5 Status: the whole flow designed; the WHAT-to-WHO vector set built, not live; CAN and AUDIT slots designed.
05 CLL / MMR + SCITT
Internet-Draft published RFC library released
Each node keeps its own append-only Merkle Mountain Range, signs small checkpoints over it, and can register those checkpoints with a SCITT Transparency Service, while the entries never leave the node.
An inclusion proof shows a record is in the log under a checkpoint; a consistency proof shows the log only grew between two checkpoints. A witness returns a COSE Receipt; the mesh plugin names none by default.
Pages
Specifications
Status from explain/05 and explain/06, Specs; build/b5, section 5 Status: checkpointed-local-log 0.2.1 on crates.io, tagged live.
06 Bilateral + settlement
Internet-Draft built, not live
Two parties who do not trust each other each seal only what their own side observed, and a verifier who trusts neither derives from the two records whether they agree; when they differ, the asymmetry is named.
Settlement records add the four legs of a payment with exact amounts and payment references. explain 12 shows the same records checked locally, by the other party, and by anyone with the evidence file.
Pages
Specifications
Status from explain/07, Specs; build/b7, section 5 Status: settlement-record legs, libraries and vectors built-not-live.
07 The local evidence log
library released
Keep every record you seal in an append-only log on your own disk, sign a checkpoint over it every N records or T minutes, and hand out a record with its inclusion proof and checkpoint so anyone can check it offline.
The reference implementation is checkpointed-local-log (CLL), in Python, Go, TypeScript and Rust; the latest crate tag is 0.3.1. In the Mesh-LLM plugin v0.1.4, capsule-emit 0.0.6 supplies the log wrapper; capsule-emit's main already builds its checkpoints on CLL directly.
Pages
Specifications
Status from build/b3, sections 1 and 5: CLL in four languages, latest crate tag 0.3.1; the Mesh-LLM plugin seals and checkpoints every exchange, live in v0.1.4. The chip is the draft b3 cites for what a book must supply (§8).
08 Judge + grades
Internet-Draft library released
A record may say how much evidence stands behind it; the verifier works that out again from the record's own bytes and reports any claim they do not support.
On the mesh, two answers to a marked pair are compared and a referee can sign a verdict (built, off by default). A verdict is its own record, linked by adjudicates, and never changes the record it judges.
Pages
Specifications
Status from explain/09 and build/b9, Specs; build/b9, section 5 Status: overclaim recomputation built, released; the referee-signed verdict built, not live; the judge record family designed.
09 History
built, not live designed
A node folds referee verdicts about a peer into counts kept locally, and an opt-in rule, off by default, can stop routing to that peer. Counts in their own units, no ranking and no score.
In a personal agent the person hands one recipient a History of selected deals; history_card/1 carries a stream's checkpoint history with no record content.
Pages
Specifications
Status from build/b11, section 5 Status: verdict counts, the opt-in rule and history_card/1 built-not-live; the personal-agent History profile designed.
10 Reports
Internet-Draft library released
A bundle packages a record with what makes it checkable and says exactly what it left out; selective disclosure withholds single fields without breaking the signature; an evidence request asks another party for a record.
The evidence report is one exchange as a file a stranger checks offline. A report page is drawn only after the file verifies, in words that live outside the evidence.
Pages
Specifications
Status from explain/08 and explain/15, Specs; build/b10, section 5 Status: verify core live in the TypeScript package 0.3.0; explain/15 Status: capsule-emit verify --bundle live.
Mesh-LLM
released (capsules v0.1.4)
Each node seals what it served, keeps its own log, exchanges records with peers, and can send a client-marked pair to a referee. The limits page says what a verified key does and does not mean.
Pages
Status from build/b5, section 5 Status: Mesh-LLM/capsules release v0.1.4, tagged live.
Personal agents
designed
Tool-call and approval records are in a released library; no personal-agent host here wires its connectors, scheduler and approvals into a book end to end.
Pages
Status from build/b6, banner: designed, not built for a personal-agent host.
Agent work for someone else
designed
The parts in code at a pinned commit are the settlement-record legs, the evidence request protocol and one composition vector set; the whole flow in one host is designed.
Pages
Status from build/b7, banner: designed, not built as a whole.
Builder's checklist
What to build, in order, to give your own host an evidence layer, with the status of each step.
Pages
Labels, specification names and status chips are taken from the explain and build pages they link to;
each layer names the page section its status comes from. Internet-Drafts are works in progress.