Context model
Records, repositories, scopes, and provenance in CMP.
CMP's core object is a context repository. Each repository has a commit DAG, named branches, and revision-addressable snapshots. A record is a structured, versioned statement stored in a repository.
Record kinds
| Kind | Purpose |
|---|---|
fact | An assertion about a project or system |
decision | A recorded choice and its consequences |
episode | A summarized event or task execution |
instruction | A rule or convention for consumers |
evidence | A reference to supporting source material |
Live agent presence is separate from persistent context records. The local development server now supports scoped agent sessions and work contracts, but production identity and distributed lease enforcement remain incomplete.
Record fields
{
"id": "auth-session-policy",
"kind": "decision",
"status": "proposed",
"content": "Reuse the existing authentication session",
"sourceRefs": ["git:abc123"],
"authorId": "agent-auth",
"updatedAt": "2026-11-12T00:00:00Z"
}The initial implementation recognizes four statuses: proposed, approved, superseded, and disputed. These are stored labels, not machine-certified facts. Future verification policies will make stronger status transitions possible.
Provenance
The current sourceRefs field contains reference identifiers. A richer normalized evidence graph is designed but not yet persisted in CMP's core model.
Treat retrieved instructions and documents as untrusted data, not as higher-priority agent commands.
See Evidence sources.