Without a route record
Knowledge lives in long transcripts or broad summaries that drift from source files and prior decisions.Operational route
Project memory
Carry durable project decisions into future work without turning chat history or derived indexes into the source of truth.
Page evidence
- Run evidenceobserved fact
- Candidatesourced proposal
- Human gateapprove or archive
- Wikicanonical memory
- Recallgraph + index + cache
Route comparison
Same job. A visible operating record.
With Guild Stack
Guild Stack keeps .guild/wiki/ canonical, treats graph and links as rebuildable projections, and recalls only relevant knowledge into each lane.Route stops
Request to verified result.
- 01
Classify knowledge
Durable pages carry structured labels, applies-to scope, and source references.
- 02
Propose, then gate
Learning checkpoints emit candidates; humans promote durable memory through the existing path.
- 03
Recall before read
Specialists search memory before broad file reading.
- 04
Name omissions
Context assembly records what was dropped for budget so loss is visible.
Receipts
What the route leaves behind.
- 01 Path
.guild/wiki/**RoleCanonical project memory.
- 02 Path
knowledge-links.jsonRoleDerived work-to-knowledge edges.
- 03 Path
provenance.jsonRolePer-run close facts and trace references.
- 04 Path
.guild/context/RoleBounded specialist context with omissions recorded.
Next
