WorkGraph is Meerkat’s durable commitment graph for agents. It answers:Documentation Index
Fetch the complete documentation index at: https://docs.rkat.ai/llms.txt
Use this file to discover all available pages before exploring further.
- what work exists?
- what is blocked?
- what is ready?
- who claimed it?
- what evidence supports completion?
- what is terminally done, failed, or cancelled?
Mental Model
WorkItem is a durable commitment. Edges describe topology such as
blocks, parent, related, supersedes, and derived_from. Readiness is
derived by the WorkGraph subsystem from item state, time gates, claims, and
topology.
What WorkGraph Owns
- item lifecycle status
- dependency legality and graph topology
- readiness and claimability
- claim ownership, leases, and revision checks
- terminal state
- evidence references
- event history and current-state projections
Boundaries
| Need | Use |
|---|---|
| Shared durable work, dependencies, readiness, claims, evidence | WorkGraph |
| One-off private scratch tracking | Builtin task_* tools |
| Time-based wakeups and recurrence | Schedule |
| Recalled knowledge and compacted context | Memory |
| Live collaboration messages | Comms |
Namespaces
Every item belongs to a realm and namespace. The default namespace isdefault, but applications can use names such as session/{id}, mob/{id},
or domain-specific namespaces. Namespaces are a scoping tool, not a promise
that every group is semantically meaningful.
