ACDC Protocol Specification Skill

ACDC defines authenticatable, chainable data containers for verifiable credentials and data provenance. Built on KERI (identifiers/key state) and CESR (encoding), ACDCs provide granular proof-of-authorship via DAGs of linked containers with graduated disclosure and contractual protection.

Architecture (5 Layers)

1. Structural — Immutability + identity: SAID, schema binding, deterministic serialization, variants
2. Semantic Graph — Composable identity graph: Attribute, Aggregate, Edge, Rule sections
3. Contractual Governance — Regulated exchange: disclosure mechanisms, exploitation protection, IPEX
4. Lifecycle/State — Temporal state: TEL registries, issuance, revocation, blinded state
5. Crypto/Transport — Cryptographic objects: selective disclosure, bulk issuance, CESR native encoding

Top-Level Fields

When present, fields MUST appear in order: [v, t, d, u, i, rd, s, a, A, e, r]. Required: [v, d, i, s]. Mutually exclusive: a (attributes) vs A (aggregate).

Message Types

ACDC: acm (field map), act (fixed fields + attribute), acg (fixed fields + aggregate). Registry TEL: rip (registry inception), upd (update). Sections: sch, att, agg, edg, rul.