Verification

PitWay runs verification in two tiers.

Task-level

pitway task-verify T001

Runs the task's own approved command and records formal evidence -- see Evidence for the three check types (command, manual, review) and how approval works.

Milestone-level

pitway verify M001

Runs every approved command-type check for the whole milestone. This is the mandatory full-suite gate: Completion (milestone-complete) refuses to close a milestone until every task is done and every check is passing.

verification_approved_hash

Verification commands are hash-approved once, at milestone-confirm time. If the approved commands drift from what's actually in the contract, verify refuses on a hash mismatch rather than silently running something that was never approved -- re-confirming the milestone (milestone-confirm --amend) re-approves the plan.

Repairing a stuck verification

If verification evidence itself needs correcting after the fact, verification-repair provides a bounded, approve-before-edit correction path -- it's not a way to bypass the checks, only to fix how their evidence was recorded.