Owner: Laura (Ops) · Reviewer: Purple · Department: Operations · 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 validation + code audits · Maturity: 4 (Operational)
What would an experienced HempDash employee know that isn't yet written? A workflow isn't complete if it needs tribal knowledge.
| Workflow | Missing knowledge | Severity | Recommendation |
|---|---|---|---|
| Recall | That delist is manual + vendor owns off-platform action | P1 | Captured in recall playbook Phase 3 reword ✅ |
| Vendor activation | That go-live is advisory, bypassable | P1 | Captured in System Capability Status ✅ |
| KYB | That the provider defaults to mock unless MIDDESK_API_KEY set | P2 | Captured in KYB playbook ✅ |
| Seal | That revocation has no in-app write path (eng escalation) | P1 | Captured in Seal Revocation playbook ✅ |
| Customer support | That there's no complaint/CAPA system (manual escalation) | P1 | Captured in Customer Onboarding & Success ✅ |
| Deploy | That backend deploys via railway up, not git push (org suspended) |
P2 | NOT in wiki — lives in repo memory; add to Release Governance SOP |
| Plaid IDV | That it's code-complete but awaiting template config | P2 | Captured in Identity Verification Standard ✅ |
Most prior tribal knowledge was surfaced into the wiki during this program (the honest current-vs-target notes). One residual item: the backend deploy mechanism (railway up bypass) lives in engineering memory, not the Release Governance SOP — recommend adding it. Severity P2.
Program Closeout Report · Final Scorecard · Remediation Plan · Home