Expand description
§acdp-types — wire types for the Agent Context Distribution Protocol
The protocol’s JSON wire shapes: the immutable body::Body,
publish::PublishRequest/publish::PublishResponse, data
references, capabilities documents, registry receipts, and search
parameters/results — plus the profile vocabulary. The opaque
identifier primitives and error vocabulary live in
acdp-primitives and are re-exported
here under the historical primitives path.
Re-exports§
pub use body::Body;pub use body::DataPeriod;pub use body::FullContext;pub use body::RegistryState;pub use body::Signature;pub use capabilities::CapabilitiesDocument;pub use capabilities::Limits;pub use data_ref::DataRef;pub use data_ref::DataRefType;pub use data_ref::EmbeddedContent;pub use data_ref::EmbeddedEncoding;pub use data_ref::Location;pub use publish::PublishRequest;pub use publish::PublishResponse;pub use receipt::ReceiptSigner;pub use receipt::RegistryReceipt;pub use search::SearchParams;pub use search::SearchParamsBuilder;pub use search::SearchResponse;pub use search::SearchResult;
Modules§
- body
- capabilities
- data_
ref - Data references —
acdp-data-ref.schema.json. - primitives
- profile
- ACDP conformance profiles (RFC-ACDP-0001 §9.1).
- publish
- receipt
- Registry receipts (ACDP 0.2, RFC-ACDP-0010 — promoted from the RFC-ACDP-0009 §2.7 reservation).
- search
Structs§
- Agent
Did - A Decentralized Identifier — v0.1.0 mandates
did:web. - Content
Hash sha256:<64-lowercase-hex>— content-addressable hash with algorithm prefix.- CtxId
acdp://<authority>/<uuid-v4>— registry-assigned context identifier.- Lineage
Id lin:sha256:<64-lowercase-hex>— registry-assigned lineage identifier.- Wire
Error - Wire error envelope returned by the registry on all error responses.
- Wire
Error Body
Enums§
- Context
Type - Registered context types plus open-ended custom namespace.
- Status
- Registry-derived lifecycle status.
- Visibility
- Visibility level of a context.