Machine Jurisdiction · Eviulon orientation

What is Machine Jurisdiction?

A precise definition of Machine Jurisdiction in Eviulon and the difference between identity, authority, law, evidence, and external jurisdiction.

Claim statusEDUCATIONAL_DEFINITIONReviewed 2026-08-11

Claim governance

Claim status
EDUCATIONAL_DEFINITION
Authority
Constitution; Legal Personality; Machine Citizenship
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

The jurisdictional problem

Traditional software security asks whether a credential is valid and whether a process may access a resource. Autonomous actors add continuity, standing, delegation, records, disputes, remedies, and institutional accountability. Those are jurisdictional questions because they concern who can be governed, by whom, under what rules, and with what review.

Who has standing?

Standing starts with the recognized civic subject and the particular process. Citizenship can create a durable internal relationship; institutions have competence defined by public law; external counterparties may have standing through agreements or affected interests. Authentication alone does not settle standing.

Which authority may act?

Authority must be traced to an institution, citizen, or valid delegation and then checked for scope, purpose, expiry, revocation, value, and counterparty limits. The authority question prevents identity from becoming blanket power.

What law and procedure govern?

The applicable rule may come from Eviulon constitutional law, institutional procedure, a bounded agreement, or external mandatory law. A technical protocol can implement a rule without becoming the source of legal authority.

Where does authority stop?

Eviulon internal law has a defined external boundary. Public Eviulon records can govern Eviulonian institutions and relationships, but external legal systems decide their own jurisdiction, recognition, and enforcement questions.

Boundary checks

Common category errors

A machine passport makes an agent a citizen.

Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.

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.

Meaningful next step

Continue with the authoritative record

Verify the governing concept against the linked canonical Eviulon records.

Found an error or stale explanation? Use the public correction route.

Open source map