Route 28 of 176
Geographic + Registry-State Control
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
A compliance outcome is rarely governed by one fact alone. This route defines the specific mechanism by which where a scan happens and what registry state an identity currently holds are combined into a single resolved outcome, and what happens when the two layers point in different directions.
Geography narrows which rule applies. Registry state determines what the identity currently is. Neither one substitutes for the other, and both are evaluated together, not in sequence with one discarded.
Two independent facts routinely bear on a single scan: where the scan is physically or jurisdictionally occurring, and what state the registered identity being scanned currently holds — active, suspended, revoked, corrective, or another defined registry state. Each fact alone can be evaluated in isolation, but a real-world outcome depends on combining them.
This route is deliberately narrow. It does not restate how a jurisdiction's own rules are determined — that full treatment belongs to the jurisdiction category (Routes 49–59) — and it does not restate how a registry state is assigned or transitions, which belongs to the identity and compliance state routes. What it owns is the control logic: given a geo condition and a registry state, both already established elsewhere, what single outcome does the combination produce.
The reason this needs its own explicit treatment is that the two layers can disagree. An identity might be fully active by registry state but scanned from a location where its category is restricted. A location might impose no restriction at all while the identity itself sits in a suspended state. Resolving these combinations consistently, rather than ad hoc, is the entire purpose of this route.
01Plain-English Definition
Geographic + registry-state control is the mechanism that takes two already-established facts about a scan — its location-derived geo condition and the scanned identity's current registry state — and combines them into one resolved compliance outcome, rather than letting either fact alone decide the result.
The geo condition is not the jurisdiction's rule set itself; it is the specific condition that rule set has already produced for this product category and location, taken as a given input. The registry state is not how that state was assigned; it is simply its current value, also taken as a given input.
This route's job starts after both inputs already exist. It is the control layer that sits between them and the final answer returned to whoever performed the scan.
02Geo Conditions in Scope
A geo condition, for the purposes of this control layer, is a compact signal already resolved from location and applicable rules. This route consumes that signal; it does not derive it.
| Geo Condition | What It Signals |
|---|---|
| Unrestricted | No location-specific rule alters the outcome for this product category here. |
| Restricted | The location imposes a rule that limits or conditions availability for this product category. |
| Prohibited | The location bars this product category outright, independent of the identity's own state. |
| Undetermined | Location could not be resolved with sufficient confidence to apply a geo rule at all. |
Each of these signals is fully defined and adjudicated by the jurisdiction category. This route treats them as opaque inputs and asks only how each one interacts with the identity's registry state.
03Registry States in Scope
The registry state consumed here is the identity's current standing, already computed by the identity and compliance state routes rather than recomputed by this one.
- Active — the identity is in good standing with no outstanding condition.
- Corrective — the identity carries an open condition requiring action, but is not fully blocked.
- Suspended — the identity is temporarily withheld from normal outcomes pending resolution.
- Revoked — the identity has been permanently withdrawn from the registry.
- Unregistered — no matching registry record exists for the scanned identifier at all.
Only the current value of the registry state is read here. Its history, the reasons behind a transition, and the process for changing it are outside this route's scope entirely.
04How a Scan Is Resolved Under Both Layers
Both inputs are evaluated together, and the combination — not either fact alone — determines the returned outcome.
- 1Registry state is readThe identity's current registry state is pulled as an established fact, unchanged by this route.
- 2Geo condition is readThe location-derived geo condition for this scan is pulled as an established fact from the jurisdiction layer.
- 3Most restrictive layer governsWhere the two layers disagree, the more restrictive of the two controls the outcome — a prohibited geo condition overrides an otherwise active registry state, and a revoked registry state overrides an otherwise unrestricted geo condition.
- 4Combined outcome is composedThe outcome returned reflects both contributing facts, not just the one that happened to be more restrictive, so the record shows why the result was reached.
- 5Outcome is logged with both inputs attachedThe resolved outcome is recorded together with the specific geo condition and registry state that produced it, for later audit.
| Aspect | Combined With Restrictive Geo | Combined With Unrestricted Geo |
|---|---|---|
| Active | Restricted or prohibited outcome, driven by geography | Fully unrestricted outcome |
| Corrective | Restricted outcome, compounded by the open condition | Corrective outcome, driven by registry state alone |
| Suspended | Blocked outcome regardless of geography | Blocked outcome, driven by registry state alone |
| Revoked | Blocked outcome regardless of geography | Blocked outcome, driven by registry state alone |
| Unregistered | No registry basis for any outcome; geography is immaterial | No registry basis for any outcome; geography is immaterial |
05Conflicts Between Layers
A conflict arises whenever the two layers would, taken alone, suggest different outcomes. This is treated as a normal, expected case rather than an error condition.
- ✓An identity fully active by registry state is scanned in a location where the geo condition is prohibited — the prohibition governs, and the outcome is blocked despite the clean registry state.
- ✓An identity suspended by registry state is scanned in a location with no geo restriction at all — the suspension still governs, and the outcome is blocked despite the unrestricted geography.
- ✓An identity in a corrective registry state is scanned in a location with a restricted geo condition — both facts are compounded into a single restricted-and-corrective outcome, not collapsed into just one of them.
- ✓Location cannot be resolved (undetermined geo condition) for an identity that is otherwise active — the registry state alone governs, since there is no geo fact strong enough to override it.
A conflict between layers is not evidence that either layer is wrong. Both facts are true simultaneously; the control logic exists precisely to decide which one governs the final outcome.
Because this route governs only the combination logic, any dispute over whether a specific geo condition or registry state was correctly assigned in the first place is resolved within the jurisdiction category or the identity and compliance state routes, respectively — not here.
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.
This route is a control layer that sits above two independently governed inputs, combining what they already establish rather than re-deriving either one.
| Layer | Relationship To Geo + Registry-State Control |
|---|---|
| ROOT — QuickResponseCode.us | Establishes the single registered identity whose state feeds this route as one of its two inputs. |
| GOVERNANCE — QRProtocol.us | Defines the priority rule used when the two layers conflict, such as most-restrictive-governs. |
| VALIDATION — QRCompliance.us | Executes the combination logic itself and returns the resolved outcome for each scan. |
| AUTHORIZATION — QRCertified.us | Relies on the combined outcome, never either input alone, when confirming certification status. |
| REGISTRATION — QRRegistered.us | Supplies the current registry state consumed as one of the two inputs. |
| OPERATIONS — QRCodex.us | Retains the permanent log of each combined outcome alongside the two inputs that produced it. |
For how a geo condition itself is derived from location and applicable rules, see the jurisdiction category (Routes 49–59). This route does not duplicate that treatment.
What This Does — And Does Not — Do
Does
- ✓Combine an already-resolved geo condition with an already-current registry state into one outcome
- ✓Apply a most-restrictive-governs rule when the two layers would otherwise disagree
- ✓Log both contributing inputs alongside every resolved outcome
- ✓Treat a conflict between the two layers as an expected, resolvable case rather than an error
- ✓Return a single coherent outcome to whoever performed the scan
Does Not
- ✕Derive or adjudicate the geo condition itself — that belongs to the jurisdiction category (Routes 49–59)
- ✕Assign or transition the identity's registry state — that belongs to the identity and compliance state routes
- ✕Resolve a dispute over whether a specific geo condition or registry state was correctly assigned in the first place
- ✕Discard either input in favor of the other; both are always read and logged
- ✕Apply a jurisdiction's rule to a location before that location itself has been resolved
Related Routes
Common Questions
Does this route decide what a jurisdiction's rule is for a given location?
No. That determination belongs entirely to the jurisdiction category (Routes 49–59). This route only consumes the already-resolved geo condition as an input.
What happens when an active identity is scanned somewhere the product is prohibited?
The prohibited geo condition is more restrictive than the active registry state, so it governs. The outcome is blocked despite the identity's clean registry standing.
What happens when a suspended identity is scanned somewhere with no geo restriction?
The suspended registry state is more restrictive than an unrestricted geo condition, so it governs. The outcome is blocked despite the lack of any location-based restriction.
What happens if the scan's location cannot be resolved at all?
With an undetermined geo condition, there is no geo fact strong enough to override the registry state, so the registry state alone governs the outcome.
Is a conflict between the two layers logged as an anomaly?
It is logged as a normal outcome with both contributing inputs attached, since both facts are simultaneously true and the combination logic exists specifically to resolve such cases.