Purpose and boundary
Each record identifies what changed, why earlier evidence could no longer support the changed surface, which public records and paths were affected, and which tests or reviews were required. These are package-governance records—not live incident reports, vulnerability disclosures, readiness statements or independent certification.
Lifecycle states
| State | Meaning |
|---|---|
| Proposed | A change has been described, but authority, scope or evidence is not yet sufficient to begin review. |
| Under Review | The affected records and required revalidation gates are being determined. |
| Revalidation Required | A relevant change has suspended reliance on one or more prior claims until successor evidence is produced. |
| Invalidated | A prior claim or evidence statement no longer supports current reliance within its former scope. |
| Revalidated | Required gates passed and named successor evidence supports the new bounded claim. |
| Superseded | A newer record replaces this record while preserving it as public institutional history. |
| Closed | The reviewed change has a final public disposition and no unresolved release gate. |
| Rejected | The proposed scope or treatment was declined and may not be represented as accepted assurance. |
Registry sections
61 canonical records are assigned exactly once across bounded semantic pages. Each page uses ordinary links and remains complete without JavaScript.
RELEASE-WIDE-CHANGES
Release-wide changes
Release transitions and release-source freezes.
- Records
- 37
- Pages
- 4
IMPLEMENTATION-AND-GOVERNANCE
Implementation and governance changes
Route, schema, asset, host-configuration, documentation and memory changes.
- Records
- 13
- Pages
- 2
PROPOSALS-AND-DECISIONS
Proposals and decisions
Proposed or rejected changes preserved as public governance history.
- Records
- 2
- 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
Change-impact API · Canonical JSON · CSV export · Invalidation and revalidation registry
Segment metadata API · Segment metadata JSON · Segment metadata CSV
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
EVI-PRO-042 governs compact assurance navigation. It excludes operational detail and never converts repository evidence into independent certification.
Revision date: . Public corrections may be initiated through the diplomatic contact route.