Resume bundles, claims, refs, and handoffs replace “remember what the previous agent meant.”
A system of owned state, not one omniscient agent
Work that survives the session.
The AgentOps ecosystem turns intent into scoped execution, then preserves the state, evidence, knowledge, and recovery path required for the next operator or agent to continue safely.
Who owns what?
Select a domain to inspect its authority, artifacts, and boundaries. Repository boundaries follow state ownership; shared visibility does not imply shared write access.
Trace one change
Switch between a human-led session and queued dispatch. The route changes; the proof obligations do not.
Authority matrix
The useful question is not “which tool can see this?” but “which contract may change it?” The table is intentionally asymmetric.
| System | Owns | May mutate | Portable projection | Must not become |
|---|---|---|---|---|
| sprintctl | work, claims, handoffs | sprint state | resume / handoff / render | project manager or swarm lock |
| kctl | knowledge review lifecycle | its candidates and entries | knowledge Markdown / JSON | backlog writer |
| actionq | action and session lifecycle | queue state through actionctl | append-only events | direct repository editor |
| actionq-dispatch | one bounded execution cycle | isolated worktree + contract writes | branch, result, gate evidence | unbounded autonomous loop |
| auditctl | repo-local audit evidence | audit index and shards | daily NDJSON | hidden central ledger |
| cockpit | composed operator view | only via owner APIs | read models and links | cockpit-shaped monolith |
Try the cockpit view
This public demo uses synthetic state to show how the operator surface composes repository, sprint, claim, dispatch, and audit projections. It has no connection to the private deployment and intentionally exposes no write controls.
Active work and claims
Dispatch and audit feed
Boundary: this screen renders projections. A real mutation must return through sprintctl or actionctl with the required ownership proof.
Why the parts exist
Every component exists to remove a concrete ambiguity. Otherwise it is distributed-systems cosplay.
One action, one worktree, explicit path ACLs, pre/post gates, and a branch that survives failure.
Events remain evidence. kctl requires review before durable or coordination lessons become published artifacts.