Qorven’s memory system is built for conversations that never end. A Qor talking to you for six months shouldn’t perform worse than one talking to you for six days. This page is the practical companion to architecture/memory-system — what operators actually do.
The mental model
Every Qor has three stores that grow together:Rolling window
The N most-recent turns sent to the LLM on every call. Bounded by the model’s context window. Stays small.
Typed memories
Durable, searchable facts. Every important thing from a conversation gets written here. Bounded by Postgres storage (effectively unlimited).
Knowledge graph
Entities + edges extracted from memories. Answers relational queries like “what do we know about Project Apollo?”
Operator touch points
The in-chat 🧠 search
Toolbar above the composer. Semantic search; click a result to drop it into context.
Memory types
fact
Durable truth. “Priya’s laptop is a 2024 M3 MacBook Pro.”
preference
How someone likes things. “Priya prefers bullet points.”
decision
What was decided. “2026-04-20: ship v0.4 with Telegram only.”
identity
Who the Qor is. Injected into every system prompt.
event
Something happened. Decays over time.
observation
Weaker than fact, unverified. Low importance by default.
goal
Ongoing objective. Retrieved when planning.
todo
Actionable item. Lives until marked done.
How retrieval works
Hybrid: pgvector cosine similarity + BM25 full-text, merged via Reciprocal Rank Fusion. In practice beats either alone.- Semantic hits catch paraphrases (“budget” matches “spending limit”)
- Keyword hits catch exact terms (“Apollo” matches “Apollo” but not “launch”)
- RRF picks the best of both without tuning weights
Scope rules
Memories have ascope that controls who sees them:
| Scope | Who retrieves |
|---|---|
agent | Only this Qor (default) |
team | Qors in the same team |
task | Scoped to one task run |
session | Scoped to one session |
prime | Visible to the Chief-of-Staff Qor |
Where next
Types
Each type, when to use, examples.
Compaction
How long chats stay fresh.
Search
UI + API + CLI.
Knowledge graph
Entities, edges, traversal.
Dreaming
Nightly consolidation.
Privacy
Scopes + PII redaction.