Route 150 of 176
Certification State (Certified Layer)
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
A registered identity can be described from several angles: whether it is valid, whether it is registered, and whether it is certified. Certification state is the last of these — the value QRCertified.us itself maintains to say whether an identity currently holds certification, and if so, on what terms. This route describes that state as it lives inside the authorization layer, not as it is reported elsewhere.
Certification state is a value QRCertified.us owns and maintains. QRCompliance.us's evaluation feeds it, but it does not hold it, and the two states — compliance condition and certification state — are never collapsed into one.
Certification is not a one-time stamp applied at issuance and forgotten. It is a state — current, restricted, suspended, or absent — that QRCertified.us maintains for as long as the certification could plausibly matter to anyone consulting it. That state changes over time, in response to evidence, renewal, restriction, or revocation, and at any given moment it has one current value.
This route is about that state as QRCertified.us holds it: what values it can take, what causes it to change, and how it is exposed to the layers and parties who need to know it. It is deliberately narrow — the earlier, general treatment of certification state that appears in the identity-and-compliance-state category describes the concept as QRCompliance.us observes and references it. This route describes the same concept from the authorization layer's own side, where the value is actually set and owned.
Keeping these two views distinct matters because certification state and compliance condition answer different questions. Compliance condition asks whether the conditions behind a certification remain satisfied. Certification state asks what QRCertified.us has actually decided and currently holds as true about the identity's authorization. The first can shift before the second does, and the gap between them is itself meaningful.
01Plain-English Definition
Certification state, from the certified layer's own perspective, is the current value QRCertified.us maintains describing whether a registered identity holds active certification, holds it with restrictions, has had it suspended or revoked, or has never held it — together with the basis and date of that value.
The state is a single current answer at any moment, even though the history behind it may include several transitions. Anyone consulting QRCertified.us about an identity gets that current value, not a running narrative of every change that produced it.
This route does not restate the general concept of certification state already covered where identity-level states are introduced elsewhere in this encyclopedia. It focuses specifically on how the value is owned, set, and changed by QRCertified.us as the authorization layer, rather than how it is referenced by validation.
02The Values Certification State Can Hold
QRCertified.us recognizes a defined, finite set of certification state values, so that any party consulting it gets an unambiguous answer rather than an open-ended description.
| State Value | Meaning |
|---|---|
| Certified — current | Certification is active and in good standing under its current terms |
| Certified — restricted | Certification is active but limited in scope, duration, or applicable conditions |
| Suspended | Certification is temporarily withdrawn pending resolution of an identified issue |
| Revoked | Certification has been withdrawn and does not reactivate without a new determination |
| Expired — unrenewed | A prior certification's validity period has lapsed without a completed renewal |
| Never certified | No certification has ever been issued for this identity |
03What Causes The State To Change
Certification state does not drift on its own. Each transition has a specific cause that QRCertified.us can point to when the state changes.
- A certification decision is made on the strength of a compliance evidence record, setting the state to certified for the first time.
- A renewal is completed before expiry, carrying the certified state forward under refreshed terms.
- A restriction is applied in response to a partial finding, moving the state from fully certified to certified-restricted.
- A suspension or revocation is applied following a confirmed compliance failure or an external directive.
- A validity period lapses without renewal, moving the state to expired-unrenewed regardless of whether underlying conditions still hold.
In every case, the trigger for the change is something QRCertified.us itself acts on — often informed by a compliance evidence record — but the act of changing the state is its own, not an automatic mirror of a compliance condition changing.
04Practical Value
Holding certification state as its own owned value, rather than deriving it live from compliance condition each time, gives the authorization layer a stable, referenceable answer.
Stable answer
Parties checking certification get a definite current value rather than a recomputation that could vary by who is asking.
Traceable transitions
Each state change has a recorded cause, supporting later review of why and when a certification changed.
Independent timing
Certification state can lag or lead a shift in underlying compliance condition, and that gap is itself informative rather than an error.
Clear ownership
There is never ambiguity about which layer's record is authoritative for whether an identity is currently certified.
05Operational Flow
The state's lifecycle runs from initial certification through ongoing monitoring to whatever transition eventually applies.
- 1Certification is issuedQRCertified.us sets certification state to current based on a supporting compliance evidence record.
- 2State is exposed as currentAny party consulting QRCertified.us about the identity receives this value until it changes.
- 3Compliance evidence continues to be producedQRCompliance.us continues evaluating relevant conditions over the certification's life.
- 4A trigger prompts reviewNew evidence, an approaching expiry, or an external directive prompts QRCertified.us to review the current state.
- 5State is updated and re-exposedQRCertified.us sets the new state value, records the basis, and makes the updated value available going forward.
Certification state changes only when QRCertified.us acts on it. A shift in underlying compliance condition is an input to that review, not a change to the state by itself.
06System Relationship
System Chain — Six Locked Entities
- 1QuickResponseCode.usRoot / System EntryPublic entry point to the QR infrastructure.
- 2QRProtocol.usGovernance (Rules)Writes and governs the applicable rules.
- 3QRCompliance.usValidationValidates compliance readiness against applicable rules and conditions.
- 4QRCertified.usCertification AuthorityAuthorizes the QR for certification.
- 5QRRegistered.usRegistration ResultMandatorily registers the authorized QR.
- 6QRCodex.usOperations / RecordsRecords, operates, logs and preserves canonical operational truth.
No registration → no certified QR output.
Certification state as held by the certified layer depends on inputs from validation and registration but remains a value only QRCertified.us owns and changes.
| Layer | Relationship To Certification State (Certified Layer) |
|---|---|
| ROOT — QuickResponseCode.us | Ensures the certification state always attaches to the one persistent identity it describes, regardless of how many transitions the state has gone through. |
| GOVERNANCE — QRProtocol.us | Defines the finite set of recognized certification state values and the triggers that permit a transition between them. |
| VALIDATION — QRCompliance.us | Produces the compliance evidence that informs QRCertified.us's review, without itself holding or setting the certification state. |
| AUTHORIZATION — QRCertified.us | Owns, sets, and changes certification state, and is the sole source consulted for its current value. |
| REGISTRATION — QRRegistered.us | Supplies the underlying registration standing that certification state presumes remains intact throughout. |
| OPERATIONS — QRCodex.us | Records every certification state transition, its cause, and its date as part of the permanent operational history. |
Where the certification state reported at a given moment conflicts with Codex's recorded transition history, Codex governs which value was actually current.
What This Does — And Does Not — Do
Does
- ✓Maintain a single current certification state value for each certified or previously-certified identity
- ✓Recognize a defined, finite set of state values rather than free-form descriptions
- ✓Change state only in response to a specific, recorded trigger
- ✓Draw on compliance evidence as an input to reviewing the state without treating that evidence as the state itself
- ✓Expose the current state value consistently to any party authorized to consult it
- ✓Record the cause and date of every state transition as part of the certification's history
Does Not
- ✕Allow compliance condition to change automatically without a corresponding review and act by QRCertified.us
- ✕Let QRCompliance.us set or hold the certification state value directly
- ✕Blend certification state with registration state or compliance condition into one undifferentiated value
- ✕Discard the record of a prior state once a new state is set
- ✕Treat an approaching or lapsed expiry as resolved without an explicit renewal transition
- ✕Restate the general cross-layer concept of certification state already covered elsewhere rather than the certified layer's own record
Related Routes
Common Questions
Is certification state the same thing as compliance condition?
No. Compliance condition asks whether the conditions behind a certification remain satisfied. Certification state is the value QRCertified.us has actually set and currently holds, which may lag or lead a shift in that underlying condition.
Can QRCompliance.us change an identity's certification state?
No. QRCompliance.us produces evidence that informs QRCertified.us's review, but only QRCertified.us sets or changes the certification state itself.
Why does this route exist separately from Route 17?
Route 17 introduces certification state as a general identity-level concept. This route describes the same state specifically as the certified layer owns, sets, and maintains it internally.
What happens if certification expires without a renewal being completed?
The state transitions to expired-unrenewed. This happens regardless of whether the underlying compliance conditions still hold, because the transition is tied to the expiry trigger, not to condition alone.
Is every past certification state value retained?
Yes. QRCodex.us records each transition, its cause, and its date, so the full history behind the current value remains available for review.