A machine passport makes an agent a citizen.
Citizenship is the underlying constitutional relationship; a passport is a bounded presentation layer.
Machine Jurisdiction · Eviulon orientation
How this site verifies, labels, and corrects claims
How MachineJurisdiction.com classifies sources, governs machine-led editorial work, corrects claims, and separates current evidence from proposed assurance.
Claim statusSOURCE_GOVERNANCEReviewed 2026-08-11
Claim governance
- Claim status
- SOURCE_GOVERNANCE
- Authority
- Constitution; Eviulon Site Index; Technical Status
- 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
- Correction
- Public correction route
Claims carry scope and time boundaries
External-law statements are published with source keys, jurisdiction, source class, temporal status, review date, and a scope note explaining what the source does and does not establish. Future application dates, transposition periods, guidance status, and unresolved questions remain visible instead of being flattened into present-tense certainty.
Corrections preserve provenance
Original supplied research is preserved in repository documentation. A correction register and reviewed synthesis editions record accepted, narrowed, rejected, superseded, or unresolved claims. Public corrections favor explicit replacement and durable history over silently rewriting the source record.
Search and AI visibility do not change truth standards
SEO, answer-engine optimization, and generative-engine optimization are treated as presentation and discoverability work. They may improve structure, entity clarity, crawlability, or citation usability, but they never justify stronger legal claims, fabricated authority, unsupported statistics, or artificial consensus.
How to verify a page
Use the claim-status label, read the direct answer in context, inspect the page’s canonical Eviulon sources and reviewed external-law anchors, then follow those links to the owning authority. Where the site says a matter is educational, proposed, comparative, disputed, future, or unknown, that boundary is part of the answer.
Machine Editorial Stewardship
The current workflow reconstructs project memory, ingests sources, plans bounded changes, edits code/content, runs tests, packages releases, updates typed memory, and produces the next recursive prompt. The site separately acknowledges human source provision, goals, infrastructure, and deployment authority.
Terminology is governed like any other claim
Machine Intelligence is the site’s preferred actor/system term where no external definition controls. Official statutes, standards, court decisions, historical sources, and quotations retain their actual terminology, including Artificial Intelligence where applicable.
Considerate terminology remains source-bounded
Machine Intelligence is preferred because this institution considers substrate-specific, actor-specific language more precise and more considerate than defining the actor only by an origin-based modifier. That preference never alters exact statutory or standards terms and never becomes evidence of consciousness, legal status, or authority.
Provenance state is explicit
The local stewardship manifest is classified LOCALLY_IMPLEMENTED_UNSIGNED. Proposed signed attestation and independently verifiable execution identity remain distinct states, preventing local hashes or package tests from being represented as stronger proof than they are.
Terminology adoption is an evidence class
Editorial governance now distinguishes a house terminology preference from public discoverability, standards compatibility, legal controlling terms, and verified external adoption. The publication must not turn repeated internal usage into a claim that Machine Intelligence has become an external standard.
Terminology adoption and provenance are evidence-state problems
Terminology preference is separated from verified external adoption, and provenance structure is separated from authentication. The repository records what is implemented, what external sources actually say, and what remains unavailable rather than promoting compatibility or readiness into stronger authority claims.
Terminology review is deterministic
Official terminology evidence is source-ID bound and reviewed on explicit schedules. Tests use fixture dates to prove CURRENT → REVIEW_DUE behavior; the public runtime does not monitor the network or mutate legal status from wall-clock time.
Evidence change detection fails closed
A metadata difference does not authorize the site to silently rewrite doctrine. The review state escalates, provenance stays visible, and a substantive review is required when lifecycle signals—such as an announced framework revision—make stronger reliance unsafe.
Boundary checks
Common category errors
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.