Architecture · 11.07
Durable Orchestration Control Plane
Rules, delivery records, graph revisions, and capability manifests keep agent-authored automation inspectable and recoverable.
Rules and deliveries are separate durable facts
workflow_event_subscriptions stores the declared relationship between a typed source event and a target workflow. workflow_event_deliveries stores each concrete activation attempt. Keeping policy separate from its effects makes the system explainable: an operator can see whether a rule did not match, a delivery is waiting, a worker holds a lease, a retry is scheduled, or a target run was actually requested.
Capability is a pre-dispatch contract
Every adapter projects a versioned RuntimeCapabilityManifest. The runtime evaluates namespaced capabilities and configuration-sensitive requirements — including allOf/anyOf alternatives — before dispatch. An agent therefore receives a typed, actionable capability mismatch instead of repeatedly attempting an operation its runtime cannot perform.
Continue
Agent, Subject, Connection, Orchestration, Experiment, Interface — the backing systems behind each, and why there's no seventh.
The monorepo layout across apps and packages, and the dependency-free boundary checker that fails CI on illegal cross-layer imports.