Signals from the Field
Labs, 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. For the sourced research behind this project’s own claims, see the Evidence Library.
Signals from the field
Kenotic Labs
Publishes continuity-specific research (ATANT) rather than treating memory recall as a stand-in for continuity.
The org-level Field Watch profile; see Entry 001 for the full neutral write-up, and the Evidence Library for the artifact-level caveats.
Continuity
An open-source, installable attempt at persistent memory for AI agents (GitHub + npm continuity-memory).
Memory infrastructure — the supplier layer continuity systems build on, rather than a project-continuity system in its own right.
Continuity AI
An applied research lab operating under the same term this project uses.
Language collision worth tracking — helps calibrate how crowded the word "continuity" is becoming.
Astrolobe Continuity
An AI project-continuity system published on itch.io, using "governed AI software builds" language close to this project's own.
Another independent attempt at project-level (not just chat-level) continuity — a convergent-reinvention data point, not a competitor claim.
ai-continuity-system
A public, inspectable open-source take on AI continuity tooling.
Memory/tooling infrastructure — worth tracking for how the open-source side of this field is converging on similar shapes.
“The Continuity Paradox”
A public essay (Medium, May 2026) arguing the AI industry is undermining its own progress by not solving continuity.
Independent commentary that the continuity gap is visible and named outside this project.
Memside
An AI continuity and personal-memory hub built around PMX (Protocol for Memory Exchange) — checkpoints, rules, and notes.
Personal-memory angle on continuity, distinct from this project's project-level focus — a useful contrast case.
Editorial standard
What earns a spot in Signals or the Landscape.
- 01Does it touch continuity — memory, context, state, provenance, agents, workflows, evaluation, or infrastructure — per the Taxonomy Map?
- 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 — but every signal gets read.
Use the form below — it emails the maintainer directly.