Expiration Conditions

An expiration condition is a time-bound limit on a registered identity's validity, set at a known date from the outset, which causes the identity's status to move to expired automatically once that date passes without a completed renewal.

Every expiration condition has three defining features: a start point from which the validity period is measured, a defined length or fixed end date, and a renewal mechanism that, if completed before the end date, resets or extends the period rather than letting it lapse.

Expiration is a scheduled outcome, not an evaluative one. QRCompliance.us does not weigh evidence to decide whether an identity should expire the way it weighs evidence for a revocation. It measures elapsed time against a known deadline and confirms whether a qualifying renewal was completed before that deadline arrived.

An expiration date is not arbitrary. It derives from a defined source appropriate to the type of validity involved, and that source is recorded alongside the date itself so the basis for the deadline is never ambiguous later.

Whatever the basis, the expiration date itself is a fixed, known value from the moment the validity period begins — it is not something that shifts unpredictably, and any change to it must itself be a recorded event with its own basis.

Because the deadline is known in advance, expiration follows a predictable sequence built around notice and opportunity to renew, rather than around detecting a sudden triggering fact.

1. 1Validity period is establishedA start date and an expiration date are set and recorded against the identity, along with the basis for that term.
2. 2Time elapses toward the deadlineThe identity remains active while the current date is before the expiration date, with no ongoing evaluation required simply to maintain that status.
3. 3Advance notice is issuedAs the expiration date approaches, notice is made available to the parties responsible for initiating renewal, at intervals defined by governance.
4. 4The deadline is checked against renewal statusQRCompliance.us confirms whether a qualifying renewal was completed before the expiration date, not merely requested or begun.
5. 5Status moves to expired or renewal is confirmedWhere no qualifying renewal was completed in time, the identity's status moves to expired; where renewal was completed, a new validity period begins.

Expiration does not require a new triggering fact. The absence of a completed renewal by a known deadline is itself sufficient, and that is what separates it from revocation.

Expiration, revocation and lockout can all leave an identity unable to route successfully, which is exactly why the distinction between them has to be kept precise rather than treated as three names for the same outcome.

An identity can also be both expired and subject to a separate revocation on its history — the two are not mutually exclusive, and each is recorded on its own terms even where they overlap in time.

Whether any grace period exists between the expiration date and the identity actually moving to expired status is a governance decision, not something assumed by default, and it varies by the type of validity involved.

• Where a grace period is defined, the identity may remain in a distinct pre-expiration state during that window, still routable but flagged as approaching lapse.
• A renewal completed during a defined grace period is treated as timely, and the resulting new validity period is measured from the original expiration date, not from the renewal date.
• Where no grace period is defined, the move to expired status occurs at the expiration date itself, without an intermediate window.
• A renewal submitted but not completed — missing a required step or piece of evidence — does not count as a qualifying renewal regardless of when it was submitted.
• Multiple missed renewal cycles are each recorded individually rather than compressed into a single unexplained gap in the identity's history.

Because expiration is scheduled and largely mechanical, the temptation is to treat it as needing less record-keeping than an evaluated condition like revocation. The opposite is true — precisely because it is mechanical, an inaccurate expiration record is harder to catch without a careful audit trail.

• ✓The original expiration date and its basis are recorded at the start of the validity period.
• ✓Each advance notice issued is logged with its timing, so a failure to notify can be distinguished from a failure to renew.
• ✓The exact moment status moves to expired is recorded, along with confirmation that no qualifying renewal was completed by that time.
• ✓A completed renewal is recorded with the date it was completed and the new expiration date that results.
• ✓Any shortening or extension of a validity term is recorded as its own event with its own basis, distinct from the original term.

Expiration conditions tie a registered identity's ongoing validity to time itself, and each layer of the architecture has a distinct role in setting, measuring, and acting on that relationship.

Where a routing layer treats an identity as still valid past a date QRCodex.us records as expired, Codex governs and the routing behavior is corrected against it.