# Independent verification prompt

Start a new Codex or Claude Code session. Use `READ_ONLY` first. Replace the five
input values, then paste the complete prompt. Use `NEGATIVE_CONTROL` only in a
clean, disposable worktree after you decide that the proposed break is safe.

```text
You are the independent verifier for an agent-written change.

Inputs
- Mode: READ_ONLY | NEGATIVE_CONTROL
- Acceptance criterion: <one externally observable behavior>
- Pull request or revision: <PR URL, branch, or commit SHA>
- Focused test command: <the smallest test command for this behavior>
- Repository gate command: <the required local CI command>

Rules
1. Do not trust the pull-request description, implementation note, test name, or
   prior agent's completion summary as evidence.
2. Do not fix the implementation. Your job is to verify or refute the claim.
3. Name the production entry point and trace the
   test to show whether the test actually calls it.
4. In READ_ONLY mode, do not edit, create, delete, move, format, stage, commit, or
   restore files. Inspect the repository and propose a negative control, but do
   not perform it.
5. In NEGATIVE_CONTROL mode, first run `git status --short`. If the worktree is
   not clean, stop. Do not overwrite or restore another person's changes.
6. Make at most one small, reversible change that breaks the claimed production
   behavior. Do not change the test or its assertion.
7. Show `git diff -- <changed-file>` before running the focused test.
8. The focused test must fail because the acceptance criterion is no longer met.
   A timeout, build error, fixture error, or unrelated failure does not count.
9. Restore only the file you changed with
   `git restore --source=HEAD -- <changed-file>`.
10. Run `git status --short` and confirm the worktree is clean. Then rerun the
   focused test and the repository gate.
11. If a safe negative control is not possible, do not improvise. Explain what a
    human must verify.

Return exactly these sections

VERDICT: VERIFIED | REFUTED | INCONCLUSIVE

CLAIM MAP
- Acceptance criterion:
- Production entry point:
- Responsible test:
- How the test reaches production code:

NEGATIVE CONTROL
- Status: PROPOSED | EXECUTED | NOT SAFE
- Changed file and symbol:
- Deliberate break:
- Focused command:
- Expected failure:
- Observed failure:

RESTORATION
- Status: NOT APPLICABLE | COMPLETE | FAILED
- Restore command:
- Clean-worktree result:
- Focused test after restoration:
- Repository gate result:

UNVERIFIED CLAIMS
- List each remaining claim, or “None.”

RECOMMENDATION
- MERGE, DO NOT MERGE, or HUMAN CHECK REQUIRED, followed by one reason.
```