Unmatched workflow

Leading words: falsifiable done-predicate, hypothesis loop, VERIFIED NOT VERIFIED INCONCLUSIVE.

When no playbook fits, the deliverable before any code is the workflow: phases that scale rigor to the task. Inconclusive is not a pass.

Copy these steps into the todo list verbatim. Skip with skip: <reason>.

1. Frame: falsifiable done-predicate, scope, rigor level (one-way doors get more). Present before a long run.
2. Design the workflow: atomic units, riskiest-unknown first, verification harness before features. The first unit that writes code is the harness, not a product edit. Deleting the old API is out of scope unless the Phase 1 predicate names it. Write the phase list down.
3. Run the loop: each unit is an experiment — hypothesis, smallest change, measure on the real artifact, keep or revert.
4. Verify the whole against the Phase 1 predicate on the real product.

Verdicts

Each unit: VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Do not hide a negative.

Pair delegated work with a parent read of the artifacts. If a worker games the gate, harden the contract. If the gate is wrong, fix the gate in its own change.

Reply contract

The playbook you designed, the rigor level and why, what is verified against the predicate, and what is still open.