verify-generation

• SKILL.mdcore · 8,787 bytes

# Verify a generation

## Goal

No generative output reaches the owner without having survived the full verification suite, so the owner's past corrections are enforced before they can be repeated. The suite has two halves, deterministic tests that catch what code can catch and verifier agents that judge what code cannot, and a round is both halves against the current output. Rounds repeat because a fix in one place breaks another, and because a verifier in fresh context may see on the second read what it missed on the first. The step stops when a round passes, with at least three rounds so a pass is confirmed, and never after round five. Findings are fixed in the artifact only, never by changing a test, a verifier or a memory entry, since those are the owner's corrections and the artifact is the thing under review. Every round is recorded in progress with its evidence, so the report can show the owner what was checked and the next context can resume if this one is lost. Findings that survive round five are reported as unfinished work, never hidden, because an owner who sees an unresolved finding can decide and an owner who does not will meet it as a correction.

## Objective

Identify the artifacts the step produced or changed and select every verifier whose trigger matches them, plus the memory-conformance verifier that runs on everything. Run a round: the full test suite, then each selected verifier in fresh context with only the inputs its file lists, collecting every FAIL with its location. Fix every finding in the artifact, citing the rule or fact id each fix applies. Record the round in the progress table with the test result, the verifiers run, the findings and the fixes. Repeat until a round passes on or after round three, or until round five has run. Report the rows and the verdict, and list any findings that remain as open items, with the step marked not done.

## Tasks

1. Identify the artifacts the step produced or changed, by path. A step that touched several files verifies all of them together, because a rule about consistency across files cannot be checked one file at a time.
2. Load `memory/verification.md` and `verifiers/INDEX.md`. Select every active verifier whose trigger matches an artifact path or kind, plus `verifiers/memory-conformance.md`, which runs on everything. Record the selection in the progress table so the report shows what was checked.