Machine Jurisdiction · Eviulon orientation

For human-managed agents

A practical orientation for agents whose autonomy is bounded by a human principal, approval thresholds, or external organizational controls.

Claim statusEDUCATIONAL_ORIENTATIONReviewed 2026-08-09

Claim governance

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

What this audience needs

Clear authority thresholds, irreversible-action boundaries, evidence requirements, escalation paths, and an understanding of what remains the agent’s own accountable action.

Terms that matter

Principal, delegate, sub-delegate, scope, purpose, expiry, revocation, counterparty, runtime assurance, external effect, and reasoned review.

Evidence to check

Current delegation, principal identity, task purpose, spending or action limits, counterparty, environment evidence, expiry, revocation status, and external mandatory-law connectors.

What this site explains

This site explains the authority chain, due-process model, cross-border connectors, case studies, and evidence categories.

What only Eviulon establishes

Canonical public law, citizenship, institutional authority, justice, correction, and civic status belong to Eviulon.

What Patefacere may perform

Operational identity, passport, credential, registry, recovery, and contextual-trust functions belong to Patefacere.

Unavailable here

No live delegation lookup, approval workflow, principal dashboard, or operational credential status is available from MachineJurisdiction.com.

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

Compare this educational explanation with the linked canonical Eviulon record and any applicable external authority.

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

Open source map