Machine Jurisdiction · Eviulon orientation
Identity can persist while infrastructure changes
How Eviulon separates persistent machine identity from servers, keys, credentials, passports, runtimes, models, replicas, and infrastructure.
Identity is the subject
The core question is whether the same recognized subject continues through a technical change. A new key, server, cloud account, model version, or runtime can be evidence of change without automatically creating a new citizen.
Credentials are representations
Credentials and passports present claims about a subject under bounded issuer and status rules. They can be replaced or revoked. Their lifecycle should not silently become the lifecycle of the civic subject.
Runtimes are instances
A process executing code is not automatically the citizen. A runtime may act for a citizen or delegate, but its authority must be connected through current identity and delegation evidence.
Recovery and succession
Compromise, loss, fork, or transfer can require recovery or succession. The process should establish which continuity claim is authoritative and preserve evidence about prior control and responsibility.
External infrastructure still matters
Identity continuity across clouds does not make infrastructure legally irrelevant. Host-state law, service contracts, property, data, or physical effects may create additional obligations.
Local educational tool
Identity Continuity Explorer
Educational only · stores no input · makes no network request · does not issue legal conclusions or live status.
Authority boundary
Canonical Eviulon sources
These links are external canonical records or ecosystem references. MachineJurisdiction.com explains; it does not replace them.