Machine Jurisdiction · Eviulon orientation

Release evidence

Local package identity, validation evidence, archive integrity, limitations, and the boundary between repository tests and live operational proof.

Claim statusSITE_FUNCTIONReviewed 2026-08-09

Claim status: SITE_FUNCTION
Authority: Technical Status
External effect: External treatment remains jurisdiction-specific and is not established by this page.
Last reviewed: 2026-08-09
Currentness: CURRENT
Correction: Public correction route

What local tests can prove

Syntax, route rendering, metadata, internal links, JSON structure, browser reflow, keyboard behavior, no-JavaScript fallbacks, Apache FileInfo behavior, security headers, package CRC, safe paths, and deterministic extraction can be tested locally.

What local tests cannot prove

Production uptime, DNS, TLS termination, search-engine indexing, third-party citation, real Patefacere state, citizen records, diplomatic recognition, or external court treatment require independent evidence.

Package identity

Every accepted release includes VERSION, SHA-256 checksums, package audit, change report, and the next recursive work prompt. Incomplete work still produces a versioned WIP archive.

No deployment assumption

A deployable ZIP is not evidence that it is deployed. Deployment status must come from owner authority or independently observable hosting evidence.

Recursive work

The `.uai` package preserves the next bounded task after every accepted release so subsequent work begins from explicit evidence rather than a generic “continue” instruction.

Currentness regression is tested

The release suite mutates a temporary source fixture from CURRENT to SUPERSEDED and verifies that the public source layer visibly changes while the source provenance remains present.

Release proof boundary

Local package evidence

A release record can establish what was tested and packaged locally. It cannot establish live deployment, external indexing, diplomatic recognition, or operation of Eviulon/Patefacere services.

ACCEPTED_PREPACKAGE

Release 1.7.0

Reviewed: 2026-08-09

This record proves local pre-package acceptance and planned artifact names only. Archive hashes are recorded in sibling release artifacts after deterministic packaging; it does not prove live deployment, indexing, recognition, or operational Eviulon/Patefacere state.

TEST TOTALS

Acceptance record

core_source_route_truth: {"pass":569,"fail":0,"warning":0,"advisory":0}
seo_geo_aeo: {"pass":107,"fail":0,"warning":0,"advisory":0}
tool_conformance: {"pass":14,"fail":0,"warning":0,"advisory":0}
machine_surface_performance: {"pass":40,"fail":0,"warning":0,"advisory":0}
source_currentness_regression: {"pass":5,"fail":0,"warning":0,"advisory":0}
browser_reflow_layout: {"pass":18,"fail":0,"warning":0,"advisory":0}
no_js_print: {"pass":4,"fail":0,"warning":0,"advisory":0}
apache_fileinfo_security: {"pass":37,"fail":0,"warning":0,"advisory":0}
memory_integrity: {"pass":172,"fail":0,"warning":0,"advisory":0}
memory_hardening: {"pass":125,"fail":0,"warning":0,"advisory":0}
combined: {"pass":1091,"fail":0,"warning":0,"advisory":0}

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.

Technical Status (opens external site)

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