Public proof surface

Evidence reconciled through 20 July 2026

Release scope: Architecture, Achievements, Knowledge Sharing

Source: GPT KB + Git

Curated static release — not a continuous live-status feed

Release: AIOS profile v0.2 + Governance layer update

Map / not livePhase 4 result: proceed with fallback

Agent Orchestration Map

A visual map of how AIOS work is routed, reviewed, gated, and improved using fallback-safe role labels. This is a documented role-and-boundary map, not runtime execution proof; availability is static unless a matching worker receipt exists.

This is a map, not a dashboard. It does not represent live telemetry, autonomous orchestration, provider comparison, benchmark proof, cost-saving evidence, or final role-registry truth. Source of truth remains committed KB docs, git history, receipts, validation artifacts, and Sararin / GPT decisions.

Count summary

Human lead

Sararin

Gate owner

AI Workforce Source Status

Verified by workspace registry

No global count shown

Big Crew

Bounded specialist delivery workspace

Started — explicit handoff and separate receipts

Supernova

Business intelligence workspace

Bounded canonical candidate; POC and R01 start unproven.

Investment Team

parked / TBD / not countable

Future lane
WHO

1. Who does what

Agent and role lanes show who owns routing, execution, evidence, and gates.

Agent / role surface
Human Gate

Sararin

Sets the release decision and human boundary.

Final approval
Executive Orchestration

GPT

Classifies work, checks claims, and keeps scope bounded.

Context and review
Operator / Handoff

Hermes

Packages handoffs and keeps the worker lane clear.

Stage management
Implementation Lane

Codex

Changes files, runs checks, and reports evidence.

Scoped execution
Research Support

Researcher

Finds sources, receipts, and limits for claims.

Evidence scan
Low-risk Support

Simple Task Supporter

Handles simple support work only after boundary confirmation.

Contract confirmation pending
Big Crew

Engineering / Quality role group

Engineering review workspace with explicit handoff and separate receipts; it is not an autonomous team claim.

Started — bounded specialist delivery
Supernova

Business / Opportunity Intelligence workspace

Frames opportunities, risks, options, and business evidence; candidate personas are not active operational roles.

Bounded canonical candidate
Future / Parked

Investment Team

Acknowledged future lane with no countable registry yet.

TBD / not countable
UX/UI: engineering capability tag, not separate roleInvestment Team: parked / TBD / not countable
HOW

2. How work moves

Example task enters AIOS, gets classified, packaged, executed, reviewed, gated, and converted into a learning artifact.

Orchestration flow
1
Intake

Sararin / GPT

Example task enters AIOS with purpose, risk, and expected output.

Intent
2
Classify

GPT

GPT identifies task type, risk level, and safest lane.

Lane
3
Package

Hermes

Work is prepared as a bounded handoff.

Packet
4
Execute

Codex / Big Crew / Supernova / Researcher / Simple Task Supporter

The selected worker lane creates the artifact or review input.

Output
5
Evidence

Executor / Researcher

Receipts, sources, validation notes, or limits are captured.

Trace
6
Review

GPT / Reviewer

Output is checked for DoD, claims, and boundary risk.

DoD
7
Sararin Gate

Sararin

Sararin approves, revises, rejects, or parks the work.

Gate
8
Outcome

GPT / Codex

Work is committed, published, revised, stopped, or archived.

State
9
Learn

GPT / KB

Lesson becomes checklist, prompt, or role rule update.

Rule

Supernova role registry and POC boundary

Supernova: first version complete; POC not yet validated.

Opportunity Framer

Decision frame

Market & Pain Reality Analyst

Pain evidence

Brand & Positioning Strategist

Claim boundaries

Business Model & ROI Strategist

Economics view

Budget & Resource Optimizer

Resource guardrail

Marketing & Sales Channel Strategist

Channel test

Finance / Tax / Legal Gatekeeper

Risk flags

KPI & Metrics Analyst

Metrics threshold

Strategy Options Advisor

Option tradeoffs

Risk & Execution PM

Execution plan

CONTROL

3. How control and learning work

Evidence, review, Sararin Gate, rework, enforcement rules, and improvement outputs keep the map bounded.

Human feedback + rule enforcement

Evidence gate

Executor / Researcher

Receipts, artifacts, validation, and source notes are captured.

Review gate

GPT / Reviewer

Scope, claims, Definition of Done, and risk are checked.

Sararin Gate

Sararin

Sararin approves, revises, rejects, or parks the work.

Rework loop

GPT / Worker lane

Feedback is classified, revised, checked, and captured.

Improvement output

GPT / KB

The lesson becomes a checklist, prompt, role contract, or routing rule.

Human feedback + rule enforcement
Feedback classified
Rule impact checked
Agent revises
Guardrail updated
Enforcement verified

Rework is treated as an evidence signal. Repeated feedback should become a checklist, prompt update, role contract, routing rule, stop condition, downgrade rule, KB note, or follow-up task. A rule only counts as improved when it becomes visible in a future check, route matrix, monitor status, or validation gate. This does not mean agents learn automatically.

Source-truth and registry notes
  • AIOS does not publish a global agent count until each workspace is backed by a committed registry or contract.
  • Big Crew: started bounded specialist delivery with explicit handoff and separate receipts.
  • Supernova: Stakeholder Core is a bounded canonical candidate; POC and R01 start are unproven.
  • Simple Task Supporter: low-risk support lane, contract confirmation pending
  • Investment Team: parked / TBD / not countable
  • UX/UI: engineering capability tag, not separate role
  • Big Crew role names remain hidden until source-of-truth confirmation is complete.
  • Simple Task Supporter contract confirmation is pending.
  • Investment Team is parked / TBD / not countable.
  • UX/UI is a capability tag, not a separate role.
Big Crew source boundary

Started bounded specialist delivery; autonomous execution is not claimed.

Big Crew is a bounded specialist delivery workspace with explicit handoff and separate receipts; this does not claim an autonomous team, active roster, or self-validation.

Source: team-of-team-orchestration/role-output-contracts.md

Supernova source boundary

Stakeholder Core is a bounded canonical candidate.

The candidate defines stakeholder decision-support personas, not active operational roles. POC validation and R01 start are not yet authorized or proven.

Source: supernova/stakeholder-core/README.md + registry.json

Global count boundary

No global AI workforce count is shown.

The page avoids a single global agent count because some lanes are active, some are parked, and some are capability tags rather than standalone roles.

Source: team-of-team-orchestration/specs/aios-agent-review-dashboard-data-contract-v0.1.md

What this map helps catch
  • unsupported counts
  • role registry conflicts
  • wrong worker/lane assignment
  • missing evidence
  • wrong Definition of Done delivery
  • overclaim risk
  • repeated rework patterns
What this map does not prove
  • live telemetry
  • autonomous orchestration
  • real-time telemetry
  • provider comparison
  • benchmark performance
  • cost-saving evidence
  • production-grade observability
  • final role-registry truth