Docs
Documentation
Concepts and short guides for the Agent Action Capsule — the open profile for verifiable records of what an AI agent did, and the transparency layer it builds on.
Concepts
What is an Agent Action Capsule?
A signed, tamper-evident record of an agent action — and the three properties that make it verifiable.
Statement vs transparency layer
What happened vs where it is recorded — and why the statement is structure-independent.
What is a Transparency Service?
Register, receipt, anchor — and the boundary between a transparency service and a verifier.
Verifiable Data Structures
RFC9162_SHA256 (vds=1) vs CCF ccf.v1 (vds=2), and what stays constant across them.
How verification works
Two independent checks: signature, then inclusion proof — both from the bytes, offline.
Guides
Live & interactive
Explore a capsule
Interactive: click each field, edit what goes into a digest, tamper one and watch the seal break, then verify a bundle as a skeptical auditor.
The public log, live
Watch the transparency log in real time — total entries, latest checkpoint, operating-since, and the most recent records. Public, verifiable, nothing fabricated.
Reference
Building on it? Implementation, tutorials, and adapter guides live in the canonical
capsule-emit docs: capsule-emit/docs ↗. These pages cover the standard-level concepts; the repo docs cover hands-on usage.Status. The Agent Action Capsule profile (draft-mih-scitt-agent-action-capsule-02) is an individual IETF Internet-Draft — submitted for discussion, not adopted by a working group, and not a standard. A companion draft, the Canonical Payload Binding (draft-mih-sokolov-scitt-payload-binding-01), defines the shared canonicalization and digest-binding layer. Both build on the IETF SCITT Architecture (RFC 9943) and the COSE Receipts specification (RFC 9942, now published).