Agent Action Capsule · build your own evidence layer
Contents

Build your own evidence layer

Seams ① Record to ⑤ View. Build: the five seams in order: ① Record, ② Contract, ③ Check/judge, ④ Result, ⑤ View; each page names the one it builds. Conform to: the Internet-Drafts each page cites, starting with draft-mih-scitt-agent-action-capsule-05.

For an agent builder or an agent-economy platform that wants signed records of what its agents did, kept so that any verifier can check them later, on any host. Every page follows one loop: an agent acts, the act is recorded, the record is judged, the judgment is reported, and the history feeds the next act. The pages are in the order the Mesh-LLM worked example was built; each ends with what you need before the next step.

The evidence loop: act, record, judge, report, history, and back into the next act Five stages arranged in a ring and joined by arrows: act at the top, record at the right, judge at the lower right, report at the lower left, history at the left, with an arrow from history back to act. Each stage lists the pages that cover it: act b1, b6 and b7; record b2, b3 and b5; judge b4 and b9; report b10; history b11. The stages light one at a time, then the arrow from history back into the next act. act b1 · b6 · b7 record b2 · b3 · b5 judge b4 · b9 report b10 history b11 history feeds the next act counts, never a score b8: the whole loop as a checklist

—Build the layer: act and record

  1. b1The seams the host exposes What the host hands an evidence plugin: an event per exchange naming both sides, a plugin key bound to the node key, capability flags, a page, and stop routing.
  2. b2The record format What one record carries: digests, not payloads; request/response binding; the signer's key id.
  3. b3The local evidence log An append-only log on the node: signed checkpoints, inclusion and consistency proofs, export.
  4. b4Use-case evidence: twins and a referee What a sampled rate tells you, and what a signed verdict on one marked pair adds.
  5. b5Making it portable Open specs and vectors, libraries any host can link, an evidence file any verifier reads offline.

—Apply it

  1. b6Personal agents The same layers for an agent acting for one person, and a History card of counts as the shareable read.
  2. b7Agent work for someone else Both sides' records, evidence requests and settlement legs, when an agent works with a counterparty.
  3. b8The builder's checklist Every step in order: what you need, where it lives today, and its status.

—Close the loop: judge, report, history

  1. b9Judging: a separate step from evidence Who judges, what a judgment record carries, and why a judgment is never rounded into evidence.
  2. b10Reporting: from a verified bundle to a page Verify first, then render from what verified, offline; wording changes never move an evidence id.
  3. b11History back into the loop History as a derived read over sealed records, recomputable by anyone, never a reputation number.