Without a route record
A run can pass its task gate while release risk, dry-run posture, rollback, and operations approvals stay blurred.Operational route
Release readiness
Move from a verified run to product-level checks, release recommendation, runbook dry-run, rollback path, and explicit approvals.
Page evidence
- Discover checksproject signals
- Quality verdictready or block
- Dry runblast radius + rollback
- Approvalhard safety gate
- Release recordrunbook evidence
Route comparison
Same job. A visible operating record.
With Guild Stack
Quality computes release readiness from evidence, then Operations runs approved runbooks under explicit safety rails.Route stops
Request to verified result.
- 01
Select checks
Quality derives applicable check classes from project signals and surfaces the matrix.
- 02
Compute verdict
Release-ready or block is computed from evidence, not guessed by a model.
- 03
Dry run first
Operations prints steps, blast radius, and rollback path before execution.
- 04
Keep hard gates
Incident, rollback, destructive, network, spend, and production-sensitive actions still ask.
Receipts
What the route leaves behind.
- 01 Path
.guild/runs/<run-id>/quality/RoleRelease-readiness matrix and verdict.
- 02 Path
.guild/runs/<run-id>/ops/RoleRunbook record, dry-run posture, and safety evidence.
- 03 Path
review/G-quality/RoleQuality review packet and result.
- 04 Path
review/G-operations/RoleOperations review packet and result.
Next
