Without a route record
Agents often read broadly, miss prior decisions, and repeat the same discovery work in the next session.Operational route
Brownfield learn
Map an existing repo, preserve durable project knowledge, and give later specialists the right context before edits begin.
Page evidence
- Task lanescope + acceptance
- Recallrelevant wiki + graph
- Bundlefiles + constraints
- Specialistbounded execution
- Receiptchanges + omissions
Route comparison
Same job. A visible operating record.
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.
- 01
Classify the project
Init detects whether the repo needs greenfield setup, brownfield learn, or later repair work.
- 02
Map before planning
The first pass can create a structural map before deeper graph or onboarding work is requested.
- 03
Keep canon in files
Graphs and indexes are rebuildable projections; durable knowledge stays in .guild/wiki/.
- 04
Recall into lanes
Future specialists receive relevant wiki and graph context inside bounded context bundles.
Receipts
What the route leaves behind.
- 01 Path
.guild/indexes/codebase-map.jsonRoleRebuildable structural map.
- 02 Path
.guild/indexes/knowledge-graph.jsonRoleDerived graph when deep learn is built.
- 03 Path
.guild/wiki/RoleCanonical durable project knowledge.
- 04 Path
.guild/context/RolePer-lane bundles assembled from relevant memory and files.
Next