Docs section

Govern

Carry goals across runs while keeping workspace boundaries, permissions, quality, operations, and traces explicit.

Initiative · D8

map / active

Close only when three independent legs resolve

A passing run is evidence for the initiative. It is not, by itself, proof that the durable goal is closed.

Common tasks

Attach work to an initiative by choice and close it only with complete evidence.

Choose the correct write root and require approval for sensitive actions.

Use quality verdicts and operations runbooks without weakening their gates.

Route guides

Run durable initiatives
Use initiatives when a Guild Stack goal spans sessions, branches, or repos: attach runs by choice, track evidence, and close only after exec, release, and docs-sync gates.
Workspaces and federation
Use Guild Stack across a repo of repos without copying knowledge up: workspace manifests, child wikis, read-through recall, and settings inheritance.
Quality and operations
Run release checks and operations without losing control: computed quality verdicts, approved runbooks, dry-runs, and hard safety rails.
Security and permissions
What Guild Stack may touch, what always requires approval, and how repo content, secrets, network access, and MCP tools stay inside explicit boundaries.
Run traces and observability
Inspect what Guild Stack did after a run: manifests, provenance, handoff receipts, verification, event logs, and local dashboard views under .guild/runs/.

Continue into View to inspect the projections that read that state without becoming its owner.