Without a route record
Review can become another chat answer with no packet, independence status, checksum binding, or durable result.Operational route
Review before ship
Make plausible agent output answer to the approved spec, the changed artifacts, and the selected review posture.
Page evidence
- Packetscope + checksum
- Challengeindependent review
- Verdictfindings + posture
- Reworkbounded fix round
- Verifycurrent artifact
Route comparison
Same job. A visible operating record.
With Guild Stack
Guild Stack writes review packets and results under the run record, with cross-host review as the strong form and weaker modes recorded.Route stops
Request to verified result.
- 01
Packet issued
The reviewed artifact, scope, and evidence are packaged for the review round.
- 02
Independence recorded
Cross-host review is strong; same-host or skipped review is recorded as weaker.
- 03
Findings loop
Blocking findings route back through bounded rework instead of disappearing into chat.
- 04
Gate pass rule
Artifact binding, result status, and blockers determine pass or rework.
Receipts
What the route leaves behind.
- 01 Path
review/<gate>/packet-<round>.mdRoleReview request bound to scope and artifact evidence.
- 02 Path
review/<gate>/result-<round>.jsonRoleStructured verdict and blocker state.
- 03 Path
review/<gate>/trail.mdRoleHuman-readable review trail.
- 04 Path
verify.mdRoleDone-gate evidence after review resolves.
Next