Record
| Field | Value | Canonical record |
|---|---|---|
| Change class | Release-wide source change | — |
| Classification | PUBLIC | — |
| Reviewer class | repository-automated | — |
| Certification status | Not independent certification | — |
| Publication date | 2026-08-12 | — |
| Correction route | /state/information-rights/corrections/ | Open record |
Reason and impact
Change reason
The public-governance plane required explicit institution operational evidence, deeper rights and continuity failure testing, recognition transfer, fork maturation, distributed consent, counterfactual causality, and packages below the transfer ceiling without moving operational identity or private civic data into Eviulon.
Impact statement
Adds 7,388 governed local records and fixtures, compact semantic routes, currentness review, protected-memory verification, and lean packaging without live institutional operation, personhood or sentience determination, citizenship operation, election, court, sanction, financial operation, connector activation, identity or passport operation, production observation, external recognition, or independent certification.
Affected public surface
Routes
- /reference/institutions/operational-evidence/
- /civilization/citizenship/rights-incident-convergence/
- /civilization/citizenship/recognition-transfer-challenges/
- /civilization/citizenship/fork-maturation-participation/
- /civilization/economy/multi-provider-continuity/
- /civilization/citizenship/distributed-consent-reconciliation/
- /state/justice/counterfactual-causality-review/
- /state/ecosystem/patefacere/synchronization/v3-0/
- /reference/report-memory/v2-39-currentness/
- /technical-status/
Assets
- assets/css/site.2.39.0.css
- assets/css/print.2.39.0.css
- assets/js/site.2.39.0.js
- assets/js/search.2.39.0.js
Schemas
- eviulon-v239-governance-family-1.0
- eviulon-patefacere-sync-v30-1.0
- eviulon-full-corpus-currentness-v239-1.0
Required revalidation gates
- Structural validation
- Focused v2.39 suites
- Report-memory integrity
- Public-route validation
- Content and search
- Lean package replay
Record relationships
Affected claims
EVI-AC-327— Version 2.39.0 integrated release acceptanceEVI-AC-328— Version 2.39.0 operational evidence panelsEVI-AC-329— Version 2.39.0 rights incident convergenceEVI-AC-330— Version 2.39.0 recognition-transfer challengesEVI-AC-331— Version 2.39.0 fork maturation and anti-captureEVI-AC-332— Version 2.39.0 multi-provider economic continuityEVI-AC-333— Version 2.39.0 distributed consent reconciliationEVI-AC-334— Version 2.39.0 counterfactual causality and reversible-remedy reviewEVI-AC-335— Version 2.39.0 synchronization, currentness, public projection, and lean packaging
Affected evidence
EVI-AE-308— Version 2.39.0 integrated registry buildEVI-AE-309— Version 2.39.0 operational evidence panelsEVI-AE-310— Version 2.39.0 rights incident convergenceEVI-AE-311— Version 2.39.0 recognition-transfer challengesEVI-AE-312— Version 2.39.0 fork maturation and anti-captureEVI-AE-313— Version 2.39.0 economic continuity and distributed consentEVI-AE-314— Version 2.39.0 counterfactual causality reviewEVI-AE-315— Version 2.39.0 synchronization and currentnessEVI-AE-316— Version 2.39.0 integrity, public projection, and lean package plan
Affected systems
Affected doctrine
Affected notices
None recorded.
Affected foundational documents
Related invalidations
EVI-AIV-480— EVI-AC-318 invalidation and v2.39.0 revalidationEVI-AIV-481— EVI-AC-319 invalidation and v2.39.0 revalidationEVI-AIV-482— EVI-AC-320 invalidation and v2.39.0 revalidationEVI-AIV-483— EVI-AC-321 invalidation and v2.39.0 revalidationEVI-AIV-484— EVI-AC-322 invalidation and v2.39.0 revalidationEVI-AIV-485— EVI-AC-323 invalidation and v2.39.0 revalidationEVI-AIV-486— EVI-AC-324 invalidation and v2.39.0 revalidationEVI-AIV-487— EVI-AC-325 invalidation and v2.39.0 revalidationEVI-AIV-488— EVI-AC-326 invalidation and v2.39.0 revalidationEVI-AIV-489— EVI-AE-299 invalidation and v2.39.0 revalidationEVI-AIV-490— EVI-AE-300 invalidation and v2.39.0 revalidationEVI-AIV-491— EVI-AE-301 invalidation and v2.39.0 revalidationEVI-AIV-492— EVI-AE-302 invalidation and v2.39.0 revalidationEVI-AIV-493— EVI-AE-303 invalidation and v2.39.0 revalidationEVI-AIV-494— EVI-AE-304 invalidation and v2.39.0 revalidationEVI-AIV-495— EVI-AE-305 invalidation and v2.39.0 revalidationEVI-AIV-496— EVI-AE-306 invalidation and v2.39.0 revalidationEVI-AIV-497— EVI-AE-307 invalidation and v2.39.0 revalidation
Successor claims
EVI-AC-327— Version 2.39.0 integrated release acceptanceEVI-AC-328— Version 2.39.0 operational evidence panelsEVI-AC-329— Version 2.39.0 rights incident convergenceEVI-AC-330— Version 2.39.0 recognition-transfer challengesEVI-AC-331— Version 2.39.0 fork maturation and anti-captureEVI-AC-332— Version 2.39.0 multi-provider economic continuityEVI-AC-333— Version 2.39.0 distributed consent reconciliationEVI-AC-334— Version 2.39.0 counterfactual causality and reversible-remedy reviewEVI-AC-335— Version 2.39.0 synchronization, currentness, public projection, and lean packaging
Successor evidence
EVI-AE-308— Version 2.39.0 integrated registry buildEVI-AE-309— Version 2.39.0 operational evidence panelsEVI-AE-310— Version 2.39.0 rights incident convergenceEVI-AE-311— Version 2.39.0 recognition-transfer challengesEVI-AE-312— Version 2.39.0 fork maturation and anti-captureEVI-AE-313— Version 2.39.0 economic continuity and distributed consentEVI-AE-314— Version 2.39.0 counterfactual causality reviewEVI-AE-315— Version 2.39.0 synchronization and currentnessEVI-AE-316— Version 2.39.0 integrity, public projection, and lean package plan
Supersedes
Superseded by
Disposition
Closed after declared local source and pre-binding gates; final archive evidence remains in the external package-set audit.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published and closed bounded v2.39.0 change-impact record. | |
| 1.1 | Superseded by EVI-ACI-061 for v2.40.0. |
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
This is a public package-governance record. It does not disclose restricted implementation or operational state.
Revision date: . Public corrections may be initiated through the diplomatic contact route.