Expiry record
| Field | Value | Canonical record |
|---|---|---|
| Record type | Assurance evidence expiry record | — |
| Status | Superseded | — |
| Reviewer class | repository-automated | — |
| Certification status | Not independent certification | — |
| Valid from | 2026-08-06 | — |
| Due-soon date | 2027-01-23 | — |
| Expiry date | 2027-02-06 | — |
| Completed date | 2026-08-09 | — |
Evidence and claims
EVI-AE-026 — Version 1.8.0 release-source inventory evidence statement
Affected claims
Trigger and required action
Trigger: The declared validity end is reached without a completed review and current successor evidence.
Disposition: Superseded before scheduled expiry because new evidence was generated for changed v1.9.0 bytes; former evidence and hash remain preserved.
- Complete declared review gates
- Verify reviewer authority and conflict status
- Publish successor evidence when bytes or scope changed
- Preserve the expiring artifact and hash
Unavailable fields
- future test result
- future external reviewer identity
- live scheduler state
- production readiness
Review and coverage
Review
Coverage
Successor evidence
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | 2026-08-06 | Published a six-month expiry schedule for the v1.8.0 evidence artifact. |
| 1.1 | 2026-08-09 | Superseded by named v1.9.0 evidence before the former validity end. |
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
Reaching an expiry date does not create a live incident. It ends package-evidence reliance until review or successor evidence is recorded.
Revision date: . Public corrections may be initiated through the diplomatic contact route.