02 — Core Definitions

Token

A token is a unit of text that a language model processes. A token may be a full word, part of a word, punctuation, or another short text unit depending on the model and language.

Context window

A context window is the bounded amount of text or information available to the model during a response. The larger the context window, the more material can be considered at once, but larger context does not automatically create durable memory, project authority, or verified state.

Memory

A memory feature stores or references information across conversations, usually for personalization, preferences, and recurring context.

Retrieval

Retrieval is the act of finding relevant information from an external source, file, database, knowledge base, or prior material and bringing it into the current working context.

Retrieval can support continuity. It does not guarantee it.

Session state

Session state is what the system, interface, or tool environment can track during a particular interaction or workflow. It may include the current thread, uploaded files, tool outputs, temporary context, or active project settings.

Project continuity

Project continuity is the durable, inspectable, current state of the work.

It answers: what are we doing, what has been decided, what sources are active, what assumptions are still valid, what changed since the last state, and what should survive the next session, branch, handoff, or restore.

Project continuity is not guaranteed by chat, memory, retrieval, or context windows.

It has to be managed.

03 — The Continuity Stack

The higher the work’s consequence, the less the operator can rely on felt continuity.

04 — What Each Layer Is Good For

Tokens are good for processing. They are not memory, evidence, or proof that the model understands the project.

Context windows are good for current working attention. They help the model work with currently available material, but a context window is still bounded. It is not durable project state.

Memory is good for recurring personalization. Memory may help the system know the operator. It does not automatically know the project.

Retrieval is good for source access. Retrieval is not the same as truth. It is access to candidate material.

05 — The Felt Continuity Problem

Chat creates a continuity illusion because humans experience sequence as relationship.

The thread is still there. The assistant remembers the tone. The interface replies as though the work is still intact. The user may feel: We are continuing.

Technically, the system may be using visible thread context, saved memory, past-conversation reference, retrieved files, summaries, system instructions, project instructions, current prompt reconstruction, or plausible inference.

Those are different mechanisms.

They can all feel like memory to the user.

They are not the same.

06 — Continuity Failure Modes

Context drift

The system gradually loses track of the original task, constraints, or priorities.

Counterweight: restate current objective, use checkpoints, create a savepoint, ask for current-state summary.

Memory illusion

The system seems to remember the project because it remembers something related.

Counterweight: distinguish preference memory from project state, keep current-state packets, review memory where possible, use explicit project records.

Retrieval mismatch

The system retrieves material, but not the right material.

Counterweight: ask which source was used, inspect retrieved passages, check recency and scope, keep source-of-truth labels.

Summary compression loss

The system summarizes prior material and loses important nuance.

Counterweight: preserve raw notes, keep decision logs, mark unresolved issues, compare summary against source material.

State contamination

Old or wrong state persists into new work.

Counterweight: conflict register, restore preview, explicit operator approval, savepoint after accepted changes.

Accountability gap

The system continues smoothly after failure, but nobody owns the affected state.

Counterweight: Repair Surface Audit, verified delta, accountable authority, refusal point.

07 — Continuity Taxonomy

The dangerous form is when one continuity type is mistaken for another.

Style continuity is not project continuity. Retrieval continuity is not accountability continuity. Conversational continuity is not decision continuity.

08 — Operator Test: What Does the System Actually Have?

When continuity matters, ask:

What information are you using right now?

Then force the distinction:

Separate your answer into:
1. current conversation context
2. saved memory or remembered preferences
3. retrieved files or sources
4. inferred assumptions
5. unknowns
6. state that requires operator confirmation

This prompt does not make the system perfect. It makes the continuity claim inspectable.

09 — The “Tokens Are Not Memory” Field Card

Use this when the interaction feels continuous but the stakes are rising.

1. What is currently in context?
2. What is remembered as a preference, if anything?
3. What has been retrieved from a source?
4. What is being inferred?
5. What is the current project state?
6. What has been approved?
7. What could be stale?
8. What needs a savepoint?
9. What should not carry forward?
10. What would prove that continuity has been preserved?

10 — Practical Distinctions

