API reference
The public API is organized around stable package boundaries rather than one monolithic client. The machine-readable public API manifest records the supported package entry points used by this documentation.
Core entry points
| Package | Representative entry points |
|---|---|
@agentplat/collective-runtime | missions, checkpoints, collective decisions, continuity, teams and sparse peers |
@agentplat/collective-membership | lineage, agent factory and governed lifecycle |
@agentplat/collective-quorum | partial-view and sparse agreement |
@agentplat/collective-sync | signed causal synchronization |
@agentplat/mesh | coordination, continuity, durability, trust and sparse overlays |
@agentplat/audit / @agentplat/trust | evidence, telemetry and eligibility |
API signatures must be read together with the relevant concept and safety pages. A callable function does not by itself grant authority: policy, identity, lease and evidence requirements determine whether an operation is admissible.