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. |
Change-impact records
EVI-ACI-001 · Release-wide source change
Version 1.6.0 release-wide assurance change review
Records the source, route, schema, test, asset, documentation and package changes that required the v1.5.0 assurance chain to be superseded and revalidated for v1.6.0.
- Status
- Closed
- Affected claims
- 5
- Revalidation gates
- 7
- Certification
- Not independent certification
EVI-ACI-002 · Route and schema change
Assurance route and schema expansion
Adds canonical change-impact and invalidation hubs, detail routes, APIs, JSON datasets and CSV exports.
- Status
- Revalidated
- Affected claims
- 1
- Revalidation gates
- 6
- Certification
- Not independent certification
EVI-ACI-003 · Public asset change
Version 1.6.0 public runtime asset change
Versions the portal CSS and JavaScript assets to 1.6.0 and adds responsive presentation for assurance lifecycle records.
- Status
- Revalidated
- Affected claims
- 2
- Revalidation gates
- 6
- Certification
- Not independent certification
EVI-ACI-004 · Host configuration and route-set change
Version 1.6.0 host configuration and route-set change
Extends the tested public route set to the assurance change-impact and invalidation registries without broadening Apache override requirements.
- Status
- Revalidated
- Affected claims
- 2
- Revalidation gates
- 5
- Certification
- Not independent certification
EVI-ACI-005 · Assurance scope proposal
Proposal to label repository tests as independent certification
Records and rejects any attempt to describe project-owned automation as independent certification.
- Status
- Rejected
- Affected claims
- 2
- Revalidation gates
- 5
- Certification
- Not independent certification
EVI-ACI-006 · Deployment evidence proposal
Production-host acceptance evidence proposal
Defines the evidence that would be required to make a bounded claim about an authorized production deployment.
- Status
- Proposed
- Affected claims
- 3
- Revalidation gates
- 7
- Certification
- Not independent certification
EVI-ACI-007 · Historical release source freeze
Version 1.5.0 release source freeze
Preserves the accepted v1.5.0 source-freeze boundary that existed before the v1.6.0 assurance-governance expansion.
- Status
- Superseded
- Affected claims
- 1
- Revalidation gates
- 1
- Certification
- Not independent certification
Preservation rule
A previously hashed evidence artifact is never silently edited to fit new source bytes. The affected claim or evidence record is invalidated or superseded, the earlier artifact remains preserved, and a successor record identifies new evidence.
Machine-readable records
Change-impact API · Canonical JSON · CSV export · Invalidation and revalidation registry
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
EVI-PRO-022 governs this public registry. It excludes operational detail and never converts repository evidence into independent certification.
Revision date: . Public corrections may be initiated through the diplomatic contact route.