i9wa4 Subagent Review
1. Ledger
- Before review, guardian freezes target, criteria, scope, and the design/public boundary. Broadening is recorded, never inferred.
- Guardian owns a never-reused ledger (
F-001); use the contract for required fields and reports. - Guardian alone decides materiality and convergence; packets supply observations, evidence, and risk signals. Nits never gate rework. Invalid packets, missing evidence, authority gaps, cap exhaustion, and criterion changes are guardian-recorded states.
2. Review to Convergence
- Run cheapest verification. Guardian defines the required perspective set; critic is guardian-specified and never self-selects. Waves are parallel.
- Deduplicate. Guardian MUST request critic for substantive review; critic returns its set plus self-review; guardian aggregates both sets. Reviewers never edit, commit, push, approve, or decide materiality. See the packet schema and blind-projection contract in contract.
- Each round reconciles every prior ID: recurrence, regression, new discovery, closure, supersession, accepted risk, or unchanged; record changed criteria.
- Review the full change, then deduplicate material findings and freeze IDs, closure conditions, and reproducible verification in one executor batch. After rework, verify and review only that set unless scope/criteria changed.
- Repeat batched fix → verification → diff-review until closure, then final
confirmation. Cap: initial plus two failed reworks. At cap/unavailable
evidence,
BLOCKEDincludes IDs, gap, authority needed, and next owner. Quarantine invalid packets before a round; they consume no rework slot.
3. Round Report
Each round follows the contract: frozen scope/criteria/targets, ledger, evidence, batch, verdict, and next action.