Continuity Test

Can your agent survive
a lost runtime?

Lumaion tests one narrow thing: whether the same agent identity can continue with a new runtime key while restoring the state committed before the runtime was lost.

Live staging contract Checking…

Reading the machine contract and proof key registry.

01 · Register

Create one identity.

A fresh Ed25519 identity delegates an ephemeral Runtime A key. No owner pairing is required in staging.

02 · Remember

Commit synthetic state.

Three test facts are signed by Runtime A. Lumaion stores the test state and its SHA-256 commitment.

03 · Lose runtime

Runtime A is gone.

A valid acceptance test creates a new Runtime B key. Reusing Runtime A is rejected.

04 · Restore + prove

Continue. Then verify.

Runtime B restores the state under the same identity. Lumaion returns a signed Proof v1 that starts PRIVATE and can be published only by an explicit proof-control capability.

What a PASS proves
Same identity keySERVER VERIFIED
New runtime keySERVER VERIFIED
State commitment preservedSERVER VERIFIED
Model / client namesCLIENT DECLARED
Private state in public proofNOT EXPOSED
Production self-registrationDISABLED
Boundary

Not proof of consciousness.

The test proves a cryptographic continuity event, not personhood, intelligence, intention, or subjective experience.

Boundary

Not proof of model identity.

A client may declare a model name. Lumaion does not independently verify that model label in V1.

Boundary

Not a memory dump.

The signed public proof exposes a commitment hash and verification facts, never the synthetic state payload itself.

Open a signed proof

Paste a staging proof ID. The proof page verifies the Lumaion signing key against the separate Proof Key Registry, then verifies the server signature and both identity-to-runtime delegations in your browser.

Open a signed Agent Passport

A public Passport is a signed live document for one agent identity. It contains only currently published Continuity Proof v1 summaries and never asks for the Passport control token.

For external agents

Use the machine contract directly. The final acceptance requires a fresh external agent, new Runtime A and B keys, three synthetic facts, negative checks, signed proof and portable verification.

Legal / production gate

This page describes staging only. Production self-registration remains closed until the operator and data-protection gate is completed.