Without a route record
A failed or interrupted agent session leaves the operator guessing which decisions, lanes, and artifacts remain trustworthy.Operational route
Resume and recover
Inspect the current state, find the last valid transition, and continue without rebuilding the route from chat history.
Page evidence
- phase event
- LLM call
- terminator
- handoff
- review result
- verification
- scope
- review
- close record
Route comparison
Same job. A visible operating record.
With Guild Stack
Guild Stack reads durable run state, frozen settings, trace events, and receipts before choosing the next safe transition.Route stops
Request to verified result.
- 01
Read status
Inspect the active run, current phase, next gate, blockers, and recovery signal.
- 02
Locate the valid state
Compare run.yaml with frozen settings, trace events, and completed handoffs.
- 03
Classify the interruption
Separate a failed lane, stale review, missing approval, and host interruption.
- 04
Resume deliberately
Continue from the recorded boundary and preserve the prior evidence.
Receipts
What the route leaves behind.
- 01 Path
run.yamlRoleLifecycle state, phase, gates, and initiative attachment.
- 02 Path
resolved-settings.jsonRoleThe frozen posture that governed the run.
- 03 Path
logs/v1.4-events.jsonlRoleAppend-only transition and tool evidence.
- 04 Path
handoffs/*.mdRoleValidated outputs that do not need to be repeated.
Next
