Feature packets
Work lives in traceable TASK-### bundles with specs, plans, reviews, and handoffs — not scattered threads.
Product
Best-in-class agent OS
Kitchen to table
Capabilities, organization tiers, skills, and workflows — public overview without operator internals.
Platform capabilities
What every ChuboOS workspace is built to do — at a glance.
Core and optional skills
A core role set ships with every ChuboOS workspace; optional modules and template packs extend crypto, compliance, game, mobile, and platform infra when you enable them per project.
Orchestrator and sub-agents
One orchestrator delegates isolated workers; independent QA and release sessions are enforced by design.
Human gates
Tier 2+ changes require explicit human approval records before implementation proceeds.
Git-native evidence
Decisions and validation live in repositories; chat is steering, not the system of record.
Regulated and high-risk domains
Optional modules for clinical AI, privacy, legal review prep, payments, and smart-contract surfaces — with specialist review paths and human promotion gates.
IDE adapters
Platform manifests are IDE-agnostic; editor skills and rules are adapters — more environments can share the same spine.
Hosted operator experiences
Browser workspaces and portals can run on a pinned ChuboOS revision so teams orchestrate work without receiving proprietary kitchen source.
Optional venture modules
Enable game, mobile, infra platform ops, Web3, and middle-management tiers per project — without forking core OS behavior.
Organization tiers
ChuboOS supports a three-tier org model (research-backed). Tier 1 C-suite stays human-owned; optional modules add middle-management leads, executive advisory memos, and specialist/sub-specialist decomposition.
| Tier | Roles | Summary |
|---|---|---|
| Tier 1 — C-suite (human root) | Human operator / founder; optional co-founder or operator peer | Owns vision, portfolio priorities, and material approval gates (merge, deploy, secrets). Org charts may label exec hats such as CEO, CTO, CPO, or COO — labels are RACI documentation, not agent roles. |
| Tier 1 — Executive advisor (optional agent) | Executive advisor skill | Memo-only challenge and exec summaries. Cannot dispatch implementers, QA, release, or leads; cannot sign gate bundles. |
| Tier 2 — Middle management (optional) | Product, engineering, QA, and design leads; program manager | Decompose large packets, coordinate rollups, and escalate vision vs velocity tensions to humans — without replacing core QA or release isolation. |
| Tier 3 — Specialists and sub-specialists (optional) | Platform ops, domain modules, template packs | Bounded specialist slices (for example Terraform, AWS, Go under platform ops) with rollups to engineering lead or orchestrator. |
| Core execution (always available) | Core skills table below | IC and orchestration roles every workspace includes — PM, architect, developer, QA, security, release, and others. |
Core skills
Included in every ChuboOS workspace after bootstrap. These roles cover discovery through independent QA, security review, and release — without enabling extra modules.
Project management
Packet lifecycle, program coordination, and orchestration entry points.
| Role | Tier | What it covers |
|---|---|---|
| Intake coordinator | Core | Guided discovery, dedupe, and routing into governed packets. |
Product and design
Scope, journeys, and acceptance criteria.
| Role | Tier | What it covers |
|---|---|---|
| Product manager | Core | Discovery, scope, and acceptance criteria. |
| UI/UX designer | Core | Journeys, states, accessibility, and copy handoff. |
Engineering
Design and implementation of approved slices.
| Role | Tier | What it covers |
|---|---|---|
| Technical architect | Core | System design, trust boundaries, and architecture decision records. |
| Software developer | Core | Approved implementation slices. |
| Frontend engineer | Core | Approved UI implementation and accessibility. |
| Data engineer | Core | Schema, pipelines, and migrations. |
| Data and BI engineer | Core | Events, metrics, lineage, and dashboards. |
| AI/LLM engineer | Core | Prompts, retrieval, models, evals, and tool authorization boundaries. |
Quality, security and release
Independent verification and ship discipline — QA and release never share a session with the implementer on the same slice.
| Role | Tier | What it covers |
|---|---|---|
| QA engineer | Core | Test plans, evidence, and independent verification. |
| Application security engineer | Core | Auth, data handling, uploads, payments, and AI tool boundaries. |
| Release manager | Core | Merge brief and release readiness. |
Optional skills and modules
Enabled per project when your risk profile or program scale requires them — C-suite advisory, middle-management leads, compliance, Web3, game, mobile, or platform infra. Optional packs do not replace core QA, security, or release gates.
Executive tier and C-suite (optional module)
Tier 1 — human-rooted strategy. Enable exec-advisory on org chart v2 when the operator wants structured challenge memos alongside human C-suite hats.
| Role | Tier | What it covers |
|---|---|---|
| Human C-suite root (operator) | Optional | Founder or operator on the org chart — owns strategy, portfolio tradeoffs, and human gate signatures; may document CEO, CTO, CPO, COO, or other exec hats. |
| Co-founder / operator peer (human) | Optional | Optional second human exec on the chart — shared RACI with the root operator; still not an agent role. |
| Executive advisor | Optional | Agent skill (Model B) — exec advisor memos and challenge questions only; orchestrator may read memos for synthesis, not gate clearance. |
Middle management — Tier 2 (optional module)
Leads and program manager for squad or program org profiles — requires org-chart v2 and middle-management module.
| Role | Tier | What it covers |
|---|---|---|
| Engineering lead | Optional | Slice decomposition and engineering rollups. |
| Product lead | Optional | Multi-stream spec decomposition and AC traceability. |
| QA lead | Optional | Multi-slice test planning and coverage matrices. |
| Design lead | Optional | UX sub-stream coordination. |
| Program manager | Optional | Cross-stream dependencies and status rollups. |
Compliance, privacy and medical (optional modules)
Advisory review artifacts — not licensed professional services.
| Role | Tier | What it covers |
|---|---|---|
| Privacy and data governance reviewer | Optional | PII, consent, retention, subprocessors, and cross-border processing. |
| Legal counsel reviewer | Optional | Terms, privacy policy, beta agreements, and counsel packet prep. |
| Medical safety reviewer | Optional | Clinical AI, triage, and regulated health workflows. |
Domain and operations modules (optional)
Integrations, automation, marketing, reliability, and service design.
| Role | Tier | What it covers |
|---|---|---|
| Integration and partner systems engineer | Optional | Vendor APIs, adapters, and external trust boundaries. |
| Senior automation engineer | Optional | Jobs, queues, webhooks, and CI automation. |
| Marketing and growth reviewer | Optional | Positioning, campaigns, and experiments. |
| Site reliability and incident engineer | Optional | SLOs, incidents, disaster recovery, and runbooks. |
| Service operations designer | Optional | SOPs, handoffs, and manual fallback paths. |
Crypto and Web3 (optional template pack)
Enable when building on-chain or cross-chain products.
| Role | Tier | What it covers |
|---|---|---|
| Smart contract and bridge security reviewer | Optional | Red-team review for lock/mint flows, adapter misconfiguration, and cross-chain supply risks. |
| Bridge and cross-chain integration engineer | Optional | Vendor adapters, token mapping, and POC acceptance for bridge surfaces. |
| Tokenomics and protocol economics reviewer | Optional | Supply caps, fee rules, curve parameters, and economic copy consistency. |
Platform operations (optional three-tier module)
Infrastructure decomposition under an engineering lead.
| Role | Tier | What it covers |
|---|---|---|
| Platform operations specialist | Optional | Infra slice routing and rollup. |
| Terraform sub-specialist | Optional | Infrastructure-as-code slices. |
| AWS sub-specialist | Optional | Cloud infrastructure slices. |
| Go sub-specialist | Optional | Go service slices. |
Shared platform engineering (optional)
Multi-tenant control plane and isolation — operator-grade deployments.
| Role | Tier | What it covers |
|---|---|---|
| Platform orchestrator | Optional | Cross-repo platform packets and venture coordination. |
| Control plane engineer | Optional | APIs, policy, async workers, and GitOps-oriented services. |
| Infrastructure platform engineer | Optional | Shared modules, clusters, secrets, and bootstrap patterns. |
| Tenant isolation specialist | Optional | Threat modeling, policy tests, and cross-tenant boundaries. |
| Platform design review | Optional | Cross-role review for multi-service platform changes. |
Prompt engineering (optional module)
Documented phase prompts and routing for complex packets.
| Role | Tier | What it covers |
|---|---|---|
| Prompt engineer lead | Optional | Packet prompt suite and routing ownership. |
| Prompt engineer | Optional | Phase delegation prompts per slice. |
Game and mobile (optional template packs)
Copy into product repos when shipping games or native apps.
| Role | Tier | What it covers |
|---|---|---|
| Unity engineer | Optional | Gameplay and engine implementation for Unity projects. |
| Unreal engineer | Optional | C++, Blueprints, and replication for Unreal projects. |
| Gameplay systems engineer | Optional | Loops, combat, progression, and save/load. |
| Multiplayer engineer | Optional | Networking, prediction, and dedicated servers. |
| Rendering engineer | Optional | Shaders, lighting, and frame budgets. |
| Technical artist | Optional | Asset pipeline, materials, and VFX. |
| Game platform engineer | Optional | Store packaging, CI, and crash analytics. |
| iOS engineer | Optional | Native iOS implementation and App Store path. |
| Android engineer | Optional | Native Android implementation and Play Console path. |
| Mobile platform engineer | Optional | Mobile CI, Fastlane, and symbol upload. |
| Mobile QA engineer | Optional | Device matrix and store testing flows. |
| Mobile release manager | Optional | Store checklists and phased rollout. |
| Mobile research analyst | Optional | Store policies and feasibility spikes. |
Workflows
| Workflow | Summary |
|---|---|
| Feature development | Intake, product spec, architecture, gated implementation slices, independent QA, triggered security and privacy reviews, release readiness, human merge and deploy. |
| Bug fix | Triage packet, minimal repro, fix slice, regression tests, QA isolation, release path matched to risk tier. |
| Security review | Threat-focused review for auth, data, uploads, webhooks, payments, and AI tool boundaries. |
| Compliance and regulated AI | Privacy, legal prep, and medical-safety modules when enabled — specialist artifacts and human gates before promotion or launch copy. |
| Crypto and Web3 change | Smart-contract and bridge security review, tokenomics check, and human gate before mainnet or parameter changes. |
| Release readiness | Merge brief, CI evidence, rollback notes, and explicit human go/no-go. |
| High-risk change | Tier 3 surfaces require specialist artifacts and human approval gates before build. |
| Incident response | Detection, mitigation, comms hooks, and post-incident packet updates. |
| GitHub PR merge discipline | Branch and pull request only, integrate latest main, evidence attached. |