Guild Stack

Docs section

Control

Understand and override the model tier chosen for each specialist lane.

Start with Configuration referenceAll docs

Page evidence

Operational mapScore the lane. Resolve the host model. Freeze the choice.
Stable tier keys
  1. cheaproutine, low-risk work
  2. midmulti-file reasoning
  3. powerfulhigh ambiguity or risk
Per-run resolution
  1. lane scoretask signals
  2. host model idconfigured mapping
  3. resolved settingsfrozen evidence

Tier keys stay portable. Exact model ids belong to host configuration.

Settings resolve first; task signals and explicit overrides then produce a recorded tier decision.
Diagram notes and sources
  • docs/v2/dispatch-execution.md
  • docs/v2/config-surfaces.md

Common tasks

Change one control with proof.

Resolve the posture

See which setting source wins and inspect the frozen effective configuration.

Inspect the decision

See which task signals move a lane between cheap, capable, and escalation tiers.

Apply an override

Set a portable tier key without coupling the project to one vendor model name.

Route guides

Resolve posture before overriding it.

Control

  • Configuration reference

    Guild Stack settings: one settings.json file, seven-source inheritance, closed-key validation, model tiers, dispatch mode, security, and MCP pins.

  • Cost-aware model tiering

    Guild Stack routes each specialist lane to the cheapest model tier that fits the work, with deterministic scoring, overrides, and advisor escalation.

Every override should leave a reason.

Continue into Learn to turn current repository evidence into reusable project knowledge.
Learn docsDocs gateway