Atlas Librarian · Selective Recall
The Conscious Memory Index decides what memory should become active.
Atlas Librarian is also the Conscious Memory Index: the front-door index, router and segment selector for cognitive recall. The architectural principle is straightforward—consult the memory index first, identify the relevant segments and records, then load only the needed subset into Working Memory. Persistent project history remains available without becoming permanent prompt clutter.
Why an index exists
Persistent memory becomes useful when the system can decide what not to load.
A project can accumulate thousands of facts, incidents, procedures, decisions, paths and artefacts. Keeping all of them in active context would be expensive, noisy and potentially misleading. The Conscious Memory Index gives Atlas a routing layer between durable retention and immediate reasoning.
The index can reason about the cognitive role of a memory candidate—fact, procedure, decision, rule, route, event, handover and other canonical types—before active context is assembled.
Memory can be scoped to project, thread, user, global or system context. That helps prevent a local interaction detail from being treated as universally relevant.
Some retained memory can represent authoritative memory-domain knowledge while other records are explicitly historical, contextual or preference-oriented. Recall can preserve that distinction.
Freshness, use and thermal state provide additional lifecycle signals. A relevant but cooled record remains retrievable without necessarily competing with hot current context.
Working Memory
Active reasoning is a bounded set, not a second copy of long-term memory.
Working Memory exists specifically for the subset of memory in current use. It is distinct from Scratch Pad, which stages complete artefacts, and from the durable memory segments that preserve long-term project knowledge.
Working Memory receives the records that matter for the current reasoning task after the Librarian has narrowed the search space.
Active context is allowed to change rapidly. Durable facts, decisions and procedures do not need to be rewritten merely because a different task becomes active.
If a task needs an entire document, image or structured artefact, Scratch Pad provides a separate whole-object staging role instead of overloading Working Memory.
Episodic and Archive Memory can retain extensive history while the active reasoning set remains focused on the immediate problem.
Checked out versus used
Seeing a memory candidate and relying on it are different events.
The Atlas Librarian read path explicitly distinguishes a memory being retrieved from a memory being used. That distinction gives the memory lifecycle better evidence than a simple retrieval count.
A record may be returned as a candidate during recall. That proves it was made available to the reasoning process, not that it influenced the outcome.
A separate usage signal records that a memory actually participated in reasoning or execution. Use can therefore influence freshness differently from speculative retrieval.
Important working material can be explicitly promoted into durable memory rather than assuming that every transient observation deserves permanent status.
Material can cool over time and move toward long-term retention while remaining accessible when explicit search or historical reasoning requires it.
Selective recall pattern
A high-level recall cycle keeps durable context available without letting it dominate every task.
The following pattern describes the public architectural intent rather than the private ranking or classification recipe.
Determine the project, scope and likely cognitive role required by the current task.
Use the Conscious Memory Index to identify the memory segments and candidate records most relevant to that role.
Consider authority, freshness, current status, supersession and relationships so old or contextual material is not mistaken for current truth.
Load the bounded set needed for reasoning, with complete artefacts staged separately when whole-object context is required.
Atlas can use the selected context to explain, recommend or coordinate while deterministic Speedway services retain authority for protected operational changes.
Update memory lifecycle evidence when a record was actually used, and preserve any new durable knowledge through the appropriate governed memory path.
Why this differs from basic retrieval
The architecture combines retrieval with memory meaning, lifecycle and project continuity.
Semantic similarity can be useful, but similarity alone does not tell a system whether a record is a rule, a superseded decision, a user preference, an incident or a current project fact. Atlas Librarian makes those distinctions explicit at the memory architecture level.
The index can select a cognitive segment before active context is assembled, reducing the assumption that every similar passage deserves equal status.
Status and supersession matter. A once-correct decision can remain historically valuable while no longer being the current authority.
Recall is designed around durable project continuity. The current conversation is a working surface, not the sole container of institutional memory.
Index first, reason second