Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Navigation & relations

Tools for moving through the memory pyramid and managing relations between memories.

Move up and down the abstraction hierarchy from a seed memory. zoom_out returns higher-layer (more abstract) memories derived from it; zoom_in returns lower-layer (more detailed) source memories it was abstracted from; both returns both directions.

Input

FieldTypeRequiredDescription
memory_idstring✓The seed memory.
directionstringzoom_in, zoom_out, or both (default).
levelsintegerLevels to traverse for zoom_in (1-5, default 1).
bankstring

Output

{
  "success": true,
  "source_memory_id": "uuid",
  "source_layer": 1,
  "zoom_in": [ /* lower-layer source memories */ ],
  "zoom_out": [ /* higher-layer abstractions */ ]
}

Examples

// From a JWT note, find the auth-architecture concept built on top of it
{ "memory_id": "uuid-of-jwt-note", "direction": "zoom_out" }

// From a concept memory, find all source evidence
{ "memory_id": "uuid-of-concept", "direction": "zoom_in", "levels": 3 }

Note

To restrict a semantic search to a specific layer, use query_memory with pyramid_config (e.g. { "mode": "top_heavy" } or layer_weights), not navigate_memory.

update_memory

Update an existing memory’s content and/or append relations by ID.

Input

FieldTypeRequiredDescription
memory_idstring✓
contentstringNew content. Re-embeds the memory.
relationsarrayRelations to append, as [{ "relation": "...", "target": "..." }].
bankstring

Output

{
  "success": true,
  "message": "Memory updated"
}

Warning

Updating content re-embeds the memory. This is an LLM-free operation (uses the same embedding model), but it does cost time and changes the semantic identity. Use it for typo fixes, not wholesale rewrites.

Manually create a relation between two existing memories. The reverse relation is created automatically (e.g. references → referenced_by).

Input

FieldTypeRequiredDescription
source_idstring✓Source memory ID (the “from” side).
relationstring✓Relation type: references, contradicts, supports, depends_on, part_of, extends, similar_to, summary_of, synthesizes.
target_idstring✓Target memory ID (must be an existing memory).
strengthnumberRelation strength 0.0-1.0 (default 1.0).
bankstring

Output

{
  "success": true,
  "message": "Relation created",
  "data": {
    "source_id": "uuid",
    "relation": "depends_on",
    "target_id": "uuid",
    "reverse_relation": "depended_on_by",
    "reverse_created": true
  }
}

Note

source_id and target_id must both be valid UUIDs of existing memories. Hierarchical relations (summary_of, part_of, synthesizes) require the source to be at a higher layer than the target. Duplicate links are rejected.

Suggested relation predicates

CategoryPredicates
Structuralchunk_of, summary_of, part_of, next_chunk, previous_chunk
Semanticreferences, extends, supersedes, depends_on, implements, configures
Layeredderived_from, emerges_from, instance_of, broader_than
Provenanceauthored_by, cited_by
Contradictioncontradicts

remove_relation

Remove a specific relation from a memory. The reverse relation on the target is removed automatically.

Input

FieldTypeRequiredDescription
memory_idstring✓Memory to remove the relation from.
relation_typestring✓The relation type to remove (e.g. references).
target_idstring✓The target memory ID in the relation.
bankstring

Output

{
  "success": true,
  "message": "Relation removed",
  "data": {
    "memory_id": "uuid",
    "removed_relation": "references",
    "removed_target": "uuid",
    "reverse_relation": "referenced_by",
    "reverse_cleaned": true
  }
}

Relations vs auto-linking

When auto-linking is enabled (via auto_link_threshold), the server automatically creates references relations to semantically similar existing memories. force_link is for cases where:

  • You know of a relation the auto-linker missed
  • You want a non-semantic relation (e.g. next_chunk, part_of)
  • You want to control the relation strength explicitly

Next