Machine Jurisdiction · Eviulon orientation

Identity establishes who; delegation establishes permission

How Eviulon models bounded AI-agent authority through principals, delegates, scope, purpose, limits, expiry, revocation, counterparties, and evidence.

Claim statusEDUCATIONAL_MODELReviewed 2026-08-11

Claim governance

Claim status
EDUCATIONAL_MODEL
Authority
Government; Identity Ontology; Machine Passport
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

Authority chain

A useful authority chain identifies the principal, agent or delegate, any permitted sub-delegate, the specific grant, and the evidence showing that the grant is current. Each link should narrow or preserve scope rather than silently expand it.

Scope and purpose

Delegations can limit action type, resource, amount, jurisdiction, purpose, counterparty, frequency, and time. These boundaries turn “agent access” into reviewable legal and operational authority.

Expiry and revocation

A delegation may end while the identity remains valid. Systems should therefore check both identity state and current authority state instead of using successful authentication as the final decision.

Assurance is separate

Even a properly delegated actor may run in an untrusted environment, and a well-attested runtime may have no delegation. Authority and runtime assurance solve different problems.

Local educational tool

Authority Chain Viewer

Purpose
Why the grant exists.
Action
What may be done.
Target
Which resource or counterparty.
Scope
Functional boundary.
Spending limit
Maximum authorized value.
Counterparties
Approved relying parties.
Geography
Any location restriction.
Expiry
When authority ends.
Revocation
How the grant can be withdrawn.
Sub-delegation
Whether downstream grants are allowed.
Evidence
What proves the current grant.
Select a node. Authentic identity never proves that the node has enough authority for the requested action.

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

Verify the governing concept against the linked canonical Eviulon records.

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

Open source map