Route 129 of 176
Restricted QR Identity
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
A registered identity is not always simply valid or invalid. Between those two poles sits a condition where the identity remains genuinely registered and generally usable, but a specific slice of its routing, access, or use has been narrowed — a jurisdiction excluded, a channel disabled, a use case blocked — while everything outside that slice continues to function normally. This route defines what makes an identity 'restricted' rather than revoked, how the scope of a restriction is expressed and validated, and how a restricted condition is distinguished from other failure and exception states nearby.
QRCompliance.us validates whether a restriction applies to a given scan or lookup, and against what scope. It does not decide to impose the restriction, does not remove it, and does not itself block the scan that falls within the restricted scope — it determines the condition and reports it to the layer that acts.
Not every limitation on a QR identity is total. A product line might remain compliant everywhere except one jurisdiction where a specific labeling requirement has not been met. A credential holder might remain authorized for most functions but barred from one high-risk activity pending a review. A batch might be cleared for domestic distribution but restricted from export until a separate certification catches up. In each case, the identity is neither fully valid nor fully revoked — it is restricted, and the restriction has a shape.
That shape matters enormously to how the condition is handled downstream. A blanket revocation tells every consuming system to treat the identity as invalid everywhere. A restriction tells consuming systems something more precise: treat this identity as valid outside a defined scope, and as failing only within it. Getting that scope wrong in either direction causes real harm — too narrow, and a genuinely non-compliant use slips through; too broad, and legitimate activity is blocked for no reason tied to any actual condition.
This route exists because 'restricted' is frequently confused with 'revoked' in casual usage, and that confusion is exactly what the architecture is built to prevent. A restricted QR identity retains its registration and its general validity. Its restriction is a scoped condition that QRCompliance.us evaluates against the specific scan, lookup, or use being asked about — not a global switch that turns the identity off.
01Plain-English Definition
A restricted QR identity is a registered identity whose validity is intact outside a defined scope, but which fails compliance evaluation for any scan, lookup, or use that falls within that scope — a jurisdiction, a channel, a use case, or another bounded category.
The defining feature of a restriction is its boundary. Somewhere in the record is a statement of exactly what the restriction covers — a jurisdiction code, a channel identifier, a category of use — and every evaluation checks the incoming scan or lookup against that boundary rather than against the identity as a whole.
A restriction is not a lesser or informal version of a revocation. It is a distinct condition with its own scope, its own basis, and its own review path. An identity can carry a restriction indefinitely without ever escalating to revocation, provided the restricted scope continues to be honored.
02What Makes A Restriction Different
Several nearby conditions are easy to conflate with restriction, and the distinctions are load-bearing for how a scan is handled.
- A revoked identity fails everywhere, for every scan and lookup, without regard to scope — a restricted identity fails only inside its defined scope.
- An expired identity has passed a time boundary that applies uniformly, while a restriction's boundary is typically categorical (jurisdiction, channel, use) rather than purely temporal.
- A restriction can itself have an expiry — a scope that lifts on a fixed date — but the two conditions are tracked separately and are not assumed to be the same mechanism.
- A restriction differs from a corrective condition in that a corrective condition anticipates resolution through a defined remediation step, while a restriction may persist as a standing limitation with no remediation pending.
- Multiple restrictions can apply to the same identity simultaneously, each with its own independent scope, basis, and review status.
03Practical Value
Scoped restriction gives the system a way to respond proportionately to a limited compliance gap without discarding an identity's overall standing.
Proportionate response
A single jurisdiction's unmet requirement blocks only that jurisdiction's scans, leaving legitimate activity elsewhere unaffected.
Precise remediation target
Because the scope is explicit, the responsible party knows exactly what must change to lift the restriction, rather than facing an undifferentiated failure.
Preserved registration
The identity does not need to be re-registered or re-issued to carry a restriction; the underlying registration remains intact throughout.
04Operational Flow
A restriction moves through a defined sequence from the moment its scope is established to the moment a specific scan is evaluated against it.
- 1Scope is definedThe basis for the restriction and the exact category it covers — jurisdiction, channel, use case, or another bounded dimension — is recorded.
- 2Restriction is recorded against the identityThe identity's condition record is updated to reflect an active restriction with its scope and basis, without altering its general validity.
- 3A scan or lookup occursA request arrives asking whether the identity is valid for a specific context — a jurisdiction, a channel, or a use.
- 4The request is checked against the scopeQRCompliance.us compares the context of the request to the recorded scope of the restriction to determine whether this particular scan falls inside or outside it.
- 5The condition is reportedQRCompliance.us reports whether the identity is valid for this specific request, restricted for it, or unaffected, and the consuming layer proceeds accordingly.
A restriction is only meaningful if its scope is checked against the specific request being made. A blanket answer of 'restricted' with no reference to scope tells a consuming system nothing useful.
05Restriction States
A restriction moves through its own lifecycle, separate from the identity's overall registration lifecycle.
| State | Entered When | Left When |
|---|---|---|
| Proposed | A basis for restricting a defined scope has been submitted for evaluation | Confirmed once evaluation supports the scope and basis, or dismissed if it does not |
| Active | Evaluation has confirmed the restriction and its scope | Reviewed on a scheduled basis or upon new evidence bearing on the scope |
| Under review | New evidence or a scheduled review has been triggered against an active restriction | Restriction is upheld, narrowed, widened, or lifted based on the review outcome |
| Lifted | Review determines the basis for the restriction no longer holds | Identity resumes full validity for the formerly restricted scope |
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.
A restricted QR identity sits at the point where validation's scoped determination meets the layers that hold the identity, authorize its use, and act on the scan.
| Layer | Relationship To Restricted QR Identity |
|---|---|
| ROOT — QuickResponseCode.us | Confirms the restricted identity is the same identity throughout, with its scope of restriction attached rather than a new or substitute identity. |
| GOVERNANCE — QRProtocol.us | Defines which categories of scope — jurisdiction, channel, use case — are recognized as valid dimensions for a restriction. |
| VALIDATION — QRCompliance.us | Evaluates whether a specific scan or lookup falls within a restriction's recorded scope and reports the resulting condition. |
| AUTHORIZATION — QRCertified.us | Reflects a restriction's scope in the certified status presented for the affected use, without withdrawing certification outside that scope. |
| REGISTRATION — QRRegistered.us | Holds the restriction as part of the identity's registered record and enforces it against the scoped access it controls. |
| OPERATIONS — QRCodex.us | Retains the full history of a restriction's scope, basis, review outcomes, and any lifting as the permanent operational record. |
Where a consuming layer's treatment of a restriction's scope conflicts with what QRCodex.us has recorded, Codex governs and the treatment is corrected to match it.
What This Does — And Does Not — Do
Does
- ✓Define an explicit scope — jurisdiction, channel, use case, or another bounded category — for every restriction
- ✓Evaluate a specific scan or lookup against the recorded scope rather than against the identity as a whole
- ✓Preserve an identity's general validity and registration outside the restricted scope
- ✓Track a restriction's own lifecycle — proposed, active, under review, lifted — separately from revocation or expiry
- ✓Support multiple simultaneous restrictions on the same identity, each with independent scope and basis
- ✓Record the basis, scope, and review history of every restriction as a distinct, auditable entry
Does Not
- ✕Treat a restriction as equivalent to a full revocation of the identity
- ✕Allow QRCompliance.us to impose, lift, or enforce a restriction directly
- ✕Apply a restriction's consequence to scans or lookups outside its recorded scope
- ✕Assume a restriction expires purely on a time boundary unless a time-bound scope was explicitly recorded
- ✕Merge separate restrictions with different bases into a single undifferentiated condition
- ✕Discard a restriction's history once it is lifted
Related Routes
Common Questions
Is a restricted QR identity the same as a revoked one?
No. A revoked identity fails everywhere. A restricted identity remains valid outside its defined scope and fails only for requests that fall inside that scope.
Can an identity carry more than one restriction at a time?
Yes. Each restriction has its own independent scope, basis, and review status, and multiple restrictions can be active on the same identity simultaneously.
Does a restriction automatically expire?
Only if a time-bound scope was explicitly recorded for it. Otherwise a restriction persists as a standing limitation until a review lifts, narrows, or widens it.
Who decides whether a restriction applies to a specific scan?
QRCompliance.us evaluates whether the scan's context falls within the restriction's recorded scope and reports the result. It does not itself block the scan.
What happens once a restriction is lifted?
The identity resumes full validity for the formerly restricted scope, and the restriction's full history — basis, scope, and review outcome — remains in the permanent record.