The license lives or dies on the security plan.
Every cannabis establishment in New Mexico stands or falls on 16.8.2 NMAC. We build security compliance packages straight from the statute — every camera, lock, log, and procedure traced to the rule it satisfies. The regulation is the spec.
Fixed price · Ten business days · Revised free until accepted- i.Limited-access areas16.8.2.10 · intro, J✓
- ii.Security alarm system16.8.2.10 · A–C✓
- iii.Video surveillance16.8.2.10 · D–E✓
- iv.Recording & retention16.8.2.10 · F–G✓
- v.Incident response16.8.2.8 · M✓
- vi.Diagrams & amendments16.8.2.24 / .32 / .38✓
Fig. 01 · The package, assembling itself
The Receipts.
Every number below is the statute — in the open, not buried in the notes.
Minimum camera resolution, every camera, permanently mounted and fixed.
16.8.2.10(D) NMACMinimum frame rate — continuous 24 hours, or motion-activated.
16.8.2.10(F)(1) NMACFootage retention — thirty days standard, twelve months after any incident.
16.8.2.10(F)(3) NMACAlarm alert window to designated employees — and law enforcement if necessary.
16.8.2.10(A) NMACDeadline to report any theft, robbery, break-in, or breach to the Division.
16.8.2.8(M) NMACLit, camera-recordable radius required at every perimeter entry point.
16.8.2.10(L) NMACThree ways in. One standard.
Applying, operating, or preparing to be inspected — the package meets you where the Division will.
License Application Security Plan
The complete security exhibit for your application, built from the rule text.
- Full facility security plan
- Surveillance & alarm specifications
- Required SOPs and training docs
- Citation index for the reviewer
- Revised free until accepted
Operational Compliance Package
For licensed operators: close every gap between how you run and what the rule requires.
- Scored gap assessment vs. the statute
- Remediation plan, prioritized by risk
- Updated SOPs, logs, and signage
- Deficiency-notice response support
- Staff walkthrough & handoff
Audit-Ready Retainer
Quarterly assurance that your posture matches the current rulebook.
- Quarterly mock inspections
- Rule-change monitoring & alerts
- SOP and document upkeep
- New-hire security training
- Priority response on notices
The tool that refuses to file a mistake.
Themis is our in-house compliance engine — the rulebook, decomposed into a requirement map with the statute’s own floors wired in as validation. Try the builder yourself, or we’ll show it to you live on the first call. Watching it reject a non-compliant input is the whole pitch.
- Statutory floors, enforced in code
Enter a 20-day retention period or a 12-fps camera and Themis refuses the entry — citing the subsection and the floor you missed. A package below the statute cannot be produced. Not "shouldn’t." Cannot.
- Nothing skipped silently
Every requirement resolves as compliant or not-applicable — and N/A demands a written justification that prints into the package the reviewer reads.
- Generation gated at 100%
The package will not generate until every requirement is resolved. An incomplete filing is not an output the system can express.
- Every line carries its citation
The finished package is a citation-mapped dossier — timestamped, versioned, and traceable to the exact rule each section satisfies.
- Rule changes get checked backward, not just forward
When the rule map updates, run a backward compliance pass and Themis re-checks every package you've already signed off on — flagging anything the amendment knocked out of compliance, not just what you file next.
While mapping the current rule, Themis flagged a cross-reference defect in the state’s own published regulation:
16.8.2.10(F)(3) → “Subsection N of 16.8.2.8”16.8.2.8(N) = license non-transferability.
The reporting rule now sits at 16.8.2.8(M).
The 2024 amendment re-lettered 16.8.2.8 without updating the security rule’s cross-reference. We read the rulebook closely enough to catch the state’s own drafting error — that’s the standard your filing gets.
From walkthrough to accepted.
Map the rulebook
The regulation, decomposed requirement by requirement — the same list the reviewer works from.
Assess the gap
Your facility and procedures, scored against every requirement. You see what’s missing and what it risks.
Build the package
Plans, specs, SOPs, and training docs — assembled, cross-cited, submission-formatted in ten business days.
Defend it
The Division has questions, we answer them. Anything kicked back, we revise free until accepted.
Find out what the reviewer will find. First.
The gap score is a free, twenty-minute teardown of your security posture against the state’s requirement checklist. You keep the scorecard either way.
No hardware pitch · No obligation · Just the list