Docs section

Start

Install Guild Stack, run one bounded task, and learn where its evidence lands.

First run · route 01

map / active

One bounded task, five inspectable stops

RequestName the task/guild:guild “one bounded change”
GateApprove scopeSpec, team, and lane plan stay visible.
DispatchRun the laneFocused context and explicit authority.
ReviewChallenge + verifyFindings must resolve before the route closes.
TerminusOpen the receiptThe final message is not the source of truth..guild/runs/<run-id>/

The route pauses at load-bearing decisions and terminates in files your team can reopen.

Common tasks

Install on a verified host, start one bounded job, and inspect the run directory.

Follow the lifecycle from scope through verification and reflection.

Find the shortest command or setting for the behavior you need.

Route guides

Get started with Guild Stack
Install Guild Stack on a receipt-verified host or preview one of 16 named targets, then run one bounded task with local .guild/ evidence.
How Guild Stack works
Follow one task through Guild Stack's six-phase lifecycle, three entry lenses, approval gates, specialist lanes, review, and reflection.
Command reference
The flat /guild:<verb> command surface: run the lifecycle, jump phases, inspect status, query memory, tune settings, and keep approval gates visible.
Installation and updates
Install Guild Stack through the supported host path, choose stable or beta, inspect the install receipt, and apply updates without hiding host limits.

Continue into Run to see how approved project inputs become specialist lanes and closure evidence.