Ouroboros (Deferred)

Ouroboros is a future concept only. FractalOps currently has no Ouroboros template, runtime, route, CLI command, scheduler, principal profile, Armory default, or operational job. Agent Studio and project-local AgentSquad are the only active ownership model.

Reintroduction gate

Do not add partial aliases or compatibility shims. Reintroduction requires all of the following:

AgentSquad identity switching, recovery, mailbox continuity, and single-sandbox process isolation are stable in production.
Canary and live evidence include a successful 24-hour soak with bounded resource use.
A new assembly-owned ADR defines the outcome, bounded context, owner, capacity model, authorization boundary, rollback, and relationship to AgentSquad.
Contract, backend, frontend, and assembly repositories accept explicit artifact and release-order changes.
The implementation proves it does not create a competing control plane, duplicate agent identity, or bypass proposal-bound writes.

Until those gates pass, references to Ouroboros outside this page are defects.