OS9 is a fleet product before it is an execution free-for-all. Each fleet carries purpose, connector reach pressure, and an honest view of what remains blocked.
This shell inherits authenticated page-route posture and is not exposed as a public marketing surface.
Runner registration and connector mutation stay blocked; signed Mission approval issuing, sandbox eval summaries, cost visibility, and operator sandbox interrupts are live.
Published /api/v2/os9 fleets, runners, approvals, and mission contracts use route-level auth and explicit OpenAPI registration; broader OS9 APIs remain closed.
The external domain model starts with explicit fleet objects.
Currently operating inside the admitted product boundary.
Visible for product proof without widening public claims.
Explicitly blocked instead of silently half-enabled.
Govern cross-substrate operations with explicit policy and stop authority.
Package internal Aweb substrate into governed customer-facing OS surfaces.
Coordinate monitored commercial interventions without widening spend posture.