Owner: Robert Taylor (Eng) · Department: Engineering · Status: Live · Version: 1.0
Effective Date: 2026-06-13 · Last Reviewed: 2026-06-13 · Next Review Date: 2026-09-13
Source of Truth: code (FastAPI backend) · Maturity: 4 (Operational)
HempDash is several apps federated at the FastAPI seam — not yet one OS. Three databases, four role models.
flowchart TB
subgraph FastAPI[FastAPI backend - compliance truth DB]
VP[Vendor Portal] --> API
CA[Customer App] --> API
AFF[Affiliate Portal] --> API
API[(ComplianceAuditLog<br/>seals/COA/recall/POS)]
end
OD[Ops Dashboard] -->|proxy| API
OD --> ODB[(own Prisma DB<br/>training/grants/CRM)]
AUT[Automation/COS] --> AUTDB[(own Prisma DB<br/>vendor-acq/approvals/LoudDept)]
- FastAPI backend owns compliance truth (
ComplianceAuditLog).
- Ops Dashboard: delivery-ops admin, proxies FastAPI + own Prisma DB.
- Automation/COS: own Prisma DB (Phase-0 ops, Loud Dept).
- Vendor Portal + Customer App + Affiliate Portal → FastAPI.
- Loud Dept: AI marketing-content pipeline in the Automation app.
- 3 separate DBs, 4 role models, 3 event schemas — not unified (§6).
- Affiliate Portal seam broken — frontend
/affiliate/* vs backend /partners/me/* 404s (§4.5).
- No demo/real separation — no
is_demo flag; demo data can leak to public pages (§6.18-21).
- Loud-Dept claims not evidence-linked to COA/rule (§5.34).
Architecture index · Home
Distilled from docs/audits/backend-truth-audit-2026-06-13.md and portal-maturity-audit-2026-06-13.md.