Getting started
Start with the system model: clients request and display work; backend/control-plane authority decides what is allowed and what state is authoritative.
This documentation overview covers stable architectural principles that can be described publicly today. API references and release-specific integration instructions will be published only when the corresponding interfaces are ready and verified.
Start with the system model: clients request and display work; backend/control-plane authority decides what is allowed and what state is authoritative.
Understand the separation between clients, control plane, policy, execution tools, validation, and evidence.
Review permission boundaries, approval gates, least-privilege execution, and auditable state transitions.
Prefer deterministic execution when available; use intelligent capabilities inside explicit task and tool contracts.
Agents are bounded capabilities with defined roles, permissions, inputs, outputs, dependencies, and escalation paths.
Important actions should produce durable records that allow validation, review, and recovery without relying on narrative memory.