Review

PitWay workflow: BRS/Backlog into Milestone (Contract ⇄ Milestone Review) through the Human Approval gate to the Task Graph, TDD → Task Verification → Task Commit repeating with a Backlog exit, then Final Full Test (failure loops through milestone revision), Milestone Complete, and an opt-in Quick Change lane for small bounded fixes when no milestone is active (TDD → Verify → Human Approval → Commit), ending at Milestone Merge

The diagram above is PitWay's full canonical workflow, from requirement through milestone merge -- this Workflow section covers the stages after a contract is confirmed: Review, Auto Run, Verification, Completion, and Merge.

pitway milestone-review drives a role-based milestone review workflow with four stages: start, brief, record, report, decide.

What PitWay does and doesn't do here

PitWay's Engineering Boundaries are explicit about this one: reviewers produce findings only. PitWay does not run reviews itself, and it does not verify reviewer independence -- the review process is structured and recorded, but the judgment is a human's (or a driver acting on a human's behalf).

Where review fits

Review happens alongside a milestone's contract, before and during confirmation (Contract ⇄ Milestone Review in the workflow lifecycle), and can recur if a milestone's verification later fails and needs revision (review → in_progress). It's distinct from Verification, which checks concrete acceptance criteria against approved commands -- review is where a human (or driver) judges quality, scope, and risk more broadly, and its findings are recorded as evidence, not silently absorbed into the milestone's history.