Purpose and boundary
Every current evidence artifact has one public expiry date matching its assurance evidence record. Reaching that date without review and successor evidence requires suspension, expiry or supersession; it never silently renews.
What happens after expiry
- Stop relying on the expired artifact.
- Suspend affected current claims.
- Repeat declared review gates.
- Publish current successor evidence when requirements pass.
- Preserve the expired artifact and its hash as history.
Registry sections
165 canonical records are assigned exactly once across bounded semantic pages. Each page uses ordinary links and remains complete without JavaScript.
ACTIVE-EXPIRY-SCHEDULES
Active expiry schedules
Scheduled, due-soon, due and under-review evidence validity records.
- Records
- 9
- Pages
- 1
Route-family review · EVI-THIN-016
Compact-record context
This route belongs to the reviewed Assurance record families family. Disposition: Convert to Compact Record. Its stable ID and distinct fact remain public; broader explanation is owned by /state/defense/assurance/.
Open the measured word range, route inventory, preservation rules, and limitations →
HISTORICAL-EXPIRY-RECORDS
Historical expiry records
Superseded, expired, renewed, closed and suspended expiry history.
- Records
- 156
- Pages
- 9
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
Expiry API · Canonical JSON · CSV export
Segment metadata API · Segment metadata JSON · Segment metadata CSV
Authority and record status
Responsible authority: National Engineering Directorate and State Registry.
Expiry is a package-governance state, not an operational incident or live-readiness signal.
Revision date: . Public corrections may be initiated through the diplomatic contact route.