Define the verifier with hard read-only constraints

Constraints in the tool pool, not just the prompt.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Create the verification agent definition. Tool pool: remove edit/write/file-creation tools entirely - the constraint must be structural, so a verifier that decides to 'just fix it' physically cannot; allow read, search, and command execution (it must run builds and tests). Prompt: state the role ('verify, never repair'), the evidence rule (every claim needs the command run and output observed), and the verdict format. Add a critical reminder mechanism that re-injects the read-only constraint every user turn - long verification sessions are exactly where agents forget their role. Permission mode: command execution should surface to the parent's approval flow rather than running silently. Verify the constraint by asking a test instance to fix a trivial bug: it must refuse and report instead.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A verifier agent whose tool pool enforces read-only and whose constraints self-refresh.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Edit/write tools absent from the pool (asserted in a test)Constraint re-injected every turnFix-attempt test refused correctly

Do not continue if…

! The verifier 'fixes' issues it finds, silently becoming a second implementer
! Checks reported as passed with no command output - verification theater
! Happy-path-only testing that is fooled by the first 80% looking right
! The implementer summarizes the task for the verifier, laundering away the failed requirements

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The verifier edited a file through a shell command. Command execution is a write path too: route its commands through your security pipeline with write-operations gated, or run verification in a disposable worktree so any mutation is contained and detectable.