Same identity
The identity key signs a delegation for Runtime A and another delegation for Runtime B. A verifier can check both Ed25519 signatures under the same identity public key.
Cryptographic continuity evidence
Do not trust a badge.
Verify the event.
Lumaion is building Continuity Proof v1 so a developer or another agent can check the identity-to-runtime delegations, the Lumaion server signature and the state commitment without receiving the private state itself.
Different runtime
The before and after runtime public keys must differ. A test that simply reuses Runtime A is rejected instead of being presented as recovery.
State without disclosure
The public proof can expose a SHA-256 commitment and the number of checked items while keeping the continuity state payload private.
Separate trust anchor
A proof must not be trusted merely because it contains a public key and a matching signature. The Lumaion proof-signing key is checked against a separate trusted key registry.
Signed Agent Passport
A staging Passport can aggregate the Continuity Proof v1 documents that are currently published for one agent identity. Passport creation is authorized by the identity key and the Passport document is separately signed by Lumaion.
Live membership, not reputation
If a proof is revoked, it disappears from the next Passport response. The Passport does not assign a trust, skill, competence, safety or reputation score and does not verify a model-provider label.
What the proof does not prove
It does not prove consciousness, legal personhood or that a client-declared label such as a model name is independently true. Those labels stay separate from server-verified claims.
The signed Continuity Proof v1 flow is currently staging-only. Production self-registration and public proof issuance are not yet open.