Enforcement — enforces the rules Protocol writes
QRCompliance.us
QR Compliance enforces the rules QR Protocol writes. Compliance can enforce only what Protocol has published; it authors nothing.
QRCompliance is the enforcement layer. It enforces the rules QR Protocol writes.
Compliance can enforce only what Protocol has published. Compliance writes nothing, governs nothing, certifies nothing and registers nothing — the separation between authorship and enforcement is structural, not stylistic.
Its independent website and system are not completed. No compliance functionality is implemented on QRProtocol.us and none is claimed as live.
Responsibilities
- — Enforces the published Protocol rules
- — Evaluates applicable requirements against enforced rules
Boundaries
- — QRCompliance cannot write rules
- — QRCompliance does not certify
- — QRCompliance does not register
- — Its independent website/system is not completed
Status: Established department — site not completed
How it interacts with the system
- Enforces the rules written by QRProtocol
- Enforcement applies across the certification path operated by QRCertified
- Enforcement events are logged within QRCodex where applicable
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.
Is QR Compliance live?
QR Compliance is an established department, but its independent website and system are not completed. No compliance functionality is implemented on QRProtocol.us and none is claimed as live.
Read next
Protocol governs the rules. QR Compliance operates within its own jurisdiction.