Route 156 of 176
Registration State (Registered Layer)
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
An identity's registration state — registered, pending, invalid, or revoked — is recorded and maintained by QRRegistered.us alone. This route addresses that state strictly from the validation side: how QRCompliance.us reads it, what it may and may not infer from it, and why validation never becomes a second place where that state is decided.
QRCompliance.us reads registration state as an input to its own evaluations. It does not set, change, or hold a competing copy of that state — QRRegistered.us is the sole authority over what the registered layer's standing actually is.
Registration state is the registered layer's own bookkeeping: whether a given identity currently stands as registered, is still pending review, was found invalid, or has been revoked. The full definition of those four states, how an identity moves between them, and how they differ from compliance condition is covered elsewhere in this encyclopedia under the route dedicated to registration state itself.
This route exists because registration state does not stay confined to the registered layer. QRCompliance.us consults it constantly — a compliance condition cannot meaningfully be evaluated for an identity that is not currently a live registration, and several validation checks depend directly on knowing which of the four states currently applies. The relationship between the two layers on this point deserves its own treatment.
The governing rule is simple to state and easy to get wrong in implementation: QRCompliance.us is a reader of registration state, never a second writer of it. Every evaluation that depends on registration state pulls the current value from QRRegistered.us's own record. Validation never maintains a parallel version of that state that could drift from the authoritative one.
01Plain-English Definition
From the validation side, registration state is the value QRCompliance.us reads from QRRegistered.us before or during an evaluation, treated as an authoritative fact rather than something validation itself determines.
Route 18 covers what registration state is and how it functions inside the registered layer — the four states themselves, how an identity enters and leaves each one, and how registration state differs from compliance condition and certification state. That ground is not repeated here.
What belongs here is the interface: how QRCompliance.us consumes that state, what it is entitled to assume from a given value, and what obligations flow from the fact that the state can change at any time, independent of any validation activity taking place.
02Why Validation Depends On This State
A number of validation activities cannot be meaningfully performed without first knowing the current registration state of the identity in question.
- A compliance condition evaluation presumes a registered identity exists to evaluate; there is nothing to check a compliance rule against for an identity still pending or found invalid.
- A revocation trigger reaching QRCompliance.us is only meaningful if it is compared against the identity's actual current registration standing, not an assumed one.
- Certification eligibility checks, addressed under the QRCompliance.us ↔ QRCertified.us category, depend on the identity already being registered before certification can even be considered.
- Audit and reporting activity attributed to an identity needs to be understood in the context of what its registration standing was at the time, not only what it is now.
In every one of these cases, the state itself is a fact supplied by the registered layer. QRCompliance.us's role is to use that fact correctly in its own evaluation, not to independently decide what the fact is.
03What Validation May And May Not Do With It
Because registration state is authoritative and external to validation, there are clear limits on how QRCompliance.us may treat it.
May read the current value
QRCompliance.us pulls the live registration state from QRRegistered.us whenever an evaluation needs it.
May act differently based on the value
Different evaluation logic applies depending on whether the identity is registered, pending, invalid, or revoked.
May not overwrite or hold a competing value
Validation does not maintain its own copy of registration state that could diverge from the registered layer's record.
May not infer a state QRRegistered.us has not recorded
An assumption about likely registration standing is never treated as equivalent to the recorded value.
04Operational Flow
A typical validation activity that depends on registration state follows a consistent pattern of reading, using, and reacting to that value.
- 1Evaluation is initiatedA compliance condition check, a revocation trigger review, or a related validation activity begins for a given identity.
- 2Current registration state is requestedQRCompliance.us reads the identity's live registration state from QRRegistered.us rather than relying on a cached or assumed value.
- 3State is applied to the evaluation logicThe check proceeds, is deferred, or is declared inapplicable, depending on which of the four states currently applies.
- 4Result is recorded with the state notedThe evaluation's outcome is recorded along with the registration state that was in effect when it was reached.
- 5A later state change triggers re-evaluation where relevantIf registration state subsequently changes, any dependent validation activity is revisited rather than left resting on a stale value.
A compliance evaluation performed while registration state was stale is not simply wrong at the margins — it is an evaluation of a fact that no longer applies, and it must be revisited.
05Reading Versus Owning: The Line In Practice
The distinction between reading a value and owning it is where most implementation confusion arises, and it is worth setting the two roles against each other directly.
| Aspect | QRCompliance.us (Reader) | QRRegistered.us (Owner) |
|---|---|---|
| Holds | A momentary reference to the current registration state, used for one evaluation | The authoritative, persistent registration state record |
| Can change the state | Never — validation has no mechanism to alter registration state directly | Yes — through admission, expiry, revocation or a superseding action |
| Responds to a stale read | Re-requests the current value and revisits any affected determination | Is not affected, since its own record was never stale to begin with |
| Failure mode if roles blur | Validation acts on an outdated or invented state, producing an incorrect evaluation | Registration record is bypassed, undermining its authority over its own layer |
This is the same discipline applied elsewhere in the architecture between determining a condition and enforcing it, translated here into the narrower question of who is entitled to say what an identity's registration standing currently is.
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.
Registration state, considered from the validation side, touches every layer that either supplies it, consumes it, or depends on decisions made using it.
| Layer | Relationship To Registration State (As Read By Validation) |
|---|---|
| ROOT — QuickResponseCode.us | Anchors the identity whose registration state is being read, independent of what that state currently is. |
| GOVERNANCE — QRProtocol.us | Defines which validation activities require a current registration state read before proceeding. |
| VALIDATION — QRCompliance.us | Reads the current registration state and applies it to evaluations without ever writing or holding a competing copy of it. |
| AUTHORIZATION — QRCertified.us | Depends on registration state indirectly, since certification eligibility presumes a registered identity already exists. |
| REGISTRATION — QRRegistered.us | Owns and maintains registration state as the sole authoritative source for the value validation reads. |
| OPERATIONS — QRCodex.us | Preserves the history of registration state values and the validation determinations made against each one. |
Where a validation determination appears to conflict with QRCodex.us's recorded history of registration state, Codex governs and the determination is reviewed against it.
What This Does — And Does Not — Do
Does
- ✓Read the current registration state from QRRegistered.us before or during any evaluation that depends on it
- ✓Apply different evaluation logic depending on whether the identity is registered, pending, invalid, or revoked
- ✓Record which registration state was in effect at the time a given evaluation was reached
- ✓Re-request the current registration state, and revisit any dependent determination, once a state change is detected
- ✓Treat registration state as an authoritative external fact supplied by the registered layer
- ✓Defer or decline evaluations that depend on registration standing the identity has not yet reached
Does Not
- ✕Set, change, or hold a competing copy of an identity's registration state
- ✕Infer a registration state that QRRegistered.us has not itself recorded
- ✕Treat a stale or cached registration state read as equivalent to the current authoritative value
- ✕Allow a compliance determination to stand unrevisited once the registration state it relied on has changed
- ✕Perform compliance condition evaluation as though an unregistered identity were already registered
- ✕Duplicate the substantive definition of the four registration states, which belongs to Route 18
Related Routes
Common Questions
Where is registration state itself defined?
Under Route 18, which covers the four states, how an identity enters and exits each one, and how registration state differs from compliance condition and certification state.
Can QRCompliance.us change an identity's registration state?
No. QRCompliance.us reads registration state as a fact supplied by QRRegistered.us. It has no mechanism to set or alter that state.
What happens if validation used a stale registration state?
The evaluation reached using that stale value is not treated as sound. QRCompliance.us re-requests the current state and revisits any determination that depended on the outdated one.
Can a compliance condition be evaluated for a pending or invalid identity?
Generally no. Compliance condition evaluation presumes a registered identity exists. Pending or invalid identities have not yet reached, or no longer hold, that standing.
Why not let QRCompliance.us maintain its own copy of registration state for speed?
A second maintained copy could drift from the registered layer's authoritative record, producing evaluations based on a fact that is no longer true. A single authoritative source avoids that risk entirely.