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-10 | — |
| Due-soon date | 2027-02-25 | — |
| Expiry date | 2027-03-11 | — |
| Completed date | 2026-08-10 | — |
Evidence and claims
EVI-AE-290 — Version 2.37.0 integrated model and data validation statement
Affected claims
EVI-AC-309— Version 2.37.0 integrated release acceptanceEVI-AC-310— Version 2.37.0 rights-remedy reliabilityEVI-AC-311— Version 2.37.0 recognition reviewEVI-AC-312— Version 2.37.0 participation recoveryEVI-AC-313— Version 2.37.0 economic portability drillsEVI-AC-314— Version 2.37.0 consent lifecycle conformanceEVI-AC-315— Version 2.37.0 responsibility appealsEVI-AC-316— Version 2.37.0 Patefacere synchronization and full-corpus currentnessEVI-AC-317— Version 2.37.0 public projection and split packaging
Trigger and required action
Trigger: Validity ends without completed review and current successor evidence.
Disposition: Superseded by v2.38 successor evidence.
- Complete declared review gates
- Verify reviewer authority and conflicts
- Publish successor evidence when bytes or scope change
- Preserve expiring artifact and hash
Unavailable fields
- future review result
- production deployment
- external certification
Review and coverage
Review
Coverage
Successor evidence
Revision history
| Revision | Date | Change |
|---|---|---|
| 1.0 | 2026-08-10 | Published v2.37.0 evidence expiry schedule. |
| 1.1 | 2026-08-10 | Superseded by v2.38 evidence. |
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.