Page 2 · Understand

4-Level Validation Logic Tiers

One scan travels through four tiers before anything is allowed to happen. Each tier asks a single question, and each tier can stop the chain. Nothing is published without a record, and nothing is certified without registration.

ScanIdentityRulesConditionsCondition PublishedRecord
L1

Identity Resolution

Is this a registered QR identity at all?

  • Decoded value resolves to a registry-backed record
  • Identity is not archived or malformed
  • Issuer / company association established

If it failsUnregistered or unresolvable — treated as an ordinary QR, no compliance condition exists.

L2

Rule Application

Which requirements apply here, right now?

  • Applicable protocol rules assembled from governance
  • Jurisdiction, facility and subject scope resolved
  • Rule version in force at scan time captured

If it failsNo applicable rule set — evaluation halts and an exception condition is recorded.

L3

Condition Evaluation

Does the identity satisfy every applicable condition?

  • Registration and certification states verified
  • Expiration, renewal and corrective conditions resolved
  • Enforcement flags and restrictions checked

If it failsOne or more conditions fail — condition drops to conditional, restricted, non-compliant, expired or revoked.

L4

Operational Record

What was decided, and what proves it?

  • Condition published to routing and alerting
  • Scan, inputs and result written to the canonical record
  • Evidence made retrievable for authorised access

If it failsNo record means no compliance. A result that is not recorded is not a validated result.

Validation Result Reference

ResultMeaningRoutingRecord
CompliantAll applicable conditions satisfiedNormal routingStandard record
ConditionalAllowed with outstanding requirementsRequirements surfacedCorrective clock
RestrictedLimited actions permittedRestricted routingOperators notified
Non-CompliantA required condition failedAction blockedEnforcement event
ExpiredValidity period endedBlocked, renewal pathState change logged
RevokedAuthority withdrawnPermanent denialLockout engaged

Key System Relationships

  1. 1 · Root / System Entry

    QuickResponseCode.us

    Public entry point to the QR infrastructure.

  2. 2 · Governance (Rules)

    QRProtocol.us

    Writes and governs the applicable rules.

  3. 3 · Validation

    QRCompliance.us

    Validates compliance readiness against applicable rules and conditions.

  4. 4 · Certification Authority

    QRCertified.us

    Authorizes the QR for certification.

  5. 5 · Registration Result

    QRRegistered.us

    Mandatorily registers the authorized QR.

  6. 6 · Operations / Records

    QRCodex.us

    Records, operates, logs and preserves canonical operational truth.