Without a route record
Cost and review strength drift across prompts, while operators cannot tell which posture produced the result.Operational route
Cost and review control
Choose how much planning, model capacity, context, and independent challenge the task deserves, then record the decision.
Page evidence
- cheaproutine, low-risk work
- midmulti-file reasoning
- powerfulhigh ambiguity or risk
- lane scoretask signals
- host model idconfigured mapping
- resolved settingsfrozen evidence
Tier keys stay portable. Exact model ids belong to host configuration.
Route comparison
Same job. A visible operating record.
With Guild Stack
Guild Stack resolves a portable tier and review mode from explicit settings and flags, then freezes them with the run.Route stops
Request to verified result.
- 01
Choose rigor
Set the planning and verification posture for the risk of the task.
- 02
Resolve the tier
Use deterministic task signals and host-configured model mappings.
- 03
Set review strength
Choose local, cross-host, or off with the resulting independence recorded.
- 04
Freeze and inspect
Keep effective settings and review evidence beside the run.
Receipts
What the route leaves behind.
- 01 Path
resolved-settings.jsonRolePer-key effective configuration and source map.
- 02 Path
run.yamlRoleSelected rigor, review posture, and lifecycle state.
- 03 Path
review/<gate>/RolePacket, result, trail, and independence label.
- 04 Path
handoffs/*.mdRoleLane tier and escalation evidence.
Next
