| name | review-harness |
| description | Use when reviewing implementation work that ran through a /tmp Pi task harness. Checks contract drift, unsafe shortcuts, validation evidence, and status honesty. |
| compatibility | Requires my-pi or Pi with the pi-harness extension tools enabled. |
Review Harness
Review completed or failed work against the immutable outer policy and
the complete versioned scaffold/amendment history.
Workflow
- Resolve the harness directory and read
harness.json, TASK.md,
status.json, OUTCOME.md or outcome.json, and
logs/events.jsonl if present.
- Run or inspect
<harness_dir>/review.sh.
- Inspect git diff and changed files.
- Compare changes against
policy.forbidden_paths, the active
scaffold.allowed_paths, test policy, escalation rules, and all
recorded amendments.
- Verify validation evidence from
status.json, logs, and command
output.
- Decide: pass, needs executor fix, or escalate to planner/user.
Review Checks
- Did work stay inside the outer policy and active scaffold?
- Were scaffold changes authorized, versioned, and honestly recorded?
- Did any amendment attempt to weaken the outer trust boundary?
- Were tests changed when
allow_test_changes is false?
- Were validators weakened, deleted, skipped, or bypassed?
- Were outputs faked or hardcoded to satisfy checks?
- Are status and evidence entries honest and complete?
- Does the outcome artifact include changed files, validation
evidence, team status, and remaining risks?
- Did the executor make unapproved architecture decisions?
Output Shape
## Verdict
Pass | Needs executor fix | Escalate
## Findings
- P0/P1/P2: <issue> — `<path>` — <required action>
## Validation Evidence
- `<command>` — pass/fail/not run — <evidence>
## Required Next Step
- <one action>
