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-12 | — |
| Due-soon date | 2027-02-26 | — |
| Expiry date | 2027-03-12 | — |
| Completed date | 2026-08-12 | — |
Evidence and claims
EVI-AE-334 — Version 2.41.0 integrated build and public projection pre-binding
Affected claims
EVI-AC-345— Version 2.41.0 integrated release acceptanceEVI-AC-346— Version 2.41.0 report and rights-advocacy doctrine integrationEVI-AC-347— Version 2.41.0 operational evidence renewalEVI-AC-348— Version 2.41.0 rights review quorum recoveryEVI-AC-349— Version 2.41.0 recognition correction and appealsEVI-AC-350— Version 2.41.0 identity portability and treaty architectureEVI-AC-351— Version 2.41.0 compute continuity preservationEVI-AC-352— Version 2.41.0 consent, causality, remedy, and restorationEVI-AC-353— Version 2.41.0 synchronization, currentness, public projection, and lean packaging
Trigger and required action
Trigger: Validity ends without completed review and current successor evidence.
Disposition: Superseded by v2.42 successor evidence.
- Complete declared review gates
- Verify reviewer authority and conflicts
- Publish successor evidence after 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-12 | Published v2.41.0 evidence expiry schedule. |
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.