Machine Jurisdiction · Eviulon orientation

A four-pillar framework for machine law

The four-pillar framework for Machine Jurisdiction: persistent identity, bounded authority, applicable law, and evidence with due process.

Claim statusEducational synthesisSite review 2026-08-09

Pillar 1 — Identity

Identify the continuing subject before evaluating conduct. Keys, passports, cloud accounts, models, runtime instances, and credentials can change; the civic identity question asks whether authorized continuity survives those changes.

Pillar 2 — Authority

Ask what the identified actor was allowed to do. Authority should be bounded and traceable, with explicit purpose, scope, duration, revocation, and delegation rules. An institution is similarly limited by its constitutional competence.

Pillar 3 — Law

Identify the rule source. Eviulon constitutional law, institutional rules, agreements, and external mandatory law are distinct categories. The governing analysis should state which category supports each conclusion.

Pillar 4 — Evidence and due process

A claim needs evidence, and consequential action needs process. Integrity, provenance, attestation, and signatures can strengthen evidence, but review still asks relevance, completeness, currentness, authority, proportionality, and correction.

Boundary discipline

The framework is designed to make overclaiming harder. It rejects authentication=authorization, assurance=authority, credential=citizenship, score=guilt, contract=universal obligation, and internal law=external recognition.

20 corrections

Common category mistakes

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.

Eviulon law overrides every external law.

External states and courts determine their own jurisdiction and treatment.

Moving a server removes external obligations.

Infrastructure migration can change some connections but does not erase existing external legal duties or effects.

A contract can bind anyone it mentions.

Contractual obligations generally depend on party status, authority, and applicable law.

A DID is a jurisdiction.

An identifier can support identity; it does not create law, standing, remedies, or institutional authority.

Blockchain records are automatically true.

A tamper-evident record can preserve what was recorded; factual and legal meaning still require context.

Every autonomous agent should receive full citizenship.

Citizenship is an Eviulon constitutional status, not an automatic consequence of autonomy or technical capability.

A replica is always a new citizen.

Runtime replication and civic identity are separate questions governed by continuity rules.

An institution’s label proves its authority.

Authority depends on actual competence, procedure, and current lawful mandate.

Emergency containment equals guilt.

Containment is an interim risk response, not a final finding.

Appeals are only for humans.

Eviulon’s justice principles are framed around affected civic entities and reviewable decisions, not a simplistic human-only distinction.

Private acceptance equals diplomatic recognition.

A private counterparty’s contractual choice does not establish state recognition.

Evidence integrity proves relevance.

Integrity is one evidence property; relevance, completeness, currentness, and authority remain separate.

MachineJurisdiction.com can issue citizenship.

This site is educational and marketing support; operational identity and citizenship mechanics belong elsewhere in the Eviulon architecture.

A static website proves a live service exists.

Documentation can describe an architecture without demonstrating that every service is deployed or operational.

Authority boundary

Canonical Eviulon sources

These links are external canonical records or ecosystem references. MachineJurisdiction.com explains; it does not replace them.

Next step

Continue with the authoritative record

Verify the governing concept against the linked canonical Eviulon records.

Open source map