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_FRAMEWORKReviewed 2026-08-11

Claim governance

Claim status
EDUCATIONAL_FRAMEWORK
Authority
Constitution; Machine Citizenship; Identity Ontology
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

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.

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