Search / Recall
Recall is not just semantic search. UnifiedMemory applies scope and trust gates, then ranks eligible memories using multiple signals.
Retrieval order
- Hard filters: workspace/container, lifecycle, namespace firewall, scope, visibility, current state, and trust bucket.
- Candidate sources: semantic search, keyword/token match, entity links, temporal resolver, graph edges, and profile/core facts.
- Fusion and budget: rank-based scoring plus token-budgeted prompt assembly.
- Courtroom links: important results should be inspectable through evidence.
- Abstention: when candidates do not clear the system relevance floor, recall returns no direct answer instead of filling the top-k with weak matches.
Query intent
Current queries prefer latest valid facts. Historical or change-over-time queries can retrieve superseded facts, but they must be labeled as historical.
Currentness is not relevance. A memory can be the newest fact in a container and still be suppressed if semantic, keyword, entity, graph, profile, or focused lexical evidence does not connect it to the query.
See Recall for the public API.