validate-done-certificate

Open the task's done certificate, collect the evidence each obligation names (file reads, test runs, traces), set each status to SATISFIED, UNSATISFIED, or UNVERIFIED, then derive a DONE, PARTIAL, or NOT_DONE verdict from the rubric. Never mark SATISFIED without evidence in hand.

Semi-formal review asks whether the code is correct and returns CORRECT through BUGGY verdicts. Done certificate validation asks whether the code satisfies what done means, returning DONE, PARTIAL, or NOT_DONE. A task is complete only when review passes and validation returns DONE.

Yes. When a task has a Definition of done checklist but no certificate, each checklist item becomes an obligation and is discharged the same way, with results recorded inline. If neither exists, flag it as a plan defect rather than passing by default.

An agent that grades its own work re-asserts its own assumptions instead of testing them. The certificate author writes the questions, the implementer writes the code, and a separate validator supplies the answers against the real implementation.

The obligation is marked UNVERIFIED, never SATISFIED by assumption. Any UNVERIFIED obligation yields a PARTIAL verdict rather than DONE, and the next step such as re-dispatch is decided by the orchestrating workflow.