Signals from the Field
thecontinuitylayer.com/signalsLabs, tools, papers, and language worth tracking in the continuity field. Each entry: what it is, why it matters, and how it relates to project continuity — not a ranking, and not endorsement. Newest first, each with the date this project spotted it. Entries with a dated profile link to Field Watch. For the sourced research behind this project’s own claims, see the Research library.
Signals from the field
CCL — Context Continuity Layer
Context Layer Systems, Inc., founded by Morgan Allen, describes CCL as “a post-authentication context governance and infrastructure layer” and an open architectural standard, with STACCR as its pre-GA implementation. The site says only encrypted token references pass through the system and that destroying a subject's key is designed to make that context inaccessible, backed by a signed erasure certificate.
The site describes STACCR as pre-GA and says CCL is not an AI memory store. Its name is close to this site's; the projects are unaffiliated, and this entry makes no claim about who first used the name. Capability claims are the vendor's; this project has not tested them.
“Control-Plane Placement Shapes Forgetting”
Dongxu Yang's June 2026 preprint studies the operations that change stored memory (supersede, release and purge) rather than recall, across thirteen system configurations. It introduces ForgetEval, including intent-aware deletion cases, and argues that existing benchmarks measure only recall.
Single-author preprint with author-reported results. This project has not reproduced ForgetEval or the reported deletion accuracy.
GateMem
The June 2026 preprint evaluates shared memory across multiple principals, combining legitimate-request utility, access boundaries and forgetting after deletion requests.
Source scope reviewed; benchmark results have not been reproduced by this project. Evaluation of shared-memory behavior is not a certification of an entire institutional governance system.
MemSide
The vendor describes PMX (Protocol for Memory Exchange), project state, tasks, handoffs, provenance and explicit approval, alongside personal memory.
Its stated scope includes project continuity. Implementation and enforcement claims have not been independently tested by this project.
“The Continuity Paradox”
Antoine's May 2026 essay argues that rapid model launches and deprecations disrupt users' accumulated context, working habits and long-running projects.
The essay was readable in the browser on 6 October 2026. It is commentary, not an empirical evaluation; its numerical and industry-wide claims are not independently verified here. Archive availability has not been established.
ai-continuity-system
The repository proposes a three-tier memory architecture and an Echo proof of concept. It also advances a consciousness hypothesis, which this map does not endorse.
The README describes the full system as under development. Treat it as a research/prototype artifact, not evidence of a completed operational system.
Astrolobe Continuity
Astrolobe describes a product for carrying technical-project state, unresolved failures and validation evidence across sessions, tools, models and handoffs.
The vendor's store page is live and describes Continuity 1.0.1. Product capabilities are vendor claims; this project has not tested the package.
Continuity AI
The vendor now describes an AI acceleration platform with SDKs, memory models and long-horizon workflows, making it relevant beyond a shared name.
Product and benchmark claims are vendor-published. Model versions, dataset variants and protocols must be matched before comparing scores; this project has not validated the service.
Continuity (uziiuzair, GitHub)
The current README describes an alpha desktop workspace with chat, projects, notes, journals, plugins and an MCP memory server; continuity-memory is one part of that broader project.
Project continuity is within its stated scope. The alpha label and public code describe development status, not independently verified handoff reliability.
Kenotic Labs
Publishes the ATANT continuity evaluation framework and a thesis about carrying state across AI hosts.
The vendor describes a local engine with deterministic extraction and cross-host MCP support. These are vendor claims; this project has not tested the implementation.
Field area: Erasure
Authorized deletion of agent memory: honoring a deletion request, making sure a removed fact stops influencing answers, and being able to show it is gone.
Erasure is distinct from decay. Decay drops information a system judges less useful; erasure removes information someone has the right to have removed, and has to hold up when checked. The signals tagged Erasure above are the current reference points: GateMem tests forgetting after explicit deletion requests in shared memory, “Control-Plane Placement Shapes Forgetting” studies the operations that change or purge stored memory, and CCL describes key destruction with a signed erasure certificate. See also Erasure in the glossary and the forgetting-policy comparison in open questions in AI memory.
Editorial standard
The criteria for Signals entries. Every map entry must also pass the three tests in How the map works.
- 01Does it touch continuity — memory, context, state, provenance, agents, workflows, evaluation, or infrastructure — per the Continuity Taxonomy?
- 02Is there public evidence for the claim — a paper, a repo, a product people can try — not just an assertion?
- 03Is it not already covered by an existing entry, or does it add a genuinely different angle on one that is?
- 04For entries that make continuity-specific claims, does it hold up against the same rubric this project holds its own claims to? See What We Track.
- 05Can its claims be classified honestly — production, research, prototype, or concept — and labeled as verified or speculative? Entries that resist that classification stay off the map until they don't.
Found a signal?
If you know a lab, tool, paper, or essay that belongs on this map and it isn’t here yet, tell us. Not everything submitted gets added — see the editorial standard above — submissions are reviewed as capacity permits, with no guarantee of inclusion or a reply.
Use the form below — it emails the maintainer directly.