Owner: Ayisha (Compliance) · Department: Compliance · Status: Live · Version: 1.0
Effective Date: 2026-06-13 · Last Reviewed: 2026-06-13 · Next Review Date: 2026-09-13
Source of Truth: this page · Maturity: 3 (Usable)
When DSHS or an inspector arrives. Governance: Inspection Readiness SOP. Regulator comms: §17.5.
flowchart TD
A[Inspector arrives] --> B[Notify Compliance lead + founder]
B --> C[Generate Audit Pack<br/>backend, signed, 90-day]
C --> D[Hand over inspection ZIP<br/>per-product COA + seal + traceability]
D --> E[Log the interaction + evidence provided]
- Notify the Compliance lead (Ayisha) + founder immediately. Do not speculate to the inspector.
- Generate the Audit Pack (FastAPI backend — signed Ed25519 manifest, 90-day window) and/or the DSHS inspection ZIP (per-product COA, seal, traceability table).
- Hand over the package; record what was provided.
- Log the interaction (who, when, what evidence) for the audit trail.
CURRENT-STATE: audit-pack generation is synchronous and real; downloads are not auto-logged (§20.23) — log the handoff manually. No dedicated training/recall sections in the pack yet.
Generated audit pack (sha256 + signature) + manual handoff log.
Playbooks index · SOPs · Reference · Home