Guild Stack

Docs section

Learn

Map a codebase, keep canonical knowledge local, and evolve reusable capability through explicit gates.

Start with Understand your codebaseAll docs

Page evidence

Operational mapRuns propose. Humans promote. Derived views rebuild.
  1. Run evidenceobserved fact
  2. Candidatesourced proposal
  3. Human gateapprove or archive
  4. Wikicanonical memory
  5. Recallgraph + index + cache
Map current source, promote stable facts through a gate, and rebuild every derived projection from canonical Markdown.
Diagram notes and sources
  • docs/v2/knowledge-memory.md
  • docs/v2/codebase-understanding.md

Common tasks

Deepen only where evidence is needed.

Map before changing

Build the codebase map and deepen only where the task needs evidence.

Query project memory

Keep canonical knowledge in Markdown and treat graphs and indexes as projections.

Promote deliberately

Turn recurring evidence into evaluated skill or specialist changes.

Route guides

Move from source to durable knowledge.

Learn

  • Understand your codebase

    Use /guild:learn to map a codebase, build a knowledge graph, produce an onboarding tour, analyze changes, and approve deeper scans before they run.

  • Project memory and wiki

    Guild Stack records canonical project memory as gated Markdown under .guild/wiki/, then derives recall indexes, graph views, and specialist context from it.

  • Evolve skills and specialists

    Guild Stack can learn from real runs without silent mutation: reflections propose better skills or specialists, evals test them, and you approve promotion.

Reusable knowledge stays traceable to source.

Continue into Govern to see how boundaries and close gates keep that knowledge accountable.
Govern docsDocs gateway