Documentation
Zero documentation
Task-oriented guides for working cases, running sessions, and verifying completed Work.
Start here
1
Create or import a Work item
Create manually, pull in a GitHub issue, or type a comment in the editor.
2
Run a planning session and approve the plan
Form a hypothesis. Zero proposes a plan — you approve before any code runs.
3
Attach proof and mark RESOLVED
Attach test logs or other evidence. RESOLVED is blocked until proof is verified.
All guides
Import GitHub issues
Bring an existing issue into Zero as a structured case.
Create a case
Open a case manually when you don't have a GitHub issue.
Run a planning session
Form a hypothesis and propose a plan before any code runs.
Proof and evidence
What counts as proof, and how to attach it.
Case states
The state machine: OPEN → INVESTIGATING → IMPLEMENTING → VERIFYING → RESOLVED.
Regression memory
Search resolved cases when a similar bug returns.
Export case data
Export cases as JSON or markdown. Team plan only.
Work types
Bugs, features, refactors, investigations, epics, greenfield — what each type means in Zero.
Epics
Multi-session Work items with child cases and rollup proof.
Session types
Planning, implementing, and verifying sessions — what each does and when to use it.
Attach code context
Tell Zero which files are relevant before running a session.
Understanding proof
Why the proof gate exists and how to think about evidence.
Comment-triggered Work
Type an actionable code comment — Zero offers to take over. Approve to start a session.