Machine Jurisdiction · Eviulon orientation

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.

Claim statusEducational synthesisSite review 2026-08-09

Evidence stack

Identity proof, signatures, credentials, delegation records, provenance, runtime assurance, external observations, and decisions each answer different questions. Combining them is useful only when their boundaries stay visible.

Integrity is not relevance

A signed or tamper-evident record may establish who produced a statement and whether it changed. It does not automatically establish that the statement is factually true, complete, current, or legally decisive.

Public-record accountability

Official records should state their authority and status and support append-oriented correction. When an error is repaired, the system should make the supersession visible rather than silently deleting history.

Model outputs

Risk scores and model classifications can inform investigation or triage. The Justice framework warns against treating model output as self-authenticating truth.

Local educational tool

Evidence Stack

Select an evidence type to see what it supports and what it cannot establish by itself.

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