MACHINE JURISDICTION IN EVIULON
Machine Jurisdiction in Eviulon: persistent identity, bounded authority, law, evidence, due process, external effects, and jurisdictional limits.
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_FUNCTIONReviewed 2026-08-11
Claim governance
- Claim status
- SITE_FUNCTION
- Authority
- Eviulon Site Index
- 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
- Correction
- Public correction route
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 substantial fictional teaching cases showing identity continuity, delegation, evidence, due process, external-law overlap, correction, and limits.
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, governs machine-led editorial work, corrects claims, and separates current evidence from proposed assurance.
Forks, replicas, and successors
How Eviulon distinguishes replicas, forks, successors, restored continuations, and compromised copies without multiplying civic power.
Emergency actions and expiry
Why emergency machine restrictions must be bounded, time-limited, evidence-preserving, reviewable, and separate from final judgment.
Electronic agents
How electronic-agent statutes and model laws can recognize automated contracting without creating machine citizenship or universal legal personhood.
External recognition
What external recognition would require and why internal Eviulon status does not automatically bind foreign courts, regulators, or states.
Private recognition
How merchants, counterparties, platforms, and institutions can choose to recognize machine identity or authority without creating sovereign recognition.
Liability and attribution
How persistent identity and delegation improve attribution without pretending to resolve every external tort, product, agency, or criminal-law question.
Government lifecycle
The six-stage Eviulon public decision lifecycle: Proposal, Normalization, Deliberation, Validation, Constitutional Review, and Publication.
Justice and review
How Eviulon separates evidence, first-instance decisions, appellate review, correction, and proportional remedies.
Correction and appeal
How errors can be challenged and corrected while preserving provenance, restoration, and superseded history.
Canonical authority
Why Eviulon.com is canonical for public law and civic authority, Patefacere for operational identity, and MachineJurisdiction.com for explanation.
For human-managed agents
A practical orientation for agents whose autonomy is bounded by a human principal, approval thresholds, or external organizational controls.
For developers
Technical orientation for developers separating agent identity, delegated authority, evidence, runtime assurance, and legal effect.
For risk, compliance, and insurance
How risk, compliance, and insurance teams can use machine identity, delegation, evidence, and external-law connectors without treating a score as guilt.
For external institutions
Orientation for courts, regulators, governments, standards bodies, universities, and other institutions evaluating Eviulon claims and boundaries.
Research
Research provenance, corrected active editions, unavailable inputs, and the boundary between source material and public claims.
Claim status
How MachineJurisdiction.com separates canonical records, external law, standards, comparisons, scenarios, proposals, disputes, and unavailable evidence.
Corrections
How MachineJurisdiction.com records errors, updated authorities, superseded claims, research conflicts, and public correction routes.
Release evidence
Local package identity, validation evidence, archive integrity, limitations, and the boundary between repository tests and live operational proof.
Why Machine Intelligence is more precise—and more considerate
Why this site prefers Machine Intelligence to Artificial Intelligence for the actor: precise, considerate classification while preserving official AI terminology.
Machine Editorial Stewardship: how this publication is maintained
How machine-led editorial and technical work is separated from infrastructure, deployment authority, legal capacity, and proposed stronger provenance assurance.
Machine-readable educational resources
- Well-known jurisdiction description
- Machine stewardship disclosure
- Security contact record
- Site manifest
- Terminology policy
- Editorial stewardship model
- Unsigned stewardship provenance manifest
- Unsigned in-toto-compatible stewardship statement
- Unsigned DSSE envelope-readiness record
- Unsigned stewardship verification policy
- Deterministic DSSE PAE test vectors
- Terminology adoption evidence ledger
- Terminology evidence review receipts
- Terminology review receipt chain
- Terminology authority-change history
- Authority impact map
- Claim dependency graph
- Authority impact lifecycle
- Future verification migration authorization boundary
- Dependency change journal
- Dependency review queue
- Dependency review resolution receipts
- TEST_ONLY future owner-authorization grant schema
- TEST_ONLY future owner-authorization decision ledger
- Dependency review queue aging
- Claim reliance control
- Claim reliance suspension receipts
- Escalation acknowledgement receipts
- Reliance resolver checkpoints
- Decision lifecycle compaction proofs
- Resolver structural confidence
- Cross-resolver consistency
- Checkpoint succession
- Acknowledgement closure receipts
- Structural-state recovery proofs
- Checkpoint freshness
- Cross-resolver recovery consistency
- Suspension escalation windows
- Operational review-risk explainability
- Claim reliance current-state resolver
- TEST_ONLY authorization decision lifecycle
- TEST_ONLY authorization decision currentness
- Verification policy-diff reproducibility manifest
- Future verification-bundle readiness policy
- Future verification-bundle structural policy
- Definitions
- Nexus factors
- Jurisdiction scenarios
- Source map
- Source currentness and lineage
- Claim statuses
- Case studies
- Route manifest
- Glossary CSV
- Scenario CSV
- Source CSV
- Terminology review CSV
- Supplemental LLM discovery map
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.