Contact
Route your inquiry correctly
Protocol governs rules. Registration, certification and operational records are handled by their own departments — routing your inquiry to the correct authority resolves it faster.
Triage
Identify the inquiry type first
Every request belongs to exactly one jurisdiction. Determine which before sending.
Protocol interpretation
A question about what a published rule permits, requires or excludes. Include the document slug and the operational scenario in question.
Routes to QRProtocol.us
Documentation request
A rule you require that is not yet published. Include the department involved and the interaction that has no governing instrument today.
Routes to QRProtocol.us
Registration
Obtaining or questioning a registration identity for a QR object. Protocol does not perform registration and cannot issue an identity.
Routes to QRRegistered.us
Certification
Whether applicable certification requirements have been satisfied. Protocol does not make certification determinations.
Routes to QRCertified.us
Operational record
A question about what happened to a specific QR object — its state, dossier, event history or evidence. That resolves to the record, not to documentation.
Routes to QRCodex.us
Compliance
Evaluation of applicable requirements. QRCompliance is an established department whose independent system is not completed.
Routes to QRCompliance.us
Routing
Where to direct each request
- Visit domain
QuickResponseCode.us
Root — the system itself
- Visit domain
QRCompliance.us
Enforcement — enforces the rules Protocol writes
- Visit domain
QRCertified.us
Authority — authorizes, verifies, proves
- Visit domain
QRRegistered.us
Result — the registered outcome
- Visit domain
QRCodex.us
Operations — the system artery
Submission
What to include
A well-formed inquiry states the interaction, not the impression. These fields let a request be evaluated against the governing rule directly.
- — The department the request concerns
- — The Protocol document or page the question relates to
- — The operational scenario, stated as an interaction rather than an opinion
- — The outcome expected and the outcome observed, where they differ
- — Whether the request concerns a rule, a record or a determination
Documentation
Requesting a Protocol document
The Protocol framework expands as infrastructure is documented. If a rule you require is not yet published, submit the operational scenario and the department involved.
Can QR Protocol register or certify my QR code?
No. Registration is performed by QRRegistered.us and certification by QRCertified.us. QR Protocol publishes the governing rules and performs neither operation, so requests of that kind are routed rather than answered here.
Who do I contact about a specific QR object's history?
QRCodex.us. The authoritative operational record, dossier, state and event history are maintained there. Protocol documentation describes the rules, not what happened to an individual object.
How do I request a Protocol document that does not exist yet?
Submit the operational scenario and the department involved. The framework expands as infrastructure is documented, and new instruments enter the hierarchy at their defined level.
What is the fastest way to get an inquiry resolved?
Route it to the department that owns the function. A registration question sent to the governance department is a routing error, and correcting it costs more time than sending it correctly the first time.