Docs section

Build

Trace module ownership, host boundaries, typed communication, and canonical vocabulary.

Page evidence

Operational mapAssignments go out. Typed receipts come back.
Lead
  1. lane assignment
  2. review packet
  3. gate decision
Specialist
  1. focused context
  2. bounded work
  3. handoff receipt
.guild/runs/
  1. task
  2. handoff
  3. review result

Files carry authority, evidence, and recovery state. Chat is not the durable bus.

Host-specific execution can degrade; typed handoffs, receipts, and trace contracts preserve the inspectable route.
Diagram notes and sources
  • docs/v2/architecture/README.md
  • docs/v2/dispatch-execution.md

Route guides

Read interfaces before implementation detail.

Build

  • System architecture

    Guild Stack internals: one lifecycle, module-owned resources, host adapters, file receipts, settings resolution, and durable .guild/ evidence.

  • Handoff and communication contracts

    The Guild handoff bus: specialists write typed receipts under .guild/runs/, and leads, review, verification, and replay consume files.

  • Glossary

    The canonical Guild Stack vocabulary for nesting, lifecycle, host, substrate, review, knowledge, and model tiering.

Portable behavior begins at a durable boundary.

Continue into Migrate to map older surfaces onto the current contracts and prove one cutover.