SOURCE-LINKED INTELLIGENCE
Runtime-Independent Persistent Agents: Preserving Identity, Memory, and Code Across Models, Harnesses, and Servers
arXiv · AI, language, vision and robotics · article · Sep 1, 2026 · UTC
Long-lived AI agents may replace their models, orchestration harnesses, interaction surfaces and hosts while retaining identity, memory and executable body lineage. We present a runtime-independent architecture that separates a continuity-bearing substrate $P_t=(I_t,M_t,B_t)$ from replaceable execution and interaction bindings. Six continuity invariants and a quiesce--checkpoint--validate--bind--rehydrate--resume protocol govern state preservation, capability changes and continuation authority. Enoch implements the design through a reusable software body, private installed state, provider cont
Read original source ↗ Open in workspace
- recordType
- paper
- region
- Global
Evidence & attribution
First collected: 2026-09-21T06:21:59.299Z. This is not the publication date.
Observed changes
AIIC observation times, not verified publisher revision times. Up to eight recent revisions.
2026-09-26T15:52:06.847Z
- summary:
Agent systems are commonly described by the model and harness that currently produce their behavior. That boundary is useful for one execution but underspecifies a long-lived agent that may change models, orchestration harnesses, interaction sessions, and host servers while retaining one identity, memory, and executable code lineage. We present a runtime-independent architecture for persistent agents. A continuity-bearing substrate $P_t=(I_t,M_t,B_t)$ contains an architectural identity representation, private durable memory, and a versioned software body. A replaceable deployment binding compr → Long-lived AI agents may replace their models, orchestration harnesses, interaction surfaces and hosts while retaining identity, memory and executable body lineage. We present a runtime-independent architecture that separates a continuity-bearing substrate $P_t=(I_t,M_t,B_t)$ from replaceable execution and interaction bindings. Six continuity invariants and a quiesce--checkpoint--validate--bind--rehydrate--resume protocol govern state preservation, capability changes and continuation authority. Enoch implements the design through a reusable software body, private installed state, provider cont