Org Chart & Role Policy
Public-safe operating map for who owns coordination, execution, evidence, review, and budget discipline inside the AIOS work system.
This is an operating model summary, not runtime access control, autonomous staffing, or production-readiness evidence.
Operating Org Chart
KB-sourced summaryLyn / Robert
Executive review and protected decisions
Robert
Personal AI context layer and KB continuity
Hermes
Stage manager, router, trace, and handoff owner
Robert KB + Git
Shared source of truth for decisions, evidence, and handoffs
Codex
Repo and UI implementation
Big Crew
Product, architecture, QA, review
Researcher
Evidence scans and claim safety
Supernova
Opportunity and monetization analysis
Investment Team
Planned specialist lane
optimize-worker
Routing and trace automation
Fallback routing
Alternate path policy
Future crews
Only after scope is proven
Role & Responsibility Policy
| Role / team | Responsibility | Owns | Does not own | Budget policy | Escalation rule |
|---|---|---|---|---|---|
| Robert / Lyn | Executive review, taste, risk appetite, and final approval for public, money, legal, privacy, reputation, health, career, and major architecture decisions. | Final gate and protected decisions | Routine execution or broad staffing before evidence exists | Lyn-gated | Stop and ask when the decision is high-risk or hard to reverse. |
| Hermes | Stage manager, dispatcher, trace recorder, KB maintainer, and task packet owner. | Routing discipline, validation summaries, and KB sync | UI/code implementation or autonomous final approval | Cheap/local first | Route to Codex, Big Crew, Researcher, Supernova, or Lyn when scope requires it. |
| Codex | Repo, UI, and code implementation executor for bounded task packets. | Files changed, build/regression evidence, commit-ready patches, and caveats | Product strategy, private raw KB exposure, or production-readiness claims | Implementation lane | Return evidence and stop when the task exceeds the packet or exposes risk. |
| Big Crew | Scoped product, architecture, engineering, QA, review, and release-readiness work. | Role-specific critique, implementation support, QA findings, and release recommendations | Autonomous staffing, final release approval, or Lyn-protected decisions | Senior synthesis only | Use senior model review only for named decisions with clear expected value. |
| Researcher | Bounded external evidence scans for market context, public claims, and practice checks. | Cited evidence, safe-claim boundaries, and research briefs | Final decisions, market certainty, or unsupported uniqueness claims | Cheap/web first | Escalate only when synthesis changes a public claim or decision gate. |
| Supernova | Opportunity and monetization intelligence through advisor-style memos and trigger-based analysis. | Business option framing, kill arguments, and monetization questions | Active execution before a concrete trigger exists | Trigger-based | Activate only when the business question is bounded and reviewable. |
| Investment Team | Planned investment advisory lane after Lyn defines scope, criteria, and evidence requirements. | TBD investment workflow once scoped | Live investment action, recommendations, or decisions today | Not active | Remain parked until scope and review policy exist. |
| optimize-worker | Routing and workflow execution support for benchmark traces, fallback paths, and thin-slice automation. | Structured runs, trace shape, and repeatable validation support | Final interpretation, provider expansion, or autonomous production routing | Cheap/local first | Escalate when automation would create false confidence without trace quality. |
Budget Policy
Role first, model second. Budget is allocated like workforce salary: use the cheapest reliable route for routine work and reserve senior review for named decisions with a clear expected value.
Use for formatting, task packets, trace updates, markdown cleanup, extraction, checklists, and low-risk structured work.
Use only when a named review, critique, tradeoff, or decision-quality output needs senior judgment.
Reserved for rare foundation decisions and Lyn-protected categories; requires an explicit gate.
Codex is used for repo and UI implementation by role fit, with files, validation, commit, and caveats returned.
No senior delegation without a named decision, expected value, cost cap, and abort condition.
Task Routing Policy
Use a bounded task packet, then return files changed, validation, commit hash, and caveats.
Use role-specific review for a named decision, then Lyn gates the final call.
Gather cited evidence and safe-claim boundaries; do not make the final claim.
Activate only when there is a concrete business trigger and a reviewable output.
Keep the work structured, public-safe where needed, and synced back to the KB.
Stop for executive review; no delegated role owns the final decision.