# Zero Operators

## Docs

- [The people behind it](https://docs.zerooperators.com/acknowledgements.md): No tool ships alone. The specialists, researchers and engineers who tested, broke things, pushed back when it counted, and made ZO sharper.
- [zo build](https://docs.zerooperators.com/cli/build.md): Launch the agent team against a plan. Smart mode detection (fresh / continue / re-decompose). The flagship command.
- [zo draft](https://docs.zerooperators.com/cli/draft.md): Launch the Plan Architect + scouts to draft plan.md against the schema. Confirms each section before writing.
- [zo init](https://docs.zerooperators.com/cli/init.md): Scaffold a new project: memory files, target file, plan skeleton, delivery repo. Conversational by default.
- [CLI overview](https://docs.zerooperators.com/cli/overview.md): Every zo command, organised by when you'd reach for it.
- [Low-token mode](https://docs.zerooperators.com/concepts/low-token-mode.md): Run ZO on a Pro plan or student account by trading some quality for substantial token savings. One flag, one preset, predictable cost.
- [Memory & continuity](https://docs.zerooperators.com/concepts/memory-and-continuity.md): Every session reads state at entry and writes it at exit. Memory is required infrastructure, not a nice-to-have.
- [Overview](https://docs.zerooperators.com/concepts/overview.md): The five concepts you need to understand to use Zero Operators effectively.
- [Phases & gates](https://docs.zerooperators.com/concepts/phases-and-gates.md): Six sequential phases of work, separated by gates. Automated gates run validation; blocking gates pause for human approval.
- [The oracle](https://docs.zerooperators.com/concepts/the-oracle.md): Every project must define a hard, verifiable success metric. Without a measurable criterion, autonomous agents become hallucinating cost centers.
- [The plan](https://docs.zerooperators.com/concepts/the-plan.md): A single Markdown file is the human's only lever of control. This is what makes ZO autonomous — and what keeps it grounded.
- [The team](https://docs.zerooperators.com/concepts/the-team.md): 21 specialised AI personas, each with a defined role, tier, and contract. The team coordinates peer-to-peer through Claude Code's native APIs.
- [Installation](https://docs.zerooperators.com/installation.md): Install Zero Operators and its prerequisites on macOS or Linux.
- [Introduction](https://docs.zerooperators.com/introduction.md): Zero Operators is an autonomous AI research and engineering team. You write a plan; agents build it; the oracle verifies the work.
- [Quickstart](https://docs.zerooperators.com/quickstart.md): Five minutes from zero to your first ZO run, training a real model end-to-end.
- [Cost benchmark](https://docs.zerooperators.com/reference/cost-benchmark.md): Methodology and measured results for ZO's --low-token cost-saving preset, benchmarked against the MNIST end-to-end reference run.
- [Low-token preset](https://docs.zerooperators.com/reference/low-token-preset.md): The compact reference card for what --low-token actually flips, with override flags and precedence rules.
- [Roadmap](https://docs.zerooperators.com/roadmap.md): What's next for Zero Operators — priorities, scope, and how to weigh in.

## OpenAPI Specs

- [openapi](https://docs.zerooperators.com/api-reference/openapi.json)