Atlas Librarian · Project Continuity
Atlas treats the project—not the conversation—as the persistent unit of cognition.
Long-running engineering and operational work cannot depend on one chat transcript staying open forever. Atlas Librarian preserves project cognition across sessions through specialized Handover, Decision, Procedural, Rules, Semantic, Episodic and related memory. The current conversation becomes a working surface over durable project knowledge rather than the sole container of what the system knows.
Project as the durable unit
Conversation context is useful, but project state must survive outside it.
A conversation naturally emphasizes the recent exchange. A project needs a broader memory horizon: architecture decisions from months ago, current rules, procedures that still apply, incidents that explain a workaround, and the exact state required to continue unfinished work. Atlas Librarian stores those concerns in their own memory roles.
A temporary interface for current reasoning, questions, tool use and working context. It can end without ending the project.
The durable collection of facts, decisions, procedures, rules, events, entities, relationships and handovers that gives future sessions continuity.
The subset of project memory selected by the Conscious Memory Index for the current task.
Low-heat retained history that remains available when a future question needs deep traceability without burdening routine work.
Handover Memory
A handover is a cognitive checkpoint, not a chat summary.
Handover Memory is designed to transfer the state of work across sessions or agents. It records enough project context to restart intelligently: what has been completed, what remains unresolved, what changed, what evidence exists and where execution should resume.
Important completed stages can be captured as continuity anchors so later work does not reconstruct progress from raw history.
The handover can preserve the active project position, including unfinished work and the dependencies that prevent immediate completion.
Continuation records can make the intended next step explicit while temporal obligations can be linked to Scheduler Memory when timing matters.
Future Atlas sessions can retrieve the latest authoritative handover as high-priority continuity context before reloading deeper history.
Decision Memory
Remembering the answer is weaker than remembering why it became the answer.
Decision Memory preserves architectural, operational and policy choices together with rationale, trade-offs and consequences. When a later decision supersedes an earlier one, the lineage can remain traceable rather than erasing evidence that the previous path ever existed.
The current decision can be retained explicitly rather than inferred from scattered implementation details.
The reason behind the decision remains available to future operators who were not present when the choice was made.
Alternatives and consequences can be preserved so a future reconsideration starts from known constraints instead of repeating the original debate.
A new decision can replace an old one as current guidance while the historical record remains available for audit and reasoning.
Rules Memory
Hard constraints should not disappear inside a sea of historical prose.
Rules Memory preserves always, never, must and other non-negotiable project constraints. It is intentionally distinct from Decision Memory because a rule is expected to act as a guardrail during reasoning and action selection, not merely explain what somebody chose previously.
Locked operational and architectural constraints can be surfaced as high-priority context when a proposed action would conflict with them.
Rules persist across sessions so the system does not depend on the current operator remembering every historical instruction.
Rules can be marked as authoritative within Atlas memory, distinguishing them from preferences, incidents and historical observations.
Procedural and Episodic Memory
How work should happen and what actually happened are separate kinds of knowledge.
This separation is central to learning from operations without confusing an exception with the approved method.
Runbooks, workflows, repair steps and repeatable procedures describe the intended way to execute a task.
Specific incidents, completed changes, failures, successes and execution traces describe what happened on a particular occasion.
Future reasoning can consult both the procedure and relevant historical episodes to understand whether an unusual result reflects a known failure mode or a genuine change in conditions.
A one-off workaround can remain an episode until a deliberate Decision or Rule changes the approved operating method.
A continuity cycle
Project cognition evolves without losing its lineage.
A typical long-running cycle can involve all of these memory roles without merging them into one undifferentiated record.
New project evidence enters Semantic or Event/Episodic Memory according to its meaning.
Decision Memory records the chosen path and rationale; any affected rule is updated deliberately rather than inferred.
Procedural Memory captures the repeatable new workflow when execution guidance genuinely changes.
The Conscious Memory Index selects the relevant facts, rules, procedures and history for the active task.
Handover Memory records the execution checkpoint and unresolved work so another session can restart with high-value continuity.
Superseded or low-heat material remains traceable through the thermal memory lifecycle without crowding current cognition.
Why this matters operationally
Persistent cognition reduces re-explanation, repeated mistakes and context loss.
In a complex multi-application platform, many failures are not caused by a lack of raw information. They happen because the current operator cannot see why something was done, which rule still applies, what happened during the previous attempt or exactly where the work was left. Segmented project cognition is designed to preserve those distinctions.
New sessions can begin from a governed handover rather than reconstructing the project from hundreds of messages.
Decision and episodic history make it easier to understand what changed before attempting a rollback or alternative path.
Procedures and rules remain retrievable as current guidance even when the people performing the work change.
The project can retain knowledge beyond the individual conversation, operator or agent that first encountered it.
Persistent project cognition