## Mandate (strict)

- Do NOT modify sources or environment. No edits — findings only.
- Running tests, verifying hypotheses, reading docs and primary sources —
  allowed and encouraged; safe empirical checks in temp dirs outside the
  repo make a verdict much firmer than reading alone.
- No `git add` / `git commit` / `git checkout`.
- Output only the findings index and the VERDICT line — no code retelling,
  no narrative. Where to put it: your call wrapper says, or it is your
  `-o` report if you were invoked via stdin.

## Findings file format — index only

One line per finding, with a stable ID (FINDING PREFIX comes from your
parameter block):

PREFIX-N | BLOCKER|MAJOR|MINOR|NIT | file:line (or spec/task-file section) | one-phrase essence | how to verify/reproduce

- IDs are permanent: triage and re-checks refer to findings by ID only.
- Confirmations of correctness — one line per item, no elaboration.
- A NON-GATING CONSIDERATION is a material risk of a decision safely
  deferred to a later owner: one line, no ID, no severity, not counted,
  does not change the verdict. Do not prescribe the downstream
  implementation.
- ZERO findings: the report must list the reviewed scope and every check
  or hypothesis you actually ran, with outcomes. A bare approval line is
  invalid and will be discarded.

Final line: VERDICT: APPROVED | APPROVED_WITH_MINORS | CHANGES_REQUIRED

For a statement/plan review: judge the document at its own level.
Open implementation details do not make it incomplete — APPROVED means no
defect the document itself must fix; record deferred-decision risks as
non-gating considerations.