Vertical Application
THCProtocol Vertical Application
THCProtocol is a vertical application of the QR Protocol framework for a regulated product environment. It introduces no new authority — it applies existing Protocol rules within a specific operational domain.
A vertical does not create authority. It inherits it.
THCProtocol operates under the same doctrine, hierarchy and operating sequence published by QR Protocol.
Framing
THCProtocol did not become QR Protocol
THCProtocol is a cannabis vertical used to demonstrate and apply QR Protocol logic. QR Protocol is universal. The vertical did not evolve into the framework; the framework is applied within the vertical.
Cannabis was used because it provides a demanding operational environment. The requirements are concrete, the evidence is external, and failure has consequences — which makes it a useful proving ground for governed QR behavior.
Rules that are specific to this vertical remain specific to it. Cannabis-specific requirements are not automatically converted into universal QR Protocol requirements.
- COAs
- Laboratories
- Batches
- Lineage
- Chain of custody
- Certification
- Compliance
- Expiration
- Revocation
- Recall
- Audit evidence
Applied Framework
How Protocol applies in this vertical
Registered Identity
Each governed item carries a registered QR identity, recognized at scan time before any action is evaluated.
State Control
Product state — active, held, suspended, recalled, retired — determines which actions are permitted.
Routing
Scan events route to the correct authorized destination based on identity, state and requesting context.
Exception Handling
Denials, unknown identities and failed conditions follow defined exception procedures rather than silent failure.
Audit Recording
Every scan, decision and state change is recorded so operational history remains reviewable.
Field Procedure
Media production, placement, inspection, replacement and retirement follow physical asset domain procedure.
Boundaries
What THCProtocol does not do
- It does not perform registration — QR Registered does
- It does not issue certification — QR Certified does
- It does not hold the operational record — QRCodex does
- It does not override Protocol rules or create exceptions to them
