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 with bounded durable checkpoint and recovery evidence for structured workflows. | Mechanical continuity evidenced | Sararin + Codex | Keep human operational value and continuous production operation unresolved until separately evidenced. | Proceed only when scope is narrow and validation is explicit. | Automation can create false confidence if trace quality is unclear. | Bounded mechanical proofTested interruption checkpoint and recovery criteria |
Fallback routing Policy lane for choosing a safe alternate route when the primary worker or model is blocked. | AIOS Enforcement v0.2 canonical and AVAILABLE | Sararin | Use additive v0.2.1 checker tooling under v0.2; keep v0.3 candidate/inactive. | 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 | Sararin + Codex | Keep homepage focused on differentiation; avoid operations-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 bounded Stakeholder Core candidate on canonical main. | First version complete; Stakeholder Core is a bounded canonical candidate. | Sararin | Keep POC validation and R01 start unauthorized and unproven until their gates pass. | Do not claim POC or operating usefulness until a concrete run is reviewed. | Candidate personas can be mistaken for active operational roles or validated business evidence. | DocumentedFirst version exists; POC not yet run |
Data Team Evidence structure, aggregation logic, interpretation, and dashboard-readiness review lane. | Evidence lens active | Sararin + Data Team | Keep evidence structure, aggregation logic, interpretation, and dashboard-readiness review explicit before stronger dashboard claims. | Supports evidence quality and interpretation; does not act as final claim authority. | Dashboard metrics can be mistaken for behavior proof if aggregation gaps and evidence limits are hidden. | DocumentedRuntime authority and monitoring evidence pages |
Big Crew Bounded specialist delivery workspace with explicit handoff and separate receipts. | Started | Sararin + 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. | Started / boundedPatch 1 and Patch 2 implementation handoffs |
Researcher Bounded evidence scanner for market context, claim safety, and external practice checks. | Started | Sararin + Researcher | Use for bounded positioning and claim-safety briefs before public copy changes. | Research output informs copy; GPT/Sararin 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 | Sararin | Defer until Supernova completes POC validation or another bounded investment trigger is approved. | 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.