Guild Stack

Docs section

Migrate

Move from v1 to v2 by mapping commands and settings, then proving one complete run.

Start with Migrate from v1 to v2All docs

Page evidence

Operational mapMigrate the control surface, then prove one full run.
Before
  1. nested commandslegacy names
  2. config.ymllegacy settings
  3. claimed supportlabel-led state
After
  1. flat verbsone command surface
  2. settings.jsonclosed-key config
  3. receipt-backed stateverified promotion
Inventory first, map commands and settings, then prove the cutover with one bounded run and its receipts.
Diagram notes and sources
  • docs/v2/distribution.md
  • docs/v2/host-adapter-migration-spec.md

Common tasks

Preserve a rollback path until proof exists.

Take the safe path

Inventory the current setup before changing command or settings surfaces.

Map commands

Replace removed v1 forms with the current flat command surface.

Prove the cutover

Run one bounded task and inspect its approvals and receipts.

Route guides

Map, migrate, verify.

Migrate

  • Migrate from v1 to v2

    Move from Guild Stack v1 to v2: command renames, settings.json migration, rigor flags, phase verbs, and the approval-gated lifecycle.

The cutover ends with evidence, not renamed commands.

Return to Start and run the current first-run path against the migrated project.
Start docsDocs gateway