Connected Infrastructure
Departments of the QR system
Each domain holds a distinct, bounded jurisdiction. Nothing overlaps, and no department substitutes for another.
Registry
Department directory
QuickResponseCode.us
Root — the system itself
QuickResponseCode.us is the root of the system and the master public reference and gateway. Every other layer exists in relation to the Quick Response Code and the scan interaction it makes possible.
Operational department
QRProtocol.us
Governance — writes and governs the rules
QR Protocol writes and governs the rules, standards and governance that determine how applicable QR-system operations are permitted to function. Protocol authors the rules; it does not enforce them.
Operational department
QRCompliance.us
Enforcement — enforces the rules Protocol writes
QR Compliance enforces the rules QR Protocol writes. Compliance can enforce only what Protocol has published; it authors nothing.
Established department — site not completed
QRCertified.us
Authority — authorizes, verifies, proves
QR Certified authorizes, verifies and proves. It is the certification authority of the system and the only path to a registered QR code — nothing reaches registration without passing through certification.
Operational department
QRRegistered.us
Result — the registered outcome
QR Registered issues the registered result — the registration identity that makes a QR operationally recognized. A registered QR code is only reachable through QR Certified.
Operational department
QRCodex.us
Operations — the system artery
QRCodex is the main operational artery of the system. It logs, records, organizes, manages and facilitates all system actions, and it is fully functional system-wide. The other domains remain passive in accordance with it.
Operational department
Jurisdiction Matrix
What each department does — and does not do
The boundary is as important as the function. A department that performs another department's job destroys the review structure.
| Domain | Performs | Does not perform |
|---|---|---|
| QuickResponseCode.us | Root of the system — public reference and gateway | Does not write rules, enforce, certify or register |
| QRProtocol.us | Governance — writes and governs the rules, standards and recording requirements | Does not enforce, certify, register or hold records |
| QRCompliance.us | Enforcement — enforces the rules Protocol writes | Cannot write rules; does not certify or register |
| QRCertified.us | Authority — authorizes, verifies and proves; the only path to registration | Does not write rules, enforce or perform registration |
| QRRegistered.us | Result — issues the registered QR identity | Not reachable except through QRCertified; does not certify or write rules |
| QRCodex.us | Operations artery — logs, records, organizes, manages and facilitates all system actions | Does not write rules, enforce, certify or register |
System Flow
How the departments interact
Connected — not collapsed. Each step is performed by the authority that owns it.
- 01
Root — the Quick Response Code
QuickResponseCode.us is the root of the system. The scan interaction is the entry event that the rest of the system exists in relation to.
- 02
Governance — rules are written
QRProtocol writes and governs which conditions must be evaluated, what may occur, what may not, and which events must be recorded. Protocol writes; it does not enforce.
- 03
Enforcement — rules are enforced
QRCompliance enforces the rules Protocol wrote. Compliance can enforce only published rules and cannot author any of them.
- 04
Authority — certification proves
QRCertified authorizes, verifies and proves. This is the required gate: no registered result exists without passing through certification.
- 05
Result — registration is issued
QRRegistered issues the registered result only after certification, producing the registered QR identity the system can operate on.
- 06
Operations — the Codex artery
QRCodex runs throughout, logging, recording, organizing, managing and facilitating every action so any past interaction can be reconstructed. QRCodex.us is fully functional system-wide.
Answers
Ecosystem questions
What is the canonical order of the QR system?
QuickResponseCode.us (root) → QRProtocol.us (governance) → QRCompliance.us (enforcement) → QRCertified.us (authority) → QRRegistered.us (result), with QRCodex.us as the continuous operational artery.
Can a QR code become registered without QR Certified?
No. Certification is the only path to registration. QRCertified authorizes, verifies and proves; only then does QRRegistered issue the registered result.
What is the difference between QR Protocol and QR Compliance?
QR Protocol writes and governs the rules. QR Compliance enforces them. Protocol cannot enforce and Compliance cannot write.
Which department holds the record of what happened?
QRCodex. It is the main operational artery — it logs, records, organizes, manages and facilitates all system actions, and holds the authoritative record, dossier, state and event history.
Do the domains work individually?
Each domain functions individually in its own defined role, but individually they do not constitute the system. The system exists only through their coordinated relationship.
Are all departments live?
QRCodex.us is fully functional system-wide. QRCompliance is an established department whose independent website and system are not completed; no compliance functionality is implemented on QRProtocol.us and none is claimed as live.