01 / MEMORY
Durable Repo State
Initiatives, tasks, sprint order, artifacts, bugs, learnings, and job records survive restarts and new AI turns.
Explore the state model →V0.1.0-BETA.1 · FUNCTIONAL PRERELEASE
Ship across agents.Never lose the work.
Team OS coordinates Assistant, PM, UI, Code, FE, and QA across many AI turns—using one repository-native source of truth.
ASSISTANT · FOUNDATIONPM · SCOPEUI · DESIGN INTENTCODE · IMPLEMENTATIONFE · FINISH QUALITYQA · SHIP CONFIDENCE
THE REAL SCALING PROBLEM
AI is great at run 1.
The real problem is run 5.
CONTEXT THAT SURVIVES
Chats forget. Sessions end. Providers change. Team OS keeps decisions, tasks, evidence, bugs, retries, and release judgment connected inside the repository.
CORE RUNTIME
The operating layer
between prompts and shipping.
ONE CONTROL PLANE
Judgment stays with specialized role contexts. Stable IDs, state movement, validation, logs, reports, and recovery stay deterministic.
02 / EXECUTION
Managed Role Execution
Launch role work or large cross-team features as durable jobs, stream progress, preserve logs, answer questions, retry failures, and reattach later.
Explore long-running work →03 / TRUST
Evidence-Gated Delivery
Completion requires linked role evidence. Validation catches broken references, stale design intent, sprint drift, and missing QA.
Explore validation →ONE PRIMARY WORKFLOW · CEO OPTIONAL
Every role starts
where the last one ended.
Assistant → PM → UI → Code → FE → QA turns a request into managed work, evidence, validation, and the next handoff. CEO can evaluate an idea first, but never gates delivery.
Run /start in any repository. Choose New project or Existing project; Assistant records the foundation with zero executor tasks, then PM resolves readiness.
TYPICAL DELIVERY TRACE
Baseline ready
.TEAM-OSSTATE
01ASSISTANT
02PM
03UI
04CODE
05FE
06QA
.TEAM-OSSTATE
JOB HISTORY · CODEAPP-001:CODE-01
Reading durable state…STATE
RUN
BLOCKED
HISTORY
/LOGS
ERROR
PARTIAL
CAUSE
/ANSWER
/RETRY
DONE
VALID
LINKED
FOLLOW-UP
STATE
/NEXT
Old job record preservedSTATE HISTORY · 16 EVENTS
SIX PRIMARY ROLE CONTRACTS
Not personas.
Evidence-producing specialists.
/assistant new CONTRACT ACTIVE01of 06
FOUNDATION · APPLICATION CONTEXT & INTAKE
ASSISTANT
Captures concise repository context, groups related work under a stable feature family, and creates a lean initiative without inventing executor tasks.
JUDGMENT CONTRACTApplication context, feature identity, guarded initiative intake
DURABLE OUTPUTContext · feature family · lean initiative · active focus
NEXT HANDOFFPM
Open role contract ↗REPLACE CHAT MEMORY
Stop rebuilding context
every session.
LOAD ONLY WHAT MATTERS
Team OS stores the current operating state and only loads detailed historical artifacts when the work actually needs them.
DEVELOPER
CHAT HISTORY
TODO NOTES
STALE PROMPTS
SCREENSHOTS
TEST NOTES
MEMORY
SIX PRIMARY ROLE CONTEXTS · ONE DURABLE NUCLEUS
RUN IT FROM THE REPOSITORY
From setup to durable
handoff in three commands.
TERMINAL-FIRST RUNTIME
Use the interactive runtime for normal work. Team OS handles state, recommends the next role, and keeps recovery tools close.
01
Start Building
Run /start in any repository, then choose New project or Existing project inside the guided setup.
02
Orchestrate Agents
/next task runs one recommended handoff. /sprint task runs the full sprint sequentially as one managed job.
03
Recover, Validate & Retry
Inspect logs, attach to active jobs, answer blockers, retry failures, and validate the state before the next handoff.
OPERATING VIEW
Know what is next.
Know what is missing.
ACTIVE SPRINTSPRINT-APP-001-07
NEXT ROLECODE
ROLE / TASKSTATEEVIDENCE
PMAPP-001:PM-07COMPLETEscope linked
UIAPP-001:UI-07COMPLETErefs fresh
CODEAPP-001:CODE-07READYrecommended
FEAPP-001:FE-07BLOCKEDawaits Code
QAAPP-001:QA-07BLOCKEDawaits FE
RECOMMENDED TASKAPP-001:CODE-07
OWNING ROLECODE
CompleteReadyPartial / blocked
RUNTIME GUARANTEES
The boring controls
that make agents useful.
DETERMINISTIC BY DEFAULT
Team OS does not rely on a perfect prompt or a model remembering yesterday. The workflow is enforced through repository state, validation gates & signed contract obligations between the runtime and roles.
Local-First State
The control plane lives beside the application source in the repository.
Stable IDs
Initiatives, tasks, bugs, jobs, and artifacts keep durable cross-file references.
Recovery Tools
Attach, inspect logs, retry, answer, or cancel managed jobs without losing the record.
Stale-Reference Gates
FE and QA cannot silently close work against outdated UI intent.
Fresh QA Closeout
Initiatives require current ship evidence after the latest delivery slice.
Archive and Reopen
Completed sprint artifacts leave active context but remain available for history and regression work.
FUNCTIONAL BETA · REVIEW LIMITATIONS FIRST