Docs · Work
Work types
Zero organizes engineering around Work items. A Work item can be a bug investigation, a feature, a refactor, an epic, or a greenfield project. The type determines how the Work item is structured and what counts as proof.
bug
A defect investigation. Something in the system behaves incorrectly — wrong output, crash, regression, or unexpected side effect. Sessions trace root cause, propose a fix, and execute it.
What counts as proof: Test results showing the defect no longer occurs. Load or regression tests preferred where applicable.
feature
A planned addition to the codebase. The Work item defines what the feature should do and acceptance criteria. Sessions implement the feature and verify it against those criteria.
What counts as proof: Tests passing against acceptance criteria, or a passing acceptance test suite. Manual verification is supported but requires an operator note as evidence.
refactor
A structural improvement without behavior change. Refactors improve readability, performance, or testability without altering external-facing behavior.
What counts as proof: Full test suite green on the refactored code. Diff review showing no behavior change is also accepted as evidence.
investigation
An exploratory session with no predetermined outcome. Used when the source of a problem is unknown or when evaluating whether a problem exists. Closes with an outcome classification.
What counts as proof: Evidence supporting the classification — reproduction trace for ConfirmedCodeBug, or session log demonstrating IntendedBehavior.
epic
A multi-session, multi-case Work item. An epic contains child Work items. Sessions can run on child items or on the epic directly. An epic resolves when all child Work items have verified proof. (In development — core structure available; GitHub milestone import planned.)
What counts as proof: All child Work items resolved with verified proof, plus an epic-level acceptance evidence record.
greenfield
A new project or module being built from scratch. Sessions scaffold the project, implement core functionality, and build an initial test suite.
What counts as proof: Specification document attached, plus initial test suite passing. CI integration record accepted as supplemental evidence.