A — 0: We want “better AI” or lower tokens, without an accepted-output definition. B — 1: The workflow is chosen, but acceptance and important errors are not agreed. C — 2: Product and operations have signed a metric dictionary defining accepted, rejected, escalated and critical-failure outcomes.
Evidence to attach: task contract and three sanitised examples with expected outcomes. If weak: narrow to one workflow before testing methods. An invoice field and a fully accepted invoice are different units.