The Continuity Layer
The Continuity Layer · Definition

What Is a Continuity Layer for AI?

thecontinuitylayer.com/what-is-a-continuity-layer

This site’s working definition, and the anchor other pages cite. It is deliberately narrow — a continuity layer is a specific part of an AI system, not a synonym for memory.

Looking for business continuity or other meanings? What continuity layer means in AI →

This site’s working definition, v2 (7 November 2026)
A continuity layer is the part of an AI system that carries forward governed state across sessions, tools, models, and hosts: what is currently true, what changed, why it changed, by whose authority, and which evidence supports it. It sits above memory and retrieval, and below agent execution, turning stored history into usable, auditable continuity; and it can correct, supersede, revoke, expire, and forget what it carries, with evidence that it did.
The Continuity Layer
Version 1 (July 2026), verbatim, and what changed

A continuity layer is the part of an AI system that carries forward governed state across sessions, tools, and models: what is currently true, what changed, why it changed, and which evidence supports it. It sits above memory and retrieval, and below agent execution, turning stored history into usable, auditable continuity.

Version 2 adds three things the research of 2026 made unavoidable: hosts among the things state has to survive, authority on every write, and forgetting with evidence. The reasons are in the thesis; the framework that turns the definition into a test is the five obligations.

01

Where it sits

A continuity layer is defined by its position in the stack, not by any one feature.

It sits above the memory and retrieval infrastructure that stores and fetches facts, and below the agents that execute. It consumes what memory holds, governs what counts as current, and — by definition — hands every surface, every model, every tool, the same governed state. Because the layer improves whenever the memory beneath it improves, it is a layer, not a feature.

02

What it carries forward

Governed state is the authoritative current answer: what is true, what changed, why, and which evidence supports it, with every write passing through a contract.

What is currently true — the present state of the project or relationship, not a transcript of everything that happened.
What changed, and why — the moves that took the record from its old state to its current one, each with the reason attached, so a decision can be re-examined, not just observed.
By whose authority — who wrote or changed each fact, at what scope, so what an agent observed never becomes what the owner said.
Which evidence supports it — the provenance of each fact: where it came from, so any claim can show its work and any deletion can find what was built from it.
What has been let go — corrections, revocations, expiries and deletions, each a distinct operation with evidence that it was carried out.
03

What it is not

The distinctions that keep the term precise.

Not memory alone

memory stores the past; continuity governs what of it is still true, who may change it, and what should be carried at all.

Not retrieval

retrieval guesses what might be relevant to a query; it doesn't decide what is current.

Not long context

a bigger window extends one session; it doesn't carry the session forward.

Not a delete button

deleting a record is one of twelve operations the word “forget” covers; a continuity layer says which it did and shows it.

For the fuller structural version of these distinctions, see the Primer’s Memory Is Not Continuity, and the side-by-side breakdown in AI Memory vs AI Continuity. For what forgetting means, operation by operation, see the erasure ladder; for the whole section, start at The Continuity Layer.