Make container isolation the real default.
Move the shipped fleet beyond the cli tier, then finish resource limits, capability dropping, and container hardening.
# Roadmap Available behavior, active hardening, and planned surfaces separated clearly, with Apache 2.0 governance staying in the open tree. Source: https://aioverload.io/roadmap/ {{< section id="available" eyebrow="AVAILABLE NOW" title="The governed execution core." >}} - Event-sourced workflows on NATS JetStream with replay through `aioctl replay`. - Named workflow and agent manifests, acceptance criteria, and registry state. - Reflex step gate, recorded holds, and human approval input. - Gateway-routed MCP decisions and default-deny tool grants. - Forge ingestion into governed task rows without automatic dispatch. - Generic declared-source ingress with deduplication and trigger matching. - CLI, operator console, worker, sidecar, and server surfaces. “Available” points to behavior in the stamped source tree. It does not imply production hardening, a stable release, or support for every runtime. {{< /section >}} {{< section id="progress" eyebrow="IN PROGRESS" title="Close the gaps the threat model names." class="section--tint" >}}
Move the shipped fleet beyond the cli tier, then finish resource limits, capability dropping, and container hardening.
Close the Bash / Edit / Write bypass instead of pretending gateway-only coverage is complete.
Move NATS accounts, bus TLS, and API TLS from an opt-in profile toward a safer operating posture.
Event-driven fleet convergence, acceptance enforcement on every ingested path, and lifecycle write-back.