Most AI systems preserve conversation history. Memex preserves structured continuity state. This paper introduces the architectural boundary between reasoning compute and continuity runtime infrastructure. Inspired by the public architecture documents.
by
Most AI systems treat continuity as conversational memory.
Memex approaches continuity differently.
Continuity is treated as runtime infrastructure.
This distinction changes the architectural boundary entirely.
The goal is not to preserve every token, interaction, or generated output.
The goal is to preserve the structured continuity conditions required for reasoning to continue across time.
The system therefore separates:
Reasoning engines may evolve.
Continuity structure must remain stable.
This architectural boundary exists because long-running AI-assisted work accumulates continuity pressure over time.
As sessions fragment:
assumptions drift
unresolved boundaries disappear
operational grounding weakens
repository awareness collapses
continuity becomes increasingly local
Most systems attempt to compensate through:
summaries
retrieval
generated memory
conversational reconstruction
Memex instead attempts to preserve explicit continuity state.
The architecture currently organizes continuity around five primitives:
Together, these structures regulate continuity across time.
Snapshots preserve structured continuity state.
Trails preserve observed continuity evidence.
Reality grounding prevents generated interpretation from replacing operational truth.
Loops regulate continuity drift relative to Compass.
The runtime intentionally prefers:
instead of:
Missing continuity remains visible.
Observed reality outranks interpretation.
This separation becomes increasingly important as continuity systems evolve across:
repositories
sessions
runtime environments
operational timelines
long-horizon reasoning work
Without stable continuity semantics:
summaries replace evidence
navigation appears authoritative
unresolved seams disappear
continuity drift compounds silently
The runtime therefore preserves explicit distinctions between:
observed truth
declared truth
projected truth
derived truth
A continuity system becomes unstable when these layers collapse into each other.
Continuity depends on stable semantic boundaries.
This is also why Memex models unresolved architectural pressure directly through seams.
A seam is not a task.
A seam is an active unresolved boundary.
The next action represents the move applied to that boundary.
This distinction helps continuity remain structurally stable across sessions and implementation cycles.
Operational trails preserve observed continuity evidence across time.
Repo cognition preserves structural continuity across evolving repositories.
Rehydration restores continuity state without reconstructing missing context through narrative approximation.
The system repeatedly enforces the same constraint:
Do not silently mutate continuity.
Do not invent missing state.
Do not collapse uncertainty into certainty.
Memex does not attempt to simulate persistent intelligence.
It attempts to preserve the continuity conditions required for reasoning to remain coherent across time.
The architecture remains under active evolution.
The invariants remain stable:
Compass anchors purpose
Snapshots structure time
Trails preserve memory
Reality grounds observation
Loops regulate continuity
Continuity is not treated as memory.
Continuity is treated as infrastructure.
