Operational route

Brownfield learn

Map an existing repo, preserve durable project knowledge, and give later specialists the right context before edits begin.

Page evidence

Operational mapGive each lane the smallest complete brief.
  1. Task lanescope + acceptance
  2. Recallrelevant wiki + graph
  3. Bundlefiles + constraints
  4. Specialistbounded execution
  5. Receiptchanges + omissions
/guild:init --learn

Route comparison

Same job. A visible operating record.

Without a route record

Agents often read broadly, miss prior decisions, and repeat the same discovery work in the next session.

With Guild Stack

Guild Stack runs Init learning, keeps canonical knowledge in .guild/wiki/, and feeds relevant recall into later planning and build lanes.

Route stops

Request to verified result.

  1. 01

    Classify the project

    Init detects whether the repo needs greenfield setup, brownfield learn, or later repair work.

  2. 02

    Map before planning

    The first pass can create a structural map before deeper graph or onboarding work is requested.

  3. 03

    Keep canon in files

    Graphs and indexes are rebuildable projections; durable knowledge stays in .guild/wiki/.

  4. 04

    Recall into lanes

    Future specialists receive relevant wiki and graph context inside bounded context bundles.

Receipts

What the route leaves behind.

  1. 01
    Path .guild/indexes/codebase-map.json
    Role

    Rebuildable structural map.

  2. 02
    Path .guild/indexes/knowledge-graph.json
    Role

    Derived graph when deep learn is built.

  3. 03
    Path .guild/wiki/
    Role

    Canonical durable project knowledge.

  4. 04
    Path .guild/context/
    Role

    Per-lane bundles assembled from relevant memory and files.

Next

Follow this route through an illustrative run.

The demo traces one bounded task through approvals, specialist lanes, review, verification, and the final run record.