QR Scan Protocol | The QR Operating Sequence

Operating Sequence

Define the ordered sequence a governed QR interaction follows from scan through recorded outcome.

Marked for Protocol review

Terminology under review. Established vocabulary supported by source material includes scan, register, certify, authorize, validate, activate, verify, route and record. The steps 'Recognize' and 'Qualify' shown below originate in earlier site material and have not been reconciled with the approved Protocol vocabulary. They are published as descriptive site content, not as authoritative Protocol states, pending review.

Protocol Family: Operations
Status: Published
Version: 1.0
Effective Date: 2026-08-12
Related Department: QRProtocol.us
Scope: All governed QR interactions across all infrastructure interactions.
Purpose: Define the ordered sequence a governed QR interaction follows from scan through recorded outcome.
Dependencies: doctrine

The scan is an event.

A scan does not automatically determine what happens next. Protocol does.

Scan

An interaction with the QR object begins.

Recognize

Determine what QR object or event the system has encountered.

Qualify

Determine whether the object and interaction satisfy conditions required to proceed.

Authorize

Determine whether the requested action, actor or system has authority to continue.

Activate

Initiate the permitted command, route or system action.

Route

Direct the interaction through the authorized pathway.

Execute

Perform the authorized action.

Confirm

Determine whether execution completed as required.

Record

Create the appropriate event record for attribution, history, evidence and audit.

* This sequence is important and must remain intact across all infrastructure interactions.

Definition

The scan is an event. A scan does not automatically determine what happens next. Protocol does.

Governing Rule

This sequence is important and must remain intact across all infrastructure interactions.

Procedure Summary

Descriptive sequence, exact ordering under review: Scan → Recognize → Qualify → Authorize → Activate → Route → Execute → Confirm → Record. 'Recognize' and 'Qualify' are legacy descriptive labels, not authoritative Protocol states.

Exceptions

Where a step cannot complete, the interaction is handled under Failures & Exceptions rather than proceeding.

What it governs

— The order in which a governed QR interaction is evaluated
— Which conditions must be satisfied before an action is permitted
— What must occur when a step cannot complete

Permitted

— Continuing to the next step only when the current step completes
— Recording the outcome of the interaction where required

Not permitted

— Skipping evaluation because a scan occurred
— Executing an action before authorization is determined
— Substituting new sequence states without supporting source material

When the condition passes: The interaction proceeds and the outcome is recorded where required.
When the condition fails: The interaction is routed to Failures & Exceptions and does not continue through the sequence.
Department performing the operation: Protocol defines the sequence. Registration is performed by QRRegistered.us, certification by QRCertified.us, and compliance evaluation by QRCompliance.us.
Record / evidence required: An event record sufficient to reconstruct the interaction and its outcome.
Where the operational record lives: QRCodex.us.