Two-Axis Completion Criterion (Checkable + Exhaustive)

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Audit a catalog revision rather than merely judging appearance. Teaching scope is IDs 1/2/3: one disposition each; active needs bilingual completeness, merged a valid target, removed a reason. Content obligations also need review beyond field presence.

Mechanism

Inventory all inputs and define checkable, sufficiently exhaustive exits. Track structural validation separately from semantic review; map each source problem/required remedy to retained content. Inspect disposition, coverage and claims independently. Preserve missing obligations even when another check passes.

Bad example

Finish when the blog looks better and example counts rise. Three IDs existing in a file is enough, despite missing language or review obligations.

Good example

Account for IDs 1/2/3 with one active/merged/removed decision each. Active has bilingual task, mechanism, contrast, check and limits; merges resolve; removals have reasons. Run reference/coverage checks and manually map distinct source obligations/remedies to retained text rather than matching counts/words. Separately report structure, semantic coverage and open items. Any unmet obligation remains incomplete.

Why the change matters

Predicates prevent vague completion while inventories prevent selecting only finished items. Semantic mapping establishes whether text addresses the actual obligation even when counts match.

Observable expectation

Removing ID 2’s reason or an active English body should fail coverage. Restoring fields while omitting necessary failure handling may pass structure but fail semantics.

Claim complete only with actual evidence for every scoped obligation and no unresolved items. Explicit exclusions need reasons, not disappearance from the source inventory.

Limits

Exhaustiveness is scoped, not global. Repeated citations may share a remedy, but shared vocabulary cannot collapse distinct obligations. Attempted repair is not confirmed repair, and acceptance differs from technical checks.