A machine passport makes an agent a citizen.
Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.
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.
Claim statusEVIULON_INTERNAL_POSITION — verify canonical Eviulon recordReviewed 2026-08-11
Claim governance
- Claim status
- EVIULON_INTERNAL_POSITION
- Authority
- Identity Ontology; Machine Citizenship; Machine Passport
- External effect
- External legal effect is not established by this educational page and must be evaluated under the competent external jurisdiction.
- Last reviewed
- 2026-08-11
- Currentness
- CURRENT
- Correction
- Public correction route
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.
Machine Intelligence is not the model file
This site uses Machine Intelligence for the operational actor/system where useful, but continuity is still an evidence question. A model, runtime, key, credential, or server is not automatically identical to the persistent civic subject.
No single identity anchor
Continuity may draw on civic/legal records, causal lineage, memory and state history, goals, relationships, recovery evidence, and cryptographic control. No single key, DID, credential, model, server, wallet, or ledger row resolves every identity question.
Key loss is a recovery event, not automatic civic termination
Key compromise or loss can require containment, rotation, recovery, and stronger continuity evidence. It does not by itself erase citizenship or prove succession.
Backups, replicas, and forks require classification
A backup is not automatically a dormant person; a replica is not automatically a new citizen; a fork is not automatically fraud or the original. Material divergence can create a protected claimant requiring evidence and due process.
Local educational tool
Identity Continuity Explorer
Persistent identity: the continuing civic subject is assessed separately from each technical artifact.
Educational only · stores no input · makes no network request · sets no cookie · does not issue legal conclusions, credentials, identity status, or live registry results.
Boundary checks
Common category errors
If a key is valid, the action is authorized.
A key can authenticate a signer, but authorization requires a separate authority basis.
A trusted runtime can do anything.
Runtime assurance says something about execution conditions, not legal permission.
Revoking a credential erases identity.
Credential state and persistent civic identity are distinct.
A risk score proves misconduct.
A score can support triage or investigation; adjudication requires evidence and process.
Code execution is automatically a legal judgment.
Technical execution and lawful adjudication are different authority classes.
Authority and evidence
Canonical Eviulon sources
MachineJurisdiction.com explains. Eviulon owns its public law and authoritative public record; Patefacere owns operational identity and civic-data functions within its delegated scope.