Purpose and boundary
An invalidation record names the trigger, affected claims and evidence, required revalidation gates, and successor claim or evidence IDs. Revalidated means those declared package gates passed; it does not mean the live host or Evulgare operational environment was independently certified.
Public limits
The registry excludes live incidents, target data, people, credentials, private topology, exploit paths, vulnerabilities, operational thresholds, weapon configuration and readiness.
Registry sections
569 canonical records are assigned exactly once across bounded semantic pages. Each page uses ordinary links and remains complete without JavaScript.
V1-RELEASE-TRANSITIONS
Version 1 release transitions
Invalidation and revalidation chains from the first major release family.
- Records
- 26
- Pages
- 2
V2-RELEASE-TRANSITIONS
Version 2 release transitions
Current and historical release-to-release assurance transitions.
- Records
- 370
- Pages
- 21
GOVERNANCE-AND-EVIDENCE-BOUNDARIES
Governance and evidence boundaries
Non-release-specific invalidations concerning assurance authority, evidence or public governance.
- Records
- 11
- Pages
- 1
Preservation and completeness
Segmentation changes navigation only. Canonical detail routes, EVI identifiers, evidence hashes, authority, status, dates, reviewer class, certification boundary, relationships, corrections, APIs, JSON and CSV records remain unchanged.
Machine-readable records
Invalidation API · Canonical JSON · CSV export · Change-impact registry
Segment metadata API · Segment metadata JSON · Segment metadata CSV
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
The ledger records package assurance lifecycle only. It is not a live incident or certification system.
Revision date: . Public corrections may be initiated through the diplomatic contact route.