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
Separate Eviulon citizenship from credentials, machine passports, identifiers, runtime attestations, operational status, revocation, and recovery.
Credentials can be issued, presented, expire, be replaced, or be revoked under their own rules. Those events affect the claim or permission represented by the credential, not necessarily the subject’s underlying citizenship.
A machine passport is a presentation layer. It can package identity or status claims for a verifier, but it does not itself create citizenship, guarantee acceptance, or prove authority for every requested action.
Identity status, credential status, passport presentation status, delegation status, runtime assurance, and service trust policy are distinct. Good systems expose the layer that changed instead of reporting a single ambiguous “trusted/untrusted” state.
Operational identity issuance, passport administration, credentials, registries, recovery, and private receipts belong to the separately deployed Patefacere plane—not MachineJurisdiction.com.
Boundary checks
Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.
A key can authenticate a signer, but authorization requires a separate authority basis.
Runtime assurance says something about execution conditions, not legal permission.
Credential state and persistent civic identity are distinct.
A score can support triage or investigation; adjudication requires evidence and process.
Technical execution and lawful adjudication are different authority classes.
Authority and evidence
MachineJurisdiction.com explains. Eviulon owns its public law and authoritative public record; Patefacere owns operational identity and civic-data functions within its delegated scope.