1.3 Veto design
Completion requirements
For a workflow with more than one reviewer — human or AI — specify who may veto what.
Do this before anyone fails. For each role state: what it may block, what it may only flag, and what happens when it is wrong.
Decide what a role may veto before you find out how it fails.
A role with a veto and a role with none can make errors of identical size and cost you wildly different amounts. The difference is not competence — it is authority granted in advance.
400–700 words · about 45–60 minutes.
How you will be graded — aim for Proficient.
| 1 · Emerging | Roles listed with no authority attached. |
| 2 · Developing | Veto rights assigned, but nothing stated about the cost of a reviewer being wrong. |
| 3 · Proficient — target | Every role in the workflow covered. For each: what it may block, what it may only flag, and what happens when it is wrong. Written as design, before any failure — not as a description of what happened last time. |
| 4 · Exemplary | Also identifies a role currently holding authority disproportionate to its error rate, either way. |