Skip to main content

load / search / graph

Read commands load routed memory, search the vault, and inspect graph routing.

load​

engram load "<task>"
engram load --for-agents "<task>"
engram load --dry-run "<task>"
engram load --all "<task>"

load first anchors routing on meaningful query terms, ignoring generic memory words such as rule, knowledge, and common stopwords. It then refines the wider candidate pool into a compact context pack. Normal load reports selected and total related counts, like loaded 8 memory files / 14 total related memories.

  • --for-agents — agent-facing compact route (only id, type, tags, confidence, depends_on in frontmatter; one selected rule variant)
  • --dry-run — show candidate counts, narrowing tags, and match reasons without printing content
  • --all — return every visible routed match instead of the compact limit

workflow and workflows still route to skill memories, but generic type words do not make a broad match by themselves.

engram search "<topic>"
engram search --semantic "<topic>"

Default search is deterministic lexical search. search --semantic adds deterministic local similarity, not embedding-backed semantic search.

graph​

engram graph "<topic>"
engram graph --rebuild

Inspect graph routing. Run engram graph --rebuild after manual edits. The graph reports dependency layers, and engram load pulls routed prerequisites into the same compact context pack before deeper memories.

Graph related edges and vector hits cannot load unrelated memories by themselves; they only help rerank or expand memories that already overlap meaningful query terms. Explicit depends_on prerequisites may still load without their own keyword overlap.

Dependency layers​

depends_on: [release-foundation]
level: advanced

Use depends_on frontmatter when a memory should build on another memory instead of repeating it.

Next steps​