Atlas Librarian · Temporal Cognition
Remembering something and remembering when it becomes relevant are different problems.
Atlas Librarian treats temporal cognition as a first-class memory concern. Scheduler Memory handles due tasks, deadlines, reminders, wake conditions and follow-up that should become active later. Event Memory records discrete signals and transitions that can feed timeline reasoning, episodic history or scheduler logic. This keeps time-aware action separate from passive knowledge storage.
Why time deserves its own segment
A fact can be true now while its required action belongs in the future.
Traditional memory often stores a sentence such as “review this next week” beside ordinary project facts. Atlas separates the future-action meaning from the factual content so time, follow-up and wake behaviour can be represented deliberately.
Semantic Memory can retain what is known: a project fact, stable identifier or durable mapping. It does not need to become an execution queue simply because the fact mentions a date.
Scheduler Memory represents that something becomes due, should wake a workflow or should be surfaced later. Its purpose is execution timing, not generic fact storage.
Event Memory records that a discrete signal or transition occurred. That event may then justify a scheduler action, episodic record or other project update.
Handover Memory can preserve the reason the future item exists and where the project should resume after the wake event.
Temporal memory flow
Signal, interpret, schedule, wake, reason and record the outcome.
The public architecture describes a high-level sequence. Internal trigger rules and execution thresholds remain private implementation details.
A memory candidate includes a deadline, follow-up requirement, reminder, wake condition, future reference or other time-sensitive meaning.
The memory front door can route the item toward Scheduler Memory when temporal execution is the dominant requirement, while related facts remain in their appropriate knowledge segments.
The temporal record keeps enough project and provenance context to know why the item exists and what it is connected to.
When the relevant time or condition is reached, the temporal item can re-enter Atlas processing instead of depending on the original interface or conversation still being open.
The wake event is not treated as an instruction frozen in the past. Atlas can combine it with current project state, rules, decisions and authoritative operational context before deciding the next permitted step.
The resulting event, decision, completed action or new handover can be retained in the appropriate segment so the project timeline remains coherent.
Event Memory
A signal is evidence that something happened, not automatically a permanent truth.
Event Memory gives Atlas a place for discrete transitions and observations before they are interpreted as stable facts, historical episodes or future obligations. This protects the distinction between “an event occurred” and “this is now the governing state.”
System, workflow or human-originated signals can be retained as discrete events with their own provenance and timing.
A state change can be remembered as an event even when the current authoritative state is owned elsewhere by a deterministic Speedway service.
Event records can be assembled chronologically when Atlas needs to understand sequence, causality or the path leading to an incident.
Important event sequences can contribute to Episodic Memory while isolated low-value signals can cool without cluttering active project context.
Scheduler as execution memory
The scheduler is not merely another folder of dated notes.
In the Atlas architecture, Scheduler Memory is explicitly linked to processing and follow-up. Its purpose is to reintroduce due items into the cognitive workflow and notification lanes even when no particular user interface remains open.
A future condition can cause a dormant item to become active again, reconnecting it to current project reasoning.
Time-bounded work can be preserved as a cognitive obligation rather than relying on conversational memory alone.
Where policy permits, a due item can feed the appropriate notification or workflow lane so relevant work is surfaced to the right participant.
A wake event should still reason against present context and deterministic authority. The fact that something was scheduled earlier does not bypass current policy, permissions or state validation.
Temporal cognition and project memory
Time-aware memory connects naturally to decisions, procedures, events and handovers.
Temporal work is most useful when Atlas can recover the surrounding reason. A scheduled follow-up may depend on a previous decision, a procedural step, an event that triggered the obligation and a handover that explains the project's current position.
A Decision Memory record can explain why a review was scheduled and what trade-off should be revisited when the wake event arrives.
A Procedural Memory record can provide the approved method that should be followed when a scheduled operational step becomes due.
An observed event can create a future obligation without changing the meaning of the event itself.
A handover can surface unresolved temporal obligations so project continuity includes not only present state but upcoming responsibilities.
Time is part of cognition