Reference

Glossary

The core vocabulary of the Agent Action Capsule and the transparency layer it builds on.

TermDefinition
SCITTSupply Chain Integrity, Transparency, and Trust — the IETF working group and architecture for registering signed statements in transparency services. Its specifications are drafts, not yet RFCs.
SCITT profileA specialization of the general SCITT signed-statement format for a domain. The Agent Action Capsule is the profile for agent actions — it builds on SCITT/COSE and interoperates with any SCITT transparency service, rather than being a separate standard.
COSECBOR Object Signing and Encryption — the signature format used for statements and receipts.
COSE_Sign1A single-signer COSE structure: one signature over a protected header and payload. The envelope an Agent Action Capsule uses.
Signed StatementA COSE_Sign1 claim about something — here, an agent action. The capsule is a profiled Signed Statement.
Agent Action CapsuleThe profile in this project: a Signed Statement over application/agent-action-capsule+json committing to an action and its input/output digests.
Transparency ServiceA service that registers Signed Statements into an append-only log, issues receipts, and publishes tree heads and proofs.
Transparency logThe public, append-only log a Transparency Service maintains. It is publicly readable — anyone can fetch its entries and verify any one of them; nothing is taken on trust.
LedgerYour local append-only trail of capsules (e.g. ledger.jsonl) — distinct from the public transparency log. The ledger is yours; the transparency log is the shared, anchored record.
ReceiptA signed proof, returned by a transparency service, that a statement was included in its log. Verifiable offline against the log key.
VDSVerifiable Data Structure — how a log proves inclusion and consistency. vds=1 is RFC9162_SHA256; vds=2 is CCF (ccf.v1).
Inclusion proofEvidence that a specific leaf is part of the log at a given size — answers “is my record in the log?”
Consistency proofEvidence that one tree head is an append-only extension of an earlier one — answers “did the log stay honest?”
STHSigned Tree Head — the log's current Merkle root and size, signed, so verifiers and witnesses can pin its state.
Merkle treeA hash tree whose root commits to every leaf; the structure behind RFC 9162 inclusion and consistency proofs.
RFC 9162Certificate Transparency 2.0 — the published RFC whose SHA-256 Merkle proofs back vds=1.
CCFConfidential Consortium Framework — Microsoft's open-source ledger framework whose receipts back vds=2.
Go deeper — implementation & usage docs in capsule-emit: Concepts, in plain words ↗