Power users
Choose the posture. Keep the evidence.
Set lifecycle entry and rigor, inspect frozen settings, then read review strength and lane receipts before treating the run as trusted.
Page evidence
Run posture
Control surface
- Lifecycle entry
- next Read phase entry points Start from the phase boundary that matches the work.
- Rigor / tier
- gate Set rigor and model tier The resolved settings snapshot freezes these choices.
- Review boundary
- gate Inspect review posture Strong, weaker, and skipped paths remain explicit.
- Lane receipt
- recorded Open completed-lane receipts Read the durable handoff before trusting a result.
- Release posture
- recorded Check verification evidence Task completion is not release approval.
Control jobs
Set the context that changes the proof.
- choose entry
- approve phase gate
- run.yaml
- set depth
- resolve host model
- resolved-settings.json
- choose posture
- record independence
- review result
Review posture
The review loop is part of the setting you inspect.
A review packet, independent challenge, rework, and verification make the strength of a run visible instead of leaving it as an assumption.
- Packetscope + checksum
- Challengeindependent review
- Verdictfindings + posture
- Reworkbounded fix round
- Verifycurrent artifact
Proof surface
A control is only useful when its record is easy to inspect.
Settings, receipts, review packets, and provenance describe what the run was allowed to do and what evidence it produced.
.guild/runs/run-<id>/
The power-user evidence trail
-
resolved-settings.jsonfrozen host, tier, rigor, and review choices -
handoffs/*.mdguild.handoff_receipt.v1 files from completed lanes -
review/<gate>/review packets, rounds, and verdicts -
provenance.jsonclose-shape facts for reconstructing the run
Continue
