Workstreams
Actionable operating status for the AIOS work system: owner, next action, gate decision, risk, and proof level.
This page is manually curated and public-safe. It is not live telemetry or a production control plane.
| Workstream | Status | Owner / role | Next action | Gate decision | Blocker / risk | Proof / evidence |
|---|---|---|---|---|---|---|
optimize-worker Execution support layer for routing experiments, benchmark traces, and structured workflow automation. | Active | Lyn + Codex | Keep benchmark trace automation parked until a thin slice is chosen. | Proceed only when scope is narrow and validation is explicit. | Automation can create false confidence if trace quality is unclear. | DocumentedBenchmark trace workflow and regression gate |
Fallback routing Policy lane for choosing a safe alternate route when the primary worker or model is blocked. | Policy active | Lyn | Route work by task type, failure mode, risk, and available worker/model. | Use fallback route when primary surface is blocked or uneconomical. | Cost and token evidence remain incomplete in some surfaces. | Smoke-provenFallback routing policy + smoke test |
Profile positioning Public portfolio framing that turns operating evidence into clear, safe claims. | Active | Lyn + Codex | Keep homepage focused on differentiation; avoid internal dashboard drift. | Public copy must remain portfolio-safe and evidence-backed. | Overclaiming maturity or exposing raw private context would weaken trust. | Regression-gatedv3.0 IA regression checks |
Supernova Opportunity and monetization intelligence lane with a first version complete, before POC validation. | First version done | Lyn | Define the first POC trigger and evidence requirement before treating it as operational. | Do not claim POC or operating usefulness until a concrete run is reviewed. | A completed first version can be mistaken for validated business evidence. | DocumentedFirst version exists; POC not yet run |
Big Crew Scoped execution crew for implementation, architecture review, QA, and release readiness. | Started | Lyn + Codex | Keep Big Crew usage bounded to implementation and verification tasks with explicit handoff. | Use for scoped execution only; do not expand into autonomous staffing. | Parallel work can blur ownership if files, roles, and review gates are not explicit. | DocumentedPatch 1 and Patch 2 implementation handoffs |
Researcher Bounded evidence scanner for market context, claim safety, and external practice checks. | Started | Lyn + Researcher | Use for bounded positioning and claim-safety briefs before public copy changes. | Research output informs copy; Robert/Lyn still gate claims before implementation. | Broad research can drift into market sizing or unsupported uniqueness claims. | DocumentedHomepage differentiation brief |
Investment Team Planned specialist lane for investment workflows after scope and review criteria are defined. | Planned | Lyn | Defer until Supernova produces a first useful signal. | No active build until there is a bounded investment workflow. | Domain risk is high without review criteria and evidence capture. | PlannedPlanning notes only |
Reading Rules
A workstream can be active while still requiring a gate decision before its output counts.
Documented, smoke-proven, and regression-gated mean different things; the page labels them separately.
The table shows public-safe operating status, not raw KB material, keys, logs, or private traces.