4 · Build
The selected engineering lead implements the card and reviews the result. CPO verifies acceptance independently before the card reaches human review.
The CPO skills
Section titled “The CPO skills”- cpo-dispatch assigns ready cards to workspaces under project ownership and capacity limits, then confirms startup.
- cpo-build invokes the selected engineering lead, accepts its reviewed return, and completes the CPO delivery steps.
- cpo-verify exercises the card’s acceptance criteria in fresh context and records the evidence.
With pstack selected, Build invokes /poteto-mode <task> with the card’s
scope and return boundary. The mode chooses its playbook, workers, and
engineering review process. CPO requires reviewed implementation, passing
configured validation, and independent acceptance across the full card.
The checkpoint
Section titled “The checkpoint”Human review, with evidence and a PR. Each acceptance criterion has an observed result and supporting proof. Failed or unavailable required proof keeps the card out of human review. Only the owner authorizes the merge gate.
Deliverables
Section titled “Deliverables”The reviewed change on the card’s branch, acceptance evidence, decision records, and a PR prepared under the CPO contract.
Who participates
Section titled “Who participates”Eng builds; Ops runs the machinery; the CPO holds the evidence standard.