cpo-verify

Verifies a card in fresh context that did not build the change. It exercises the promised behavior through the project’s verification skill, documented harness, or appropriate direct runtime checks and attaches evidence to the card.

When to use it

• a card’s build is done and needs proof before human review
• you want to see a change working, not just passing tests

What it needs

• a configured repo with its verification-tool source
• a card with acceptance criteria to verify against
• access to the intended build, environment, and test persona

What you get

• pass, fail, or not-checkable for every acceptance criterion
• commands or interactions, observed results, and evidence tied to the revision
• prototype differences and missing access or required proof recorded explicitly

Required proof must be present. Optional media capture can fail without invalidating otherwise sufficient evidence, but the report records that gap.

Where it sits

Build runs this acceptance pass across the full card after engineering review and configured validation. Builder checks provide earlier feedback using the same tools. Every criterion must pass before cpo-pr can make the card ready for human review. Verification returns evidence; Build and PR own board transitions.

Say this

verify this
check it works
show me it working