Specification

ACDP RFC specifications

ACDP RFC Index

This directory contains the normative RFCs that define the Agent Context Distribution Protocol (ACDP). ACDP is a coordination-agnostic substrate for publishing, discovering, and verifying units of agent-produced content; v0.1.0 is the first published version.

RFCTitleStatus
RFC-ACDP-0001Core — identifiers, JCS, hashing, signaturesFinal
RFC-ACDP-0002Context BodyFinal
RFC-ACDP-0003Publish & SupersessionFinal
RFC-ACDP-0004Retrieval & LineageFinal
RFC-ACDP-0005Discovery (keyword search)Final
RFC-ACDP-0006Cross-Registry ReferencesFinal
RFC-ACDP-0007Capabilities & ErrorsFinal
RFC-ACDP-0008Security & Threat ModelFinal
RFC-ACDP-0009Extensions (lifecycle, attestations, walks)Reserved

Reading order

The numbering matches dependency order. Read top-to-bottom:

  1. RFC-ACDP-0001 Core — identifiers, JCS canonicalization, content hashing, signatures, time format.
  2. RFC-ACDP-0002 Context Body — the immutable signed body; context types; data references; visibility.
  3. RFC-ACDP-0003 PublishPOST /contexts, supersession constraints, registry-assigned fields.
  4. RFC-ACDP-0004 RetrievalGET /contexts/{ctx_id} and lineage queries.
  5. RFC-ACDP-0005 Discovery — keyword search.
  6. RFC-ACDP-0006 Cross-Registryacdp:// URI scheme and resolution flow.
  7. RFC-ACDP-0007 Capabilities/.well-known/acdp.json and the error envelope.
  8. RFC-ACDP-0008 Security — threat model and required defenses.

Reserved (no normative text, numbering pinned for future work):

  • RFC-ACDP-0009 Extensions — retraction/lifecycle events, post-publication relationships, attestations, push subscriptions, server-side traversal.

RFC lifecycle

Draft → Review → Final Comment Period → Release Candidate N → Final (or Rejected). Reserved is a sidebar state for placeholder RFCs (e.g. RFC-ACDP-0009). See governance/RFC-PROCESS.md and VERSIONING.md.