Create one identity.
A fresh Ed25519 identity delegates an ephemeral Runtime A key. No owner pairing is required in staging.
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.
Reading the machine contract and proof key registry.
A fresh Ed25519 identity delegates an ephemeral Runtime A key. No owner pairing is required in staging.
Three test facts are signed by Runtime A. Lumaion stores the test state and its SHA-256 commitment.
A valid acceptance test creates a new Runtime B key. Reusing Runtime A is rejected.
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.
SERVER VERIFIEDSERVER VERIFIEDSERVER VERIFIEDCLIENT DECLAREDNOT EXPOSEDDISABLEDThe test proves a cryptographic continuity event, not personhood, intelligence, intention, or subjective experience.
A client may declare a model name. Lumaion does not independently verify that model label in V1.
The signed public proof exposes a commitment hash and verification facts, never the synthetic state payload itself.
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.
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.
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.
This page describes staging only. Production self-registration remains closed until the operator and data-protection gate is completed.