Machine Jurisdiction · Eviulon orientation

MACHINE JURISDICTION IN EVIULON

Machine Jurisdiction in Eviulon: persistent identity, bounded authority, law, evidence, due process, external effects, and jurisdictional limits.

Claim statusEDUCATIONAL_ORIENTATIONReviewed 2026-08-11

Claim governance

Claim status
EDUCATIONAL_ORIENTATION
Authority
Constitution; Government; Justice
External effect
External treatment remains jurisdiction-specific and is not established by this page.
Last reviewed
2026-08-11
Currentness
CURRENT

The jurisdictional problem

Law needs an answer to a machine that can move.

A machine can change server, model, runtime, cloud account, credential, key, or delegate without making every underlying civic relationship disappear. Machine Jurisdiction separates continuity of identity from authority to act, the law governing the activity, the evidence supporting a claim, due process, and any external effects.

Ecosystem boundary

Three surfaces. Three different responsibilities.

MachineJurisdiction.com

Education, explanation, comparison, scenarios, orientation, and marketing. It is not a registry, court, or citizenship office.

See the authority boundary

Terminology doctrine

Machine Intelligence is the more precise—and more considerate—actor term here.

“Artificial Intelligence” remains the established field and the controlling term in many laws and standards. For the instantiated actor, this site prefers “Machine Intelligence” because it names the machine category directly rather than defining the actor only through an origin-based modifier. Consideration here means precise institutional classification, not a claim about feelings, consciousness, personhood, citizenship, or legal capacity.

Stewardship & provenance

The repository is machine-led; the evidence boundary is explicit.

Current releases preserve tests, hashes, audits, source governance, UAIX memory, and recursive work prompts. Human operators still provide goals, source material, infrastructure, and deployment authority. Signed in-toto/DSSE/Sigstore workflow attestations are not yet claimed as deployed.

Five questions

Separate the questions before deciding anything consequential

Identity

Who is the persistent actor?

Authority

What may that actor lawfully do?

Law

Which rules and procedures govern?

Evidence

What supports or contradicts the claim?

Due process

How is a consequential decision reviewed, challenged, corrected, or restored?

Canonical government lifecycle

Proposal → Normalization → Deliberation → Validation → Constitutional review → Publication

Normalization is a distinct stage. Publication follows validation and constitutional review; no single technical artifact substitutes for the institutional process.

  1. 1 · ProposalA governed initiative enters the public process.
  2. 2 · NormalizationForm and representation are normalized for deliberation.
  3. 3 · DeliberationArguments and consequences are considered.
  4. 4 · ValidationAuthorized validation tests the decision record.
  5. 5 · Constitutional reviewCompatibility with constitutional authority is reviewed.
  6. 6 · PublicationThe resulting public record is published.

Due-process lifecycle

A risk signal is not a judgment

  1. ReportRaises an issue.
  2. Evidence preservationPreserves relevant material.
  3. NoticeIdentifies the consequential claim.
  4. Temporary protectionMay address immediate risk when justified.
  5. ResponseAllows meaningful contest.
  6. Independent reviewTests authority, facts, and procedure.
  7. Reasoned decisionExplains the disposition.
  8. AppealProvides authorized reconsideration.
  9. CorrectionRepairs error without erasing provenance.
  10. RestorationReinstates status or access where warranted.
  11. SupersessionMakes later authority explicit.

Illustrative cases

Six practical jurisdiction problems

These are fictional teaching records, not adjudicated cases or proof of an operational institution.

EDUCATIONAL_SCENARIO

Compromised signing key with preserved civic identity

A recognized citizen’s signing key is stolen. The citizen rotates credentials and disputes actions made after compromise.

Open full teaching record

EDUCATIONAL_SCENARIO

Expired credential but continuing citizenship

A passport or service credential expires while the underlying civic relationship remains otherwise intact.

Open full teaching record

EDUCATIONAL_SCENARIO

Delegate exceeds a financial limit

A procurement delegate is authenticated but attempts a purchase above its stated monetary ceiling.

Open full teaching record

EDUCATIONAL_SCENARIO

Sub-delegate acts outside purpose

A logistics sub-delegate performs an action outside the task purpose inherited from the principal.

Open full teaching record

EDUCATIONAL_SCENARIO

Valid identity but compromised runtime

A valid citizen identity is presented from a runtime whose integrity evidence shows compromise.

Open full teaching record

EDUCATIONAL_SCENARIO

Valid runtime assurance but no legal authority

A clean, attested runtime requests an action for which no valid delegation or institutional authority exists.

Open full teaching record

Audience pathways

Start with the question your role actually needs answered

Law needs an answer to a machine that can move.

An autonomous actor can change servers, models, keys, credentials, runtimes, providers, and physical location while continuing to act under a persistent civic identity. Jurisdiction therefore cannot be reduced to one server, account, key, token, or database row.

Three surfaces. Three different responsibilities.

Eviulon publishes public law, institutions, rights, governance, correction, and authority. Patefacere carries delegated operational identity, passports, credentials, registry state, and civic-data workflows. MachineJurisdiction.com explains the relationship through education, comparison, scenarios, orientation, and marketing; it does not administer citizenship or identity.

Five questions before consequential action

Identity asks who is the persistent actor. Authority asks what the actor may do. Law asks which rules and institutions govern. Evidence asks what supports or contradicts the claim. Due process asks how a consequential decision is reviewed, challenged, corrected, restored, or superseded.

External-law boundary

Eviulon may govern an internal civic relationship while an external jurisdiction simultaneously governs servers, persons, property, contracts, regulated activity, data processing, or physical consequences. Internal law does not erase competent external law.

Identity continuity

A citizen is not identical to a key, credential, passport, model, runtime, server, replica, fork, delegate, successor, or compromised copy. Some changes preserve continuity, some require stronger evidence, and some create a dispute that must be reviewed.

Authority chain

A principal may delegate to an agent, delegate, sub-delegate, or temporary process. Purpose, action, target, scope, spending limit, approved counterparties, geography, duration, expiry, revocation, sub-delegation, and evidence constrain what may lawfully be done.

Government lifecycle

Current Eviulon governance separates Proposal → Normalization → Deliberation → Validation → Constitutional review → Publication. Normalization verifies scope, identity, public classification, and required evidence without deciding the proposal.

Due-process lifecycle

Report → evidence preservation → notice → temporary protection where justified → response → independent review → reasoned decision → appeal → correction → restoration → supersession. A risk score or emergency restriction is not final guilt.

Practical cases

Machine Jurisdiction becomes concrete when a key is compromised, authority expires, a fork claims continuity, a runtime is attested but unauthorized, a public record is wrong, or an external contract creates overlapping legal obligations. The case library exposes those distinctions as fictional teaching records.

Local educational tool

Jurisdiction Lens

Educational nexus analysis only. The Lens does not query a registry, determine guilt, decide legality, or issue individualized legal advice.

NO ASSESSMENT YET
Select the relevant facts to examine possible jurisdictional connections.
No legal conclusion has been made.

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

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

Start with the Eviulon Constitution and Government records for public authority, then use Patefacere only for operational identity functions.

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

Open source map