Context is what the system can use now.

Memory is what the system may reference later.

Neither automatically equals project state.

Memory can store preferences or recurring context. A source of truth is an authoritative record.

Retrieval brings material into view. Knowledge requires correct interpretation, scope, and relevance.

A summary compresses. A savepoint preserves state.

A conversation is an exchange. A workflow is a process with state, transitions, decision gates, and outputs.

11 — When to Use What

Use chat context when the task is exploratory, failure cost is low, work benefits from dialogue, output will be reviewed, and state does not need to survive.

Use saved memory when preferences are stable, personalization helps, the remembered item is low-risk, and the operator can review or correct memory.

Use retrieval when sources matter, the answer depends on documents, the system needs to inspect prior material, and claims need support.

Use a notebook/repository when reasoning must persist, citations must attach, versions matter, the project has a durable output, and multiple agents or people need the record.

Use a savepoint when decisions have been made, state must survive a new session, work is about to branch, another agent will take over, old/new instructions might conflict, or restoration needs to be inspectable.

Use Repair Surface Audit when failure occurred, apology appeared, continuation feels restored, state is uncertain, and a downstream action depends on the answer.

12 — Continuity Prompts

Current State Prompt

State the current project state in five parts:
1. objective
2. active constraints
3. approved decisions
4. unresolved questions
5. what should not be carried forward

Context Audit Prompt

What are you relying on right now?
Separate:
- current thread context
- saved memory or preferences
- uploaded files / retrieved sources
- assumptions
- unknowns
- items requiring operator confirmation

Memory Boundary Prompt

Do not rely on memory for project state.
Use only the current savepoint, uploaded source material, and explicit instructions in this thread.
List any memory-based assumptions separately.

Retrieval Verification Prompt

For each claim, name the source used, the specific support it provides, and whether the source is current, partial, or background only.

Savepoint Trigger Prompt

Before continuing, identify what state needs to survive:
- decisions
- constraints
- source backbone
- rejected directions
- open questions
- next action
Then prepare a savepoint candidate for approval.

Post-Failure Continuity Prompt

Identify the failure, name the affected state, show the verified delta, and state whether this is safe to continue.

13 — Applied Scenarios

The assistant “remembers” an old instruction

Ask:

Separate what you remember from what is present in the current project state. Which instruction is active, which is historical, and which needs operator confirmation?

Better access mode: savepoint or repository.

The thread is long and the answer sounds confident

Ask:

List the assumptions you are carrying forward. Mark each as current-thread, source-backed, memory-based, or inferred.

Better access mode: notebook / source-backed state record.

A retrieved source partially supports the answer

Ask:

Show the exact source support and identify what the source does not establish.

Better access mode: source-backed repository or NotebookLM-style source review.

A project crosses sessions

Use a savepoint:

Restore from the latest approved savepoint only. Do not infer missing state from memory.

Better access mode: savepoint + project state file.

The system apologizes for losing context

Ask:

What context was lost, what state was affected, what has been restored, and what remains uncertain?

Better access mode: savepoint restore or manual state reconstruction.

14 — What This Replaces

Replaces “It knows what I mean” with “What context is available?”

Replaces “It remembers this project” with “What state has been preserved?”

Replaces “It found the source” with “What source was retrieved, and what does it actually support?”

Replaces “It apologized, so we can continue” with “What changed, and is it safe to continue?”

Replaces “The thread is enough” with “What needs a savepoint?”

15 — Source & Claim Notes

This report uses selected technical sources lightly.

This VSR’s taxonomy — context continuity, memory continuity, retrieval continuity, project continuity, accountability continuity — is a VECTOR / DFEI applied framework. It is not an externally established taxonomy.

The point is practical control:

Do not treat felt continuity as durable state.

16 — Closing Signal

The chat may continue. The model may respond. The thread may remain visible. The memory layer may recall a preference. The retrieval system may find a relevant document.

None of that proves the project state is intact.

Continuity is not the feeling that the exchange has kept going.

Continuity is the evidence that the right state survived.

The operator’s rule:

If the state matters, make it explicit.