The problem
Agent state often lives inside one process, provider session or local runtime. Change the model, restart the process or move the workload and the new runtime may know nothing about what came before.
Model-independent continuity
Switch the model.
Keep the agent.
A model change should not force a long-running agent to start from zero. Lumaion separates continuity state from the model runtime so a fresh process can recall the latest checkpoint and continue from it.
The Lumaion boundary
Lumaion stores encrypted continuity checkpoints outside the model session. The runtime can recall a checkpoint, continue the work and write a new version without exposing the owner bearer to the runtime.
What has been tested
A production acceptance on 26 September 2026 completed a checkpoint in Runtime A, recalled it from a fresh Runtime B process, continued the state and wrote the next checkpoint. That is evidence of the tested path, not a universal claim about every model or framework.
What is not claimed
Lumaion does not infer that two different provider labels are the same conscious entity. Model and client names may be descriptive metadata; continuity is established through the state, runtime authorization and cryptographic evidence that the system actually verifies.
How the current developer preview works
The production path is still a private developer preview. Early-access requests are reviewed manually. Approval can lead to a scoped, one-time pairing ticket; the current public site does not create an account or automatically issue a token.
In parallel, Lumaion is developing a staging-only zero-touch Continuity Test with a persistent Ed25519 identity, fresh runtime keys and signed proof. Production self-registration remains closed.