Product / Execution
Autonomy needs durable ownership
An agent that can act without an owning scheduler, explicit authority boundaries, and a recovery path is a liability, not a capability. Execution in Omnacta OS is built around immutable plans, leased work, and compensable effects.
Local, transactional execution with checkpoint-based recovery is implemented for the reference workflow. Cross-repository sagas and multi-tenant scheduling are in development.
Immutable plans, scheduler-owned
Once a plan is versioned, it does not silently mutate mid-execution. The scheduler, not any individual worker or agent, owns the authoritative mission state. Capability negotiation matches available workers, model routes, and tools against plan requirements before work is assigned.
Progressive authority levels
Authority is granted incrementally and explicitly, never assumed. Each level below is a distinct scoped grant, not a permission toggle.
| Level | What it permits |
|---|---|
| Observe | Read-only access to state; no effects can be produced. |
| Propose | Can draft changes for review; nothing is applied without approval. |
| Execute isolated | Can apply changes within a sandboxed, disposable environment. |
| Integrate governed | Can apply changes to shared systems under policy and approval gates. |
| External effects | Can take actions with consequences outside the controlled environment, under the strictest gates. |
Checkpoints, leases, and recovery
Missions are expected to outlive individual workers, connections, and sessions. Recovery behavior is explicit for each failure class rather than left undefined.
Worker loss
The lease expires, the checkpoint is reassigned, and execution resumes from the last durable state.
Cancellation
In-flight effects are completed to a safe boundary or compensated; partial state is not left dangling silently.
Deadline exceeded
The mission is paused and escalated rather than allowed to run unbounded.
Uncertain external effect
The mission blocks and reports the uncertainty instead of guessing at the outcome.
Current host and sandbox boundaries
- Transactional changes are proven for local, single-repository execution today.
- Cross-repository saga coordination and compensation are in development.
- Sandbox isolation depends on the host environment's capabilities and is not uniform across every deployment mode.
- External-effect actions require the strictest authority level and remain the most limited in current scope.
Execution produces evidence
Every executed step is expected to leave an evidence trail, verified against acceptance criteria.