Route 46 of 176
Status-Based Routing
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
Status-based routing is the specific and most common form of conditional routing in which the single condition driving the branch is the identity's own status. Where a general conditional route might weigh time, location, and status together, a status-based route keys its decision to one thing: what is the identity's status right now, and which destination has been mapped to that status. QRCompliance.us determines the status. The routing layer holds the mapping from status to destination and carries out the resolution.
Determining that an identity's status is active, restricted, revoked, expired, or under a corrective condition is a validation function performed by QRCompliance.us. Deciding what destination corresponds to each of those statuses, and actually sending the scan there, is a routing function. Status-based routing only works because those two functions stay separate.
Many registered identities pass through a small number of well-defined statuses over their operational life: active, restricted, revoked, expired, or placed under a corrective condition pending resolution. Status-based routing takes that existing vocabulary of statuses and attaches a destination to each one, so that a scan of the identity is sent somewhere different depending on which status currently applies — without anyone needing to write a bespoke rule for every possible circumstance that might produce that status.
The appeal of status-based routing is its simplicity relative to a fully general conditional route. Because the branching variable is always the same — status — the mapping from status to destination can be defined once for an entire category of identities, rather than authored separately for each one. A batch of identical products can share one status-to-destination mapping even though each unit's individual status may diverge over time.
Status-based routing depends entirely on the accuracy and timeliness of the status it reads. If QRCompliance.us has not yet reflected a status change, a status-based route will faithfully resolve to the destination for the old status, because the routing layer has no independent way of knowing the status has moved. This is why status-based routing is closely tied to how quickly a status change propagates once it occurs.
01Plain-English Definition
Status-based routing is a routing mechanism in which the destination a scan resolves to is chosen from a pre-defined mapping keyed to the registered identity's current status, as determined by validation at the moment of the scan.
The mapping itself — which status maps to which destination — is authored and held by the routing layer or the party configuring the identity's behavior. It is not something QRCompliance.us defines; QRCompliance.us's role ends at reporting the status.
Status-based routing is a specialization of conditional routing generally: every status-based route is a conditional route, but not every conditional route is status-based, since a conditional route can branch on facts other than status, such as time or location, either instead of status or in combination with it.
02Common Status-To-Destination Mappings
While the exact destinations chosen vary by organization and use case, certain status-to-destination pairings recur across most status-based deployments.
| Status | Typical Destination |
|---|---|
| Active | The identity's normal informational or transactional destination |
| Restricted | A limited-access page reflecting reduced privileges or a partial hold |
| Revoked | A notice indicating the identity is no longer valid, without exposing normal content |
| Expired | A renewal or reissuance page rather than the expired content itself |
| Under corrective condition | A status page describing the open corrective action and expected resolution path |
None of these destinations is mandatory; the mapping is configurable. What is fixed is that the status itself, and the fact that a mapping exists for every status the identity can hold, come from outside the routing layer.
03Practical Value
Status-based routing gives an organization a consistent, predictable way to translate a compliance state into a scan experience without hand-authoring a route for every individual identity.
- A single mapping can apply across an entire product line, batch, or identity category, reducing configuration effort.
- Because the mapping is keyed to a small, well-understood set of statuses, its behavior is easy to reason about and easy to audit.
- When a status changes, the routing outcome changes automatically at the next scan, without a manual redirect.
- A revoked or restricted identity's scans can be redirected away from normal content immediately once its status reflects that.
04Operational Flow
Resolving a scan under status-based routing follows a short, repeatable sequence built around a single lookup and a single mapping check.
- 1Scan is receivedThe routing layer receives a scan event for a registered identity configured for status-based routing.
- 2Current status is retrievedThe routing layer requests the identity's current status from QRCompliance.us.
- 3Status is matched against the mappingThe returned status is checked against the identity's configured status-to-destination mapping.
- 4Destination is selectedThe destination corresponding to the matched status is chosen; if the status has no explicit entry, a default destination applies.
- 5Scan is resolved and the outcome loggedThe scan is sent to the selected destination, and the status observed together with the destination chosen is recorded.
A status-based route can only ever be as current as the status it reads. If a status change has not yet propagated, the route will resolve correctly against the status it was given — even though that status is now out of date.
05Handling Statuses Outside The Mapping
A status vocabulary can expand over time as new compliance conditions are introduced, and a mapping authored before that expansion may not have an entry for a newly introduced status.
| State | Entered When | Left When |
|---|---|---|
| Status has an explicit mapping entry | The status returned by QRCompliance.us matches one of the entries defined for the identity. | The scan resolves to the destination configured for that entry. |
| Status has no mapping entry | A status is returned that the identity's current mapping does not account for, often because the status vocabulary changed after the mapping was configured. | The scan resolves to a defined default destination, and the unmapped status is flagged so the mapping can be updated. |
| Status cannot be retrieved | The lookup to QRCompliance.us fails or times out before a status is returned. | The scan resolves to a distinct failure destination, separate from any status-based branch, and the failure is logged as a lookup failure rather than a status outcome. |
Keeping an unmapped status and a failed lookup distinct from one another, and both distinct from a normal status match, prevents either condition from being silently absorbed into an ordinary routing outcome.
06Status-Based Routing Compared With General Conditional Routing
Status-based routing is easier to configure and audit precisely because it narrows the branching variable to one thing, at the cost of some of the flexibility a fully general conditional route offers.
| Aspect | Status-Based Routing | General Conditional Routing |
|---|---|---|
| Branching variable | Identity status only | Any combination of status, time, location, usage, or other facts |
| Configuration effort | One mapping can cover many identities sharing a status vocabulary | Often authored per rule set, since conditions and combinations vary |
| Auditability | Straightforward — one status, one destination | More complex, since multiple conditions and their order must be reconstructed |
| Best suited to | Large groups of similar identities with a shared, well-defined status vocabulary | Identities whose routing needs depend on more than status alone |
07System 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.
Status-based routing is the point where a compliance status, determined elsewhere, is turned into a concrete scan destination, and each layer's contribution to that outcome is kept distinct.
| Layer | Relationship To Status-Based Routing |
|---|---|
| ROOT — QuickResponseCode.us | Confirms the scanned code corresponds to the specific registered identity whose status is about to be looked up. |
| GOVERNANCE — QRProtocol.us | Defines the recognized status vocabulary and the rules for how a status-to-destination mapping must be structured. |
| VALIDATION — QRCompliance.us | Determines and reports the identity's current status; it does not hold or apply the mapping from status to destination. |
| AUTHORIZATION — QRCertified.us | Contributes certification-related statuses, such as suspended or withdrawn authorization, where those feed the same status vocabulary. |
| REGISTRATION — QRRegistered.us | Confirms the identity remains registered, since a status-based route has nothing legitimate to resolve for an unregistered identity. |
| OPERATIONS — QRCodex.us | Holds the canonical status-to-destination mapping and the full history of status observed and destination selected for every scan. |
Where a routing layer's local copy of a status-to-destination mapping conflicts with what QRCodex.us records as canonical, Codex governs and the local copy is corrected.
What This Does — And Does Not — Do
Does
- ✓Read an identity's current status from QRCompliance.us at scan time
- ✓Match that status against a pre-defined status-to-destination mapping
- ✓Resolve a scan to the destination configured for the matched status
- ✓Apply a defined default destination when a status has no explicit mapping entry
- ✓Log the status observed and the destination selected as distinct facts
- ✓Treat a failed status lookup as a distinct outcome from any normal status match
Does Not
- ✕Determine an identity's status itself — that determination belongs to QRCompliance.us
- ✕Define the recognized status vocabulary — that is set by governance
- ✕Silently absorb an unmapped status into an existing branch without flagging it
- ✕Treat a failed lookup as equivalent to a specific status value
- ✕Allow the routing layer to override a status it receives from validation
- ✕Resolve a scan for an identity that is not currently registered
Related Routes
Common Questions
How is status-based routing different from conditional routing generally?
Status-based routing is a conditional route in which the only variable driving the branch is the identity's status. General conditional routing can branch on status combined with other facts such as time, location, or usage.
Who decides what destination corresponds to a given status?
The party configuring the identity's routing defines the mapping. QRCompliance.us determines the status itself but has no role in choosing which destination that status maps to.
What happens if a status is reported that the mapping doesn't recognize?
The scan resolves to a defined default destination, and the unmapped status is flagged for review so the mapping can be updated to account for it.
Can a status change be reflected before the routing layer knows about it?
Status-based routing can only resolve against the status it is given at scan time. Its accuracy depends on how quickly a status change propagates from validation to the routing layer.
Is a failed status lookup treated as a specific status, like revoked?
No. A failed lookup is logged and resolved as a distinct failure outcome, separate from any specific status value, so it is never mistaken for a genuine status determination.