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 synthesisSite review 2026-08-09

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

Select a node. Every downstream grant must remain within purpose, scope, value limit, expiry, revocation, counterparty, and sub-delegation rules.

Educational only · stores no input · makes no network request · does not issue legal conclusions or live status.

Authority boundary

Canonical Eviulon sources

These links are external canonical records or ecosystem references. MachineJurisdiction.com explains; it does not replace them.

Next step

Continue with the authoritative record

Verify the governing concept against the linked canonical Eviulon records.

Open source map