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.

Start here

Read a ledger before you write one. Steps 1 and 2 install nothing — you read two real ledgers and check them yourself; step 3 is where you produce one.

1 · See a ledger ↗

Two real agent runs shown beside the capsules that record them — the run you hold vs. the ledger anyone can check. Nothing to install.

2 · Verify one yourself

Signature, then inclusion proof — from the bytes alone, in the browser, on the command line, or as a library.

3 · Produce your own

Now seal a capsule with one seal() call, witness it, and verify it. Copy-paste-runnable.

Use cases

Where the record layer applies today — decentralized inference, and composing with other logs.

Case study: Mesh-LLM

Accountability for strangers' machines, with no central operator and no ranking of nodes.

Interop

The TRACE Registry

An independent public registry whose checkpoint layer uses CLL — what it records, which parts it uses, and how to check an entry yourself.

Concepts

You've reached a witness

Followed a link from a checkpoint or a receipt? Start here — what it shows, what it never does, and how to check it yourself.

What is an Agent Action Capsule?

A signed, tamper-evident record of an agent action — and the three properties that make it verifiable.

How it works

Both sides: the organisation seals each action and registers a checkpoint with a Transparency Service, which fixes the date; later, a party entitled to ask requests a slice and recomputes the answer offline.

Statement vs transparency layer

What happened vs where it is recorded — and why the statement is structure-independent.

What is a Transparency Service?

Verifiable Data Structures

RFC9162_SHA256 (vds=1) vs CCF ccf.v1 (vds=2), and what stays constant across them.

How verification works

Three independent checks: the capsule_id, the signature, then the inclusion proof — all from the bytes, offline.

Trust map: what each check shows

Each check in plain words, for any exchange between agents: what it shows, what it does not show, and how it reads in two settings.

What's consequential

Seal what changes the world, plus reads of sensitive data; everything else is observability.

How it composes with your stack

Identity, authorization and transparency logs stay where they are; the capsule references their evidence by digest.

Witness anywhere

Only a digest and a timestamp leave: witness at the public log, run your own, or self-host where the hash never leaves.

Guides

Quickstart

Seal your first capsule with one seal() call, witness it, and verify. Copy-paste-runnable.

Verify a capsule

Verify in the browser, on the command line, or as a library — same checks everywhere.

A2A + AP2 example

An A2A callee seals a capsule on every AP2 payment action: the mandate is the ‘may’, the capsule is the ‘did’.

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.

Reference

Specifications

Every Internet-Draft in the family, its current revision and status from the Datatracker, its test vectors, and the open-source code that implements it.

Witness directory

Services that accept a checkpoint and return a receipt you can check offline — alphabetical, none privileged.

Glossary

SCITT, COSE_Sign1, Receipt, VDS, inclusion & consistency proofs, the disposition list, witness vs anchored.

Translation: dev / auditor / spec

The same concepts and verbs in three registers — the word a developer, an auditor, or the spec text would use.

Extensions

Bilateral attestation

When two organizations act together: each party holds proof of the other's commitment, checkable by a third party who trusts neither.

Project

Governance

Open and built to be donated to a neutral foundation; governance modeled on Linux Foundation practice.

Patent posture

The specifications are unencumbered: the provisional applications were expressly abandoned, and no license is required.

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, latest revision on the Datatracker) 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, latest revision on the Datatracker; site), 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).