Docs section

Run

Turn approved intent into scoped specialist lanes, typed handoffs, review findings, and closure evidence.

Six-phase routeroute_lifecycle

Approved project inputs become specialist lanes, typed handoffs, review findings, and closure evidence.

Common tasks

Follow the work, not the chat.

Decide whether the work belongs to one run, an initiative, or a federated workspace.

See how specialists receive focused context and return typed receipts.

Read how independent review and verification record their evidence.

Route guides

Choose the right operating scope
How Guild Stack scopes work across workspace, project, optional initiative, and run — and where durable state belongs at each level.
Specialist roster
Meet Guild Stack's roster: 15 domain specialist templates minted on demand, plus the advisor and developer machinery agents, for scoped lanes and typed handoffs.
Context assembly
Guild Stack gives each specialist a focused context bundle before dispatch: task lane, required skills, relevant wiki pages, and no project-wide dump.
Dispatch and execution
How Guild Stack turns an approved plan into specialist tasks, selects an execution mode, records handoffs, and recovers failed lanes.
Adversarial review
How Guild Stack challenges AI work before trusting it: independent review packets, bounded rounds, recorded verdicts, and no silent weak sign-offs.
Verify a host-adapter migration run
The migration-specific evidence packet, reviewer requirements, and followup policy used to verify work against the host-adapter migration spec.

Continue into Control to inspect the settings and tier decisions that shape each lane.