SuperLocalMemory records local behavioral signals that influence ranking without a separate LLM call for the learning step. Three phases — baseline observation, rule-based heuristics, optional ML model activation. Inspect signals, thresholds, and rank changes; optional modes and integrations retain their own network paths.
Semantic, graph, and adaptive channels feed the ranking pipeline. Each channel is independently inspectable.
Dense vector candidates from a local embedding model. Finds memories conceptually related to a query even when keywords do not match exactly.
Entities — files, functions, concepts — are extracted and linked. Querying one entity can surface linked neighbours via graph traversal, not keyword matches alone.
Local behavioral signals — access patterns, explicit feedback, recency — adjust candidate rank without an additional LLM call for the learning step itself.
Recall emits local exposure telemetry. Exposure alone is not positive feedback and does not increase truth or trust scores stored in memory.
Optional reranking and channel diagnostics can record exposure. Explicit positive, negative, or corrective feedback remains separate from stored-memory confidence and trust. No model activation at this phase.
Heuristic boosts from learned patterns: recency weight, access frequency, and trust score. The ranking influence is deterministic and inspectable — no trained model is loaded at this phase.
When the learning path has sufficient valid signals and model activation is enabled, it can train on local behavioral state. Verify activation, model state, and rank impact in the installed release.
Each signal type has distinct semantics. Read the source before inferring intent from a rank change.
These features require hooks, background workers, or explicit configuration. Each needs independent verification for a complete deployment review.
Query enters, candidate producers run, re-ranking applies behavioral weights, ranked context exits. Every stage is traceable.
Read the published research behind the memory architecture, or follow the installation guide to deploy V4.