Record
| Field | Value | Canonical record |
|---|---|---|
| Invalidation class | Changed source, evidence, route, memory, and package scope | — |
| Classification | PUBLIC | — |
| Reviewer class | repository-automated | — |
| Certification status | Not independent certification | — |
| Effective date | 2026-08-10 | — |
| Correction route | /state/information-rights/corrections/ | Open record |
Trigger and reason
Trigger: Adversarial governance registries, deterministic fixtures, public projection, typed memory, synchronization-v2.7, exact-once currentness, assurance artifacts, or package-partition scope changed.
Reason: The v2.35 predecessor cannot cover the v2.36 source, evidence, route, memory, and package scope.
Affected records
Claims
EVI-AC-291— Version 2.35.0 integrated release acceptanceEVI-AC-292— Version 2.35.0 rights implementation evidenceEVI-AC-293— Version 2.35.0 recognition under uncertaintyEVI-AC-294— Version 2.35.0 participation and anti-Sybil governanceEVI-AC-295— Version 2.35.0 economic continuity and compute dependencyEVI-AC-296— Version 2.35.0 consent and cognitive integrityEVI-AC-297— Version 2.35.0 legal responsibility and remediesEVI-AC-299— Version 2.35.0 public projection and split packaging
Evidence
Change-impact records
Required revalidation gates
- Structural validation
- Focused v2.36 suites
- Report-memory integrity
- Public-route validation
- Package-set replay
Successor assurance
Claims
EVI-AC-300— Version 2.36.0 integrated release acceptanceEVI-AC-307— Version 2.36.0 Patefacere synchronization v2.7 and full-corpus currentnessEVI-AC-308— Version 2.36.0 public projection, typed memory, and split packaging
Evidence
Disposition
Revalidated only within the declared local static pre-binding and external package-set scope.
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | Published v2.36.0 successor relation from EVI-AE-279 to EVI-AE-288. |
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.