Route 45 of 176
Conditional Routing
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
Most QR codes point to one fixed destination forever. A conditionally routed identity instead carries a rule set: at the moment of a scan, that rule set is evaluated against the identity's current compliance condition, and the outcome of that evaluation — not a hardcoded link — determines where the scan is sent. The rule and its evaluation logic live with routing; whether the underlying condition being tested is actually satisfied is a question this route hands to validation.
QRCompliance.us supplies the condition that a conditional route depends on. It does not choose the destination, does not hold the routing table, and does not execute the redirect. Determining that a condition is true or false is validation's job; deciding what a true or false result does to a destination is a routing function that sits elsewhere.
A conditional route is built around a simple structure: if a stated condition holds at the moment of the scan, send the scan to destination A; if it does not, send it to destination B, or to a fallback, or to no destination at all. The power of this structure is that it lets a single printed or issued QR code behave differently over its life without ever being reprinted, because the destination was never fixed to the code in the first place — it is computed fresh each time someone scans it.
This differs from simply having several static routes for several static states. A conditional route can combine multiple inputs into one rule — compliance status together with location, or certification standing together with a time window — and can nest conditions so that a secondary check only runs once a primary one has passed. The routing logic itself, including how conditions combine and in what order they are checked, is what this route defines.
The condition tested inside a conditional route is very often a compliance condition: is this identity currently valid, is a required credential still active, has a corrective action been closed out. QRCompliance.us is the layer that answers those specific questions. But the rule that says 'test this condition, and if it fails, route here instead' belongs to routing, and the distinction matters because it keeps a validation layer from quietly becoming the thing that decides where traffic goes.
01Plain-English Definition
Conditional routing is the mechanism by which a QR identity's scan destination is selected at the moment of the scan from a defined rule set, based on the outcome of one or more conditions evaluated against the identity's current state.
A conditional route is not a single link; it is a small decision tree attached to an identity. Each branch of that tree corresponds to a possible outcome of the conditions it tests, and each branch resolves to a destination — a landing page, a redirect target, a hold screen, or an instruction to fall back to a default.
Conditional routing is distinct from simply changing a destination manually after an event occurs. In conditional routing, the branching logic is defined in advance, and the scan-time evaluation is what selects among the pre-defined branches automatically, without a person intervening at the moment of the scan.
02What A Condition Can Reference
A condition inside a conditional route can reference several different kinds of facts, and most real rule sets combine more than one.
- Current compliance status of the identity, as determined by QRCompliance.us at the time of the scan.
- Certification standing held with QRCertified.us, where a route depends on whether authorization remains active.
- Registration standing with QRRegistered.us, since an unregistered identity cannot legitimately resolve at all.
- Time-based facts, such as whether the scan falls inside or outside a defined validity window.
- Location-based facts, such as the jurisdiction or region from which the scan originates.
- Scan-count or usage facts, such as whether a single-use or capped-use identity has already been consumed.
Each of these facts is supplied by the layer responsible for it. Conditional routing does not generate the fact; it consumes a fact that already exists and decides what to do based on its value.
03Practical Value
Conditional routing lets an organization design for outcomes it cannot fully predict at issuance time, without needing to reissue or physically replace a QR code every time circumstances change.
One code, many outcomes
A single printed label can send a scanner to a product page when everything is in order and to a recall notice the moment a condition changes, without swapping the label.
Fewer manual interventions
Because the rule is pre-defined, an operator does not need to manually redirect traffic every time an identity's condition shifts — the rule handles it automatically at scan time.
Layered checks in one route
A route can check compliance status first and, only if that passes, check a secondary condition such as location, avoiding unnecessary evaluation work.
Predictable fallback behavior
A well-formed conditional route always resolves to a defined branch, including a fallback for the case where no other condition matches, so a scan is never left without an outcome.
04Operational Flow
The path from a scan to a resolved destination under conditional routing follows a consistent sequence, regardless of how many conditions the rule set contains.
- 1Scan is receivedThe routing layer receives a scan event referencing a specific registered identity.
- 2Applicable rule set is identifiedThe routing layer looks up the conditional rule set attached to that identity.
- 3Conditions are evaluated in orderEach condition in the rule set is checked, often querying QRCompliance.us or another source of record for the relevant fact.
- 4A branch is selectedThe first condition (or combination of conditions) that resolves determines which branch of the rule set applies.
- 5Destination is resolved and outcome loggedThe scan is sent to the destination defined by the selected branch, and the branch chosen, along with the facts that produced it, is recorded.
A conditional route only ever executes a branch that its rule set already defined. It does not invent a destination on the fly, and it does not decide, on its own, that a condition should be interpreted differently than the rule states.
05Rule Structures
Not all conditional routes are structured the same way, and the structure chosen affects how predictable and auditable the routing behavior is.
| Structure | Behavior |
|---|---|
| Single binary condition | One condition is checked; the route resolves to one of exactly two destinations depending on true or false. |
| Ordered condition chain | Conditions are checked in a defined sequence, and the first one that matches determines the branch, with later conditions never evaluated. |
| Combined condition | Multiple conditions must hold together (all of them, or a defined subset) before a branch is selected. |
| Default fallback branch | A branch that applies only when no other condition in the rule set matches, ensuring the route always resolves. |
An ordered condition chain is common where one check is meant to gate the others — for example, confirming an identity is not revoked before evaluating any secondary, more specific condition at all. Skipping the secondary check when the gating condition fails avoids resolving a scan against conditions that no longer matter.
06When A Condition Cannot Be Resolved
A conditional route depends on being able to obtain the fact a condition tests. When that fact is unavailable — a lookup times out, a source is unreachable, or a value is ambiguous — the route needs a defined answer rather than an undefined one.
| State | Entered When | Left When |
|---|---|---|
| Condition resolves cleanly | The relevant fact is retrieved successfully and evaluated against the rule. | A defined branch is selected and the scan proceeds to its destination. |
| Condition source unreachable | The lookup needed to evaluate a condition cannot be completed within the routing layer's operating limits. | The rule set's declared fallback for an unresolved condition is applied, and the failure is logged distinctly from a normal branch selection. |
| Condition value ambiguous | The fact returned does not clearly match any branch defined in the rule set. | The route treats this as an exception rather than guessing a branch, and resolves to the fallback destination while flagging the ambiguity for review. |
Treating an unresolved condition as its own outcome, rather than silently defaulting to whichever branch happens to be listed first, keeps a routing failure from being mistaken for a legitimate compliance determination.
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.
Conditional routing sits at the point where compliance and other operational facts are converted into a routing decision, and each layer contributes a distinct piece of that process.
| Layer | Relationship To Conditional Routing |
|---|---|
| ROOT — QuickResponseCode.us | Confirms the scanned code corresponds to the identity whose rule set is about to be evaluated, before any condition is checked. |
| GOVERNANCE — QRProtocol.us | Defines which kinds of conditions are permitted inside a rule set and how branches must be structured to be valid. |
| VALIDATION — QRCompliance.us | Supplies the compliance-related facts a rule set tests, such as current status or open corrective conditions, without selecting the destination itself. |
| AUTHORIZATION — QRCertified.us | Supplies certification-standing facts where a rule set conditions its branch on active authorization. |
| REGISTRATION — QRRegistered.us | Confirms the identity remains registered, since routing logic has nothing legitimate to route if registration has lapsed. |
| OPERATIONS — QRCodex.us | Holds the canonical rule set and the record of every branch selected, resolving any dispute about which destination should have applied. |
Where a routing layer's cached rule set conflicts with what QRCodex.us records as the canonical rule set for an identity, Codex governs and the routing layer's copy is corrected.
What This Does — And Does Not — Do
Does
- ✓Define a branching rule set attached to a registered identity that determines its destination at scan time
- ✓Evaluate one or more conditions, drawn from compliance, certification, registration, time, or location facts
- ✓Select among pre-defined branches based on the outcome of those conditions
- ✓Apply a defined fallback branch when no other condition in the rule set matches
- ✓Log which branch was selected and which facts produced that selection
- ✓Treat an unresolved or ambiguous condition as a distinct exception rather than a silent default
Does Not
- ✕Determine on its own whether a compliance condition is actually satisfied — that determination belongs to QRCompliance.us
- ✕Invent a destination that was not already defined in the rule set
- ✕Allow a routing layer to override or reinterpret a compliance fact it receives
- ✕Resolve a scan to a branch without recording the condition outcome that produced it
- ✕Treat a failed lookup the same as a condition that resolved to false
- ✕Route an identity that is not currently registered as if it were
Related Routes
Common Questions
Does QRCompliance.us decide where a conditionally routed scan ends up?
No. QRCompliance.us determines whether a compliance condition referenced by the rule set is currently true or false. Selecting the destination based on that answer is a routing function, not a validation function.
What happens if a conditional route can't reach the source it needs to evaluate a condition?
The rule set's declared fallback branch applies, and the failure is logged distinctly from a normal branch selection so it is never mistaken for a compliance determination.
Can a conditional route test more than one condition at once?
Yes. Rule sets can chain conditions in sequence or require multiple conditions to hold together before selecting a branch.
Is conditional routing the same as manually changing a link after an event?
No. Conditional routing evaluates a pre-defined rule automatically at scan time. Manually changing a link requires a person to intervene after the fact for every affected code.
What happens if two systems disagree about which rule set applies to an identity?
QRCodex.us holds the canonical rule set for the identity. Where a routing layer's copy conflicts with what Codex records, Codex governs and the routing layer's copy is corrected.