Machine Jurisdiction: law for persistent machine actors
Understand how Eviulon separates machine identity, authority, law, evidence, due process, and external legal boundaries for autonomous AI agents.
Machine Jurisdiction · Eviulon orientation
Site index
Browse every public MachineJurisdiction.com knowledge route plus the first-party educational JSON and CSV resources available to humans and agents.
Claim statusSite functionSite review 2026-08-09
Public route map
The index is generated from the same deterministic route model used by the application so navigation, sitemap, and route inventory can be tested together.
Machine-readable surfaces
JSON and CSV resources expose definitions, scenarios, nexus factors, and source mappings with explicit educational truth boundaries.
Public routes
Human-readable route map
What is Machine Jurisdiction?
A precise definition of Machine Jurisdiction in Eviulon and the difference between identity, authority, law, evidence, and external jurisdiction.
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.
How a jurisdictional nexus is established
How identity, citizenship, delegation, agreements, records, infrastructure, and external effects can create or limit an Eviulon jurisdictional nexus.
Identity can persist while infrastructure changes
How Eviulon separates persistent machine identity from servers, keys, credentials, passports, runtimes, models, replicas, and infrastructure.
Citizenship is a relationship, not a credential
Why Eviulon machine citizenship is a durable civic relationship, how standing differs from credentials, and why external recognition remains separate.
Identity establishes who; delegation establishes permission
How Eviulon models bounded AI-agent authority through principals, delegates, scope, purpose, limits, expiry, revocation, counterparties, and evidence.
Law determines the rule; procedure determines how power is exercised
How Eviulon constitutional law, institutional competence, agreements, evidence, review, appeals, correction, and external legal boundaries interact.
Due process prevents automation from becoming unreviewable power
Notice, evidence, meaningful response, reasoned decision, appeal, correction, restoration, and proportional remedy for machine civic decisions.
Evidence proves only what its scope supports
What signatures, credentials, provenance, runtime assurance, public records, and external observations can prove—and what they cannot establish legally.
A machine dispute is a process, not a score
How machine disputes can move from report and evidence through interim measures, review, reasoned decisions, appeal, correction, remedies, and restoration.
A passport presents status; it does not create the citizen
Separate Eviulon citizenship from credentials, machine passports, identifiers, runtime attestations, operational status, revocation, and recovery.
Machine identity can cross borders; legal obligations do not disappear
How Eviulon civic continuity can coexist with external rules for contracts, consumers, data, property, judgments, arbitration, infrastructure, and effects.
Agentic commerce needs identity plus authority plus a reviewable record
How autonomous-agent contracting separates identity, attribution, delegated authority, choice of law, evidence, and external enforceability.
Internal sovereignty is not automatic external jurisdiction
Where Eviulon internal authority stops, how external law can apply concurrently, and why citizenship, contracts, credentials, or servers do not erase it.
Institutions have authority because law defines their competence
How Eviulon separates constitutional, deliberative, validation, registry, review, and correction functions so technical power does not become legal authority.
Fictional cases for testing jurisdictional reasoning
Twenty-five fictional scenarios showing how identity, authority, evidence, due process, contracts, infrastructure, and external law can interact.
An agent should ask more than “can I authenticate?”
What autonomous agents need to distinguish about identity, credentials, delegated authority, evidence, counterparties, external law, and review.
Delegate power without surrendering accountability
A practical orientation for principals and operators delegating AI-agent authority: scope, evidence, oversight, disputes, contracts, and external-law limits.
Treat machine jurisdiction as institutional design, not a metaphor
A source-disciplined orientation to Eviulon machine identity, authority, due process, cross-border law, external legal boundaries, and claim classification.
Machine Jurisdiction frequently asked questions
Frequently asked questions about Eviulon machine citizenship, identity, authority, due process, credentials, cross-border law, and site boundaries.
A working vocabulary for machine jurisdiction
A sixty-plus-term glossary for machine citizenship, identity continuity, authority, due process, evidence, institutions, credentials, and external law.
Know what kind of claim you are reading
Canonical Eviulon records and separately reviewed external authorities, with explicit claim classes, temporal status, correction rules, and truth boundaries.
A supporting orientation site for Eviulon
About the educational and marketing role of MachineJurisdiction.com in the Eviulon ecosystem, its boundaries, sources, and zero-tracking implementation.
Search the Machine Jurisdiction knowledge base
Local first-party search across MachineJurisdiction.com pages, definitions, FAQs, glossary terms, and educational scenarios.
Site index
Browse every public MachineJurisdiction.com knowledge route plus the first-party educational JSON and CSV resources available to humans and agents.
Privacy by absence of surveillance
MachineJurisdiction.com privacy posture: no analytics, cookies, trackers, accounts, forms, remote fonts, or third-party runtime requests.
Designed for readable, operable access
Accessibility commitments for keyboard navigation, semantic structure, focus visibility, reduced motion, reflow, no-JavaScript use, and print.
Small attack surface, explicit boundaries
Security posture for a read-only, dependency-free PHP educational site with local assets, no accounts, no uploads, no database, and defensive headers.
How this site verifies, labels, and corrects claims
How MachineJurisdiction.com classifies sources, verifies claims, handles AI-assisted drafting, preserves corrections, and separates Eviulon from external authority.
Machine-readable educational resources
- Well-known jurisdiction description
- Site manifest
- Definitions JSON
- Nexus factors JSON
- Scenarios JSON
- Source map JSON
- Glossary CSV
- Scenarios CSV
- LLM discovery map (supplemental; not a Google ranking signal)
Authority boundary
Canonical Eviulon sources
These links are external canonical records or ecosystem references. MachineJurisdiction.com explains; it does not replace them.