Operational route

Review before ship

Make plausible agent output answer to the approved spec, the changed artifacts, and the selected review posture.

Page evidence

Operational mapChallenge the bound artifact, then route the verdict.
  1. Packetscope + checksum
  2. Challengeindependent review
  3. Verdictfindings + posture
  4. Reworkbounded fix round
  5. Verifycurrent artifact
/guild:guild "Review this implementation against the approved spec." --review=cross

Route comparison

Same job. A visible operating record.

Without a route record

Review can become another chat answer with no packet, independence status, checksum binding, or durable result.

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.

  1. 01

    Packet issued

    The reviewed artifact, scope, and evidence are packaged for the review round.

  2. 02

    Independence recorded

    Cross-host review is strong; same-host or skipped review is recorded as weaker.

  3. 03

    Findings loop

    Blocking findings route back through bounded rework instead of disappearing into chat.

  4. 04

    Gate pass rule

    Artifact binding, result status, and blockers determine pass or rework.

Receipts

What the route leaves behind.

  1. 01
    Path review/<gate>/packet-<round>.md
    Role

    Review request bound to scope and artifact evidence.

  2. 02
    Path review/<gate>/result-<round>.json
    Role

    Structured verdict and blocker state.

  3. 03
    Path review/<gate>/trail.md
    Role

    Human-readable review trail.

  4. 04
    Path verify.md
    Role

    Done-gate evidence after review resolves.

Next

Follow this route through an illustrative run.

The demo traces one bounded task through approvals, specialist lanes, review, verification, and the final run record.