← Home

Resources

Three ways in, help when something breaks, and where Guild Stack lives.

Start where you are

  1. New here Install → onboard a repo → first team run See a result in your own project before any theory. Start with install →

    Then: onboard a repo →

  2. Want control Commands → configuration → cost and tiering The commands and settings behind what the other pages demonstrate. Open the command reference →

    Then: configuration →

  3. Want internals Architecture → review gates → conformance evidence What a run does underneath, and how the release proves it. Open the architecture →

    Then: how releases are verified →

When something breaks

Releases and community

How these docs are tested

The install guide and every use case name the validation-suite scenarios that back them, and each page's claims trace to what those scenarios check. A page that is not executed by the suite says so with an illustrative label.

The release itself ships with evidence: every conformance check passed on both supported tools before 3.0.0 shipped, signed and tied to the exact source commit. How it’s verified →

The release route: a version cut on next, conformance evidence built at that exact commit, a promotion gate that refuses mismatches, a tagged merge to main, and a dev bump that reopens next.
Open full size