Team OS functional beta

Team OS coordinates long-running AI delivery work through durable repository state instead of relying on one chat. The primary workflow has six roles:

Assistant → PM → UI → Code → FE → QA

CEO is a seventh, optional idea evaluator. It is never required by /next, task planning, or sprint delivery.

This documentation targets the receipt-gated v0.1.0-beta.3 functional beta. The runtime, migration, security/privacy boundaries, provider-specific installations, deterministic workflows, release archives, and downloaded-client acceptance are gated. A matching immutable GitHub prerelease and receipt—not source copy—establish publication. Broader seven-role pilots, matched baselines, scenario coverage, provider calibration, and final independent scoring continue in Phases 12–19. The beta is not GA and does not claim Validated or Exemplar readiness.

Durable control plane

Team OS separates deterministic workflow operations from role judgment.

Runtime responsibilities	Role responsibilities
Stable IDs, state, task gating, jobs, logs, validation, reports, migration, archive indexes, and recovery	Intake judgment, planning, experience direction, implementation, finish quality, verification, and explicit evidence

Every managed project owns a .team-os/ directory:

project/
├── .team-os/
│   ├── assistant.md          # application context, feature families, focus
│   ├── app.md                # initiative lifecycle and PM planning
│   ├── todo.md               # delivery tasks and bugs
│   ├── sprint.md             # derived execution order
│   ├── sprint-artifacts/     # live and archived evidence
│   └── runtime/jobs/         # managed jobs and resumable checkpoints
└── application source

Use team-os commands for state changes. Do not freehand-edit generated state or role-local runtime mirrors.

Core loop

/start
/new
/next
/next task
/sprint task
/report

/new [request] and /new task [request] offer exactly two routes:

1. Create new task with Assistant
2. Evaluate idea with CEO

Assistant creates a lean, feature-labeled initiative with zero executor tasks. PM then resolves material delivery unknowns and atomically commits the task graph. UI, Code, FE, and QA execute the resulting sprint. Completed sprint evidence is archived and linked back to the feature family.

Current user scope, repository behavior, task state, and live sprint evidence always outrank archived history. Historical refs are lazy advisory context and must record any supersession.

Start here

1. Install the beta.
2. Follow the Quickstart.
3. Read the workflow and role boundaries.
4. Review Beta status and limitations.
5. Learn managed-job recovery.