Protocol Framework
QR Protocol governs the rules of operation
Protocol is the governing authority for rules operating within the QR system. It publishes standards, procedures, state conditions, routing rules, exception handling and recording requirements.
Jurisdiction
What Protocol governs — and what it does not
Protocol governs
- — Rules, standards and operating procedures
- — Permitted actions and conditions of authorization
- — State conditions that govern operation
- — Routing rules across connected domains
- — Exception and failure handling
- — Recording and audit requirements
Protocol does not
- — Hold the operational record — that is QRCodex
- — Operate a registry — that is QR Registered
- — Issue certification — that is QR Certified
- — Replace or duplicate any department's jurisdiction
Departmental Function
Protocol governs rules. Departments perform operations.
Protocol may govern rules affecting another department without performing that department's operational function. The distinction is deliberate and is never collapsed.
| Protocol establishes | Department performs | Record lives |
|---|---|---|
| Rules governing registration | QRRegistered.us performs registration | QRCodex.us |
| Rules affecting certification | QRCertified.us performs certification | QRCodex.us |
| Compliance-related requirements | QRCompliance.us handles compliance | QRCodex.us |
| Recording requirements | QRCodex.us maintains records, dossiers and evidence | QRCodex.us |
What is QR Protocol?
QR Protocol is the rules, standards and governance department of the QR system. It publishes the documentation that determines how applicable QR-system operations are permitted to behave.
Does Protocol replace the other departments?
No. Protocol does not replace QRCodex, QRRegistered, QRCertified or QRCompliance. It governs applicable rules; each department performs its own operation.
Published Documents
Protocol families
Documents are grouped by the area of the system they govern. The framework is expandable — new documents are added as the infrastructure is documented.
Audit
Field Operations
Governance
Core Doctrine
Establish the foundational operating doctrine that determines what the QR system does after a QR interaction begins.
Published · v1.0
Protocol Hierarchy
Organize governance instruments so that each carries a defined function and authority level.
Published · v1.0
System Progression
Document the departmental progression from a generated QR code to a Registered QR Code operating in the Codex environment.
Published · v1.0
Scope & Jurisdiction
State what QR Protocol governs, what it does not govern, and which department performs each operation.
Published · v1.0
Terminology Control
Hold the vocabulary of the QR system fixed so that terms carry the same meaning across every department and document.
Published · v1.0
Network
Operations
Operating Sequence
Define the ordered sequence a governed QR interaction follows from scan through recorded outcome.
Published · v1.0
State Control
Define the conditions Protocol evaluates before permitting system behavior.
Published · v1.0
Operational Lifecycle
Govern the QR object across its operational lifecycle, not only at the scan.
Published · v1.0
Authorization
Establish the rule that a governed QR action proceeds only when the requesting actor, system or action holds the authority required to continue.
Published · v1.0
Validation
Establish the rule that the data, condition or evidence presented must satisfy the applicable requirement before an action proceeds.
Published · v1.0
Verification
Establish the rule that a claimed identity, record or condition must correspond to what the system holds.
Published · v1.0
Activation & Execution
Establish the rule that only a permitted command, route or system action may be initiated, and that its completion must be confirmed.
Published · v1.0
Revocation & Expiration
Establish how operational authority ends, and what survives after it ends.
Published · v1.0