Canonical memory model#
Canonical memory persists knowledge beyond one model context. Supported scopes organize Room, Project and System information. Entries can carry tags, provenance, timestamps, lifecycle and change history; authorized mutations should preserve traceability.
Useful memory includes decisions, preferences, project conventions, verified findings and durable task context. It is not the location for API keys, OAuth grants, passwords, setup tokens, session cookies or private credential files.
The product has graph-based navigation and a 3D memory view. Related graph implementations use Graphology/Sigma-style infrastructure; the inspected 3D view projects 3D coordinates onto a canvas. Do not describe Sigma itself as the complete 3D renderer or infer a particular renderer solely from a marketing image.
A graph node is a navigable representation of stored knowledge. An edge can indicate provenance or a computed relationship. Similarity is not proof, authority, equivalence or causality.
Retrieval, indexing and context budgeting#
The codebase includes deterministic lexical/relationship techniques, including English/Greek TF-IDF and cosine similarity. Additional indexing or embedding behavior depends on installation and settings. Do not claim every retrieval path uses no external service or that every query uses embeddings.
Recommended retrieval flow:
- Identify scope and a few distinctive search terms.
- Retrieve bounded results with source references.
- Inspect dates, provenance and superseding entries.
- Expand only the relevant result.
- Check current source/runtime evidence before changing state.
- Save concise durable findings only when appropriate and authorized.
Persistent memory does not enlarge a model's context window. Loading an entire history can obscure current instructions and waste context. Old observations are not current measurements; successful historical deployments do not prove a new build.
Generic starter memory in public packaging is separate from mutable owner memory. A fresh install must not contain another operator's private history or provider profiles.