ACI-068: Independent Verification

Thesis

A node's report that its work is done is the trigger for verification. The builder's word does not close the work: a computed gate closes it, and the sign-off comes from a peer node or the human. The verifier fires on the claim, reads what was built rather than what was said about it, writes its own mutants against the committed bytes, tries to refute its own findings before posting them, and says what it did not check.

Story

Intent's whiteboard skill ships the method. A validation node fires on a claim, reads the as-built and never the narrative, classifies every finding, refutes its own high findings first, sends its findings to the owner, and audits its own coverage (Intent@9311a3fd5, 2026-09-26). It began as Lamplight's validation node describing itself in June: "fire on a done/closed/green claim; read the as-built (file:line), never the narrative; self-refute HIGH findings; classify expected-vs-real; state coverage" (Lamplight@4d0014e2a, 2026-06-15). Its verdicts ended with the paragraph that makes them usable, the list of what it had not done: "Did NOT: run a live dev re-publish to backfill existing worlds" (Lamplight@527e76695, 2026-06-24).