Record
| Field | Value | Canonical record |
|---|---|---|
| Invalidation class | Changed package bytes and scope | — |
| Classification | PUBLIC | — |
| Reviewer class | repository-automated | — |
| Certification status | Not independent certification | — |
| Effective date | 2026-08-09 | — |
| Correction route | /state/information-rights/corrections/ | Open record |
Trigger and reason
Trigger: Review-calendar, uncertainty, diplomatic-record, dependency-exit, statement-history, synchronization, source-currentness, report-memory, evidence, asset, or package change.
Reason: The former record cannot cover v2.23.0 scope or bytes.
Affected records
Claims
EVI-AC-174— Version 2.22.0 integrated release acceptanceEVI-AC-177— Version 2.22.0 scenario calibration and crisis-handback governanceEVI-AC-178— Version 2.22.0 Patefacere public-status contract v1.3 conformance
Evidence
Change-impact records
Required revalidation gates
- Structural validation
- Browser acceptance
- Apache compatibility
- Focused v2.23 suites
- Report-memory integrity
- Package replay
Successor assurance
Claims
EVI-AC-183— Version 2.23.0 integrated release acceptanceEVI-AC-185— Version 2.23.0 diplomatic record lifecycleEVI-AC-186— Version 2.23.0 dependency exit and handback governanceEVI-AC-187— Version 2.23.0 public statement history and critique governance
Evidence
Disposition
Revalidated only within the declared local static package scope.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published v2.23.0 invalidation and successor mapping. |
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
The record proves only the stated package-level invalidation and revalidation chain. It is not independent certification or live readiness.
Revision date: . Public corrections may be initiated through the diplomatic contact route.