Task, not trace
Verification is scoped to the unit of work. A run either satisfies the task spec or it does not — no judgement calls about style, paths, or tokens spent.

Task, not trace
Verification is scoped to the unit of work. A run either satisfies the task spec or it does not — no judgement calls about style, paths, or tokens spent.
Deterministic checks first
Every task ships with executable checks. Files, outputs, assertions, side effects. If a check can be a test, it is a test, not a rubric.
Verdicts you can audit
A verdict is pass, fail, or unexplained, always attached to the
evidence that produced it. Unexplained is a first-class outcome, never a
silent pass.
Fits your harness
Run it as a library, a CLI step in CI, or an HTTP endpoint that any agent harness can call after a run finishes.
Verify Task answers one question, cheaply and repeatably:
Did this run complete the task it was given?
It is deliberately separate from audit (what happened, and can we prove it) and from scoring (how good was it, on a scale). Verification produces a binary verdict plus the evidence behind it.
Early skeleton. The site structure, navigation, and reference layout are in place; the API surface below is a proposal, not a shipped contract.