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
New supplied research required a governed scenario registry, while the stored loop required privacy-minimized contract, performance, conflict and renewal records.
Impact statement
The v2.8.0 chain does not cover new scenarios, reports, procurement schemas, routes, assets, memory or package bytes.
Affected public surface
Routes
- /state/procurement/contracts/
- /state/procurement/performance/
- /state/procurement/conflicts/
- /state/procurement/renewals/
- /state/futures/
- /state/futures/antarctica/
- /state/futures/moon/
- /state/futures/maritime-commons/
- /state/futures/seabed/
- /state/futures/dependency-reversal/
- /external-relations/human-machine-order/
- /data/futures/
Assets
- assets/css/site.2.9.0.css
- assets/css/print.2.9.0.css
- assets/js/site.2.9.0.js
- assets/js/search.2.9.0.js
Schemas
- public-contract-notice-1.0
- contractor-performance-1.0
- contractor-conflict-1.0
- contract-review-1.0
- future-scenario-1.0
- scenario-methodology-1.0
Required revalidation gates
- Structural validation
- Browser acceptance
- Apache acceptance
- Procurement/futures/report governance
- Package inventory and replay
Record relationships
Affected 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
Affected 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
Affected systems
Affected doctrine
Affected notices
None recorded.
Affected foundational documents
Related invalidations
EVI-AIV-078— EVI-AC-080 invalidation and EVI-AC-086 revalidationEVI-AIV-079— EVI-AC-081 invalidation and EVI-AC-087 revalidationEVI-AIV-080— EVI-AC-082 invalidation and EVI-AC-088 revalidationEVI-AIV-081— EVI-AC-083 invalidation and EVI-AC-089 revalidationEVI-AIV-082— EVI-AC-084 invalidation and EVI-AC-090 revalidationEVI-AIV-083— EVI-AC-085 invalidation and EVI-AC-091 revalidation
Successor claims
EVI-AC-086— Version 2.9.0 integrated release acceptanceEVI-AC-087— Version 2.9.0 responsive and progressive-enhancement behaviorEVI-AC-088— Version 2.9.0 Apache FileInfo-only shared-host compatibilityEVI-AC-089— Version 2.9.0 procurement, futures and report governance preservationEVI-AC-090— Version 2.9.0 root-deployable package inventoryEVI-AC-091— Version 2.9.0 Talisman and constitutional boundary integrity
Successor evidence
EVI-AE-077— Version 2.9.0 structural validation evidence statementEVI-AE-078— Version 2.9.0 Chromium browser evidence statementEVI-AE-079— Version 2.9.0 Apache shared-host evidence statementEVI-AE-080— Version 2.9.0 procurement, futures and report governance evidence statementEVI-AE-081— Version 2.9.0 package inventory evidence statement
Supersedes
Superseded by
Disposition
Accepted and closed. The v2.8.0 chain was superseded by EVI-AC-086 through EVI-AC-091 and EVI-AE-077 through EVI-AE-081.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published the v2.9.0 change and revalidation record. | |
| 1.1 | Superseded by EVI-ACI-030 after scenario-governance, 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.