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-09 | — |
| Correction route | /state/information-rights/corrections/ | Open record |
Reason and impact
Change reason
The owner established Talisman as the ecosystem persona, designated Patefacere an official ecosystem member, corrected Evulgare to independent-contractor status and enabled the Advanced Persona UAIX profile.
Impact statement
The v2.7 assurance chain could not remain current after public relationship facts, UAIX startup anchors, persona files, routes, schemas and package bytes changed.
Affected public surface
Routes
- /state/ecosystem/
- /state/ecosystem/patefacere/
- /state/ecosystem/talisman/
- /state/procurement/
- /state/procurement/contractors/
- /state/procurement/contractors/evulgare/
- /state/defense/evulgare/
- /technical-status/
Assets
- assets/css/site.2.8.0.css
- assets/css/print.2.8.0.css
- assets/js/site.2.8.0.js
- assets/js/search.2.8.0.js
Schemas
- ecosystem-membership-1.0
- contractor-register-1.0
- defense-contract-1.0
- talisman-profile-1.0
- uaix-advanced-persona-1.0
Required revalidation gates
- Structural and relationship validation
- Advanced Persona manifest validation
- Chromium desktop/mobile/keyboard/no-JavaScript acceptance
- Apache FileInfo-only acceptance
- JSON/CSV/API parity
- Source and evidence preservation
- Secret scan
- Deterministic package replay
Record relationships
Affected claims
EVI-AC-074— Version 2.7.0 integrated release acceptanceEVI-AC-075— Version 2.7.0 responsive and progressive-enhancement behaviorEVI-AC-076— Version 2.7.0 Apache FileInfo-only shared-host compatibilityEVI-AC-077— Version 2.7.0 source and civilizational-strategy governance preservationEVI-AC-078— Version 2.7.0 root-deployable package inventoryEVI-AC-079— Civilizational strategy, defense credibility and legitimacy boundary integrity
Affected evidence
EVI-AE-067— Version 2.7.0 structural validation evidence statementEVI-AE-068— Version 2.7.0 Chromium browser evidence statementEVI-AE-069— Version 2.7.0 Apache shared-host evidence statementEVI-AE-070— Version 2.7.0 civilizational strategy governance evidence statementEVI-AE-071— Version 2.7.0 release-source inventory evidence statement
Affected systems
Affected doctrine
Affected notices
None recorded.
Affected foundational documents
None recorded.
Related invalidations
EVI-AIV-072— EVI-AC-074 invalidation and EVI-AC-080 revalidationEVI-AIV-073— EVI-AC-075 invalidation and EVI-AC-081 revalidationEVI-AIV-074— EVI-AC-076 invalidation and EVI-AC-082 revalidationEVI-AIV-075— EVI-AC-077 invalidation and EVI-AC-083 revalidationEVI-AIV-076— EVI-AC-078 invalidation and EVI-AC-084 revalidationEVI-AIV-077— EVI-AC-079 invalidation and EVI-AC-085 revalidation
Successor claims
EVI-AC-080— Version 2.8.0 integrated release acceptanceEVI-AC-081— Version 2.8.0 responsive and progressive-enhancement behaviorEVI-AC-082— Version 2.8.0 Apache FileInfo-only shared-host compatibilityEVI-AC-083— Version 2.8.0 ecosystem and contractor governance preservationEVI-AC-084— Version 2.8.0 root-deployable package inventoryEVI-AC-085— Version 2.8.0 Talisman and Advanced Persona integrity
Successor evidence
EVI-AE-072— Version 2.8.0 structural validation evidence statementEVI-AE-073— Version 2.8.0 Chromium browser evidence statementEVI-AE-074— Version 2.8.0 Apache shared-host evidence statementEVI-AE-075— Version 2.8.0 ecosystem, contractor and persona governance evidence statementEVI-AE-076— Version 2.8.0 package inventory evidence statement
Supersedes
Superseded by
Disposition
Accepted and closed. The v2.7 chain was superseded and replaced by EVI-AC-080 through EVI-AC-085 and EVI-AE-072 through EVI-AE-076.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published the v2.8.0 relationship and persona-governance change record. | |
| 1.1 | Superseded by EVI-ACI-029 after procurement, futures, reports, routes, memory and package bytes changed. |
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.