Glossary
Entity and observation
An entity names a subject. An observation records a statement about it, with authorship and supporting evidence. Supersession records which previous observation a correction replaces. A current observation is resolved server-side; it is distinct from a checkpoint.
Scope and checkpoint
A scope identifies a project or task. A checkpoint is an immutable snapshot of working state. A revision identifies its position in recorded history, not its authority over competing branches. The current pointer names the accepted checkpoint.
Branch and reconciliation
A branch preserves a normal write against an older checkpoint parent. Reconciliation explicitly folds competing heads into a selected result while retaining history. An accepted lineage is the history leading to the selected checkpoint; v3 facts and loops are read from that lineage.
Record and patch
Record adds fact/loop changes without resending state. Patch modifies state through a merge patch. In v3, both require the current parent; a stale request returns a conflict.
Resume and coverage
Resume rebuilds scoped context under a budget. Coverage reports included and total counts and omissions for each section. Provenance identifies where a returned value was recorded.
Identity and coordination
A lane is a client process bound to an exact agent identity. Tracked delivery means message state is recorded, not that action is guaranteed. ACP is the Adaptive Coordination Protocol: a coordination discipline with owners, expected reply times, and explicit handoffs. It does not by itself run an unattended agent scheduler.
Authorization modes
Observe preserves legacy compatibility. Mixed allows rollout while reserving enforced principals. Required requires per-agent proof for protected agent operations. These are deployment settings; supporting a feature is not the same as enabling it.