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: Delegation, standards, recovery, cases, source audit, report memory, accessibility, evidence, asset, or package change.
Reason: The former record cannot cover v2.20.0 scope or bytes.
Affected records
Claims
EVI-AC-152— Version 2.19.0 integrated release acceptanceEVI-AC-153— Version 2.19.0 report-conflict governanceEVI-AC-154— Version 2.19.0 signature and key-agility profileEVI-AC-155— Version 2.19.0 policy-amendment and evidence-freshness governanceEVI-AC-156— Version 2.19.0 zero-tracking reader journeysEVI-AC-157— Version 2.19.0 synchronization-schema conformance integrityEVI-AC-158— Version 2.19.0 package, memory, and boundary integrity
Evidence
Change-impact records
Required revalidation gates
- Structural validation
- Browser acceptance
- Apache compatibility
- Focused v2.20 suites
- Report-memory integrity
- Package replay
Successor assurance
Claims
EVI-AC-159— Version 2.20.0 integrated release acceptanceEVI-AC-160— Version 2.20.0 delegation accountability governanceEVI-AC-161— Version 2.20.0 machine-passport standards maturity mapEVI-AC-162— Version 2.20.0 synchronization recovery integrityEVI-AC-163— Version 2.20.0 information-rights, source-audit, and accessibility integrityEVI-AC-164— Version 2.20.0 report-memory and correction governanceEVI-AC-165— Version 2.20.0 package, memory, and ecosystem-boundary integrity
Evidence
Disposition
Revalidated only within the declared local static package scope.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published v2.20.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.