cda8946c75
- 11 wiki pages: CannaManage-Home + 01-10 covering full Phase 0 docs - 5 mockup images in docs/wiki/images/ - Updated _Sidebar.md with CannaManage section
1.7 KiB
1.7 KiB
🌿 CannaManage
B2B SaaS for German Cannabis Social Clubs (Anbauvereinigungen)
Status: Phase 0 — Planning Complete | Stack: Spring Boot 3.x + PrimeFaces → Next.js | Legal: ✅ CanG-Compliant
Documentation Index
| Document | Description |
|---|---|
| Project Charter | Vision, scope, risk register, timeline Gantt chart |
| User Stories | 25 stories with MoSCoW priorities + acceptance criteria |
| Architecture | System diagram, 8-entity ERD, multi-tenancy design |
| Flow Charts | 5 business logic flows (distribution, recall, compliance) |
| API Spec | REST API: 7 controllers, 30+ endpoints |
| Wireframes & Mockups | 6 screen wireframes with AI-generated UI mockups |
| Coding Standards | Java 21 standards, compliance code rules, Git strategy |
| Test Plan | 26 test cases, JaCoCo 100% gate on ComplianceService |
| Deployment Guide | Hetzner VPS, Docker Compose, Gitea CI/CD |
| Retrospective | Sprint 0 retro: decisions, challenges, Sprint 1 goals |
Quick Facts
- Market: 500–3,000 German Anbauvereinigungen (cannabis social clubs)
- Revenue Target: €39,500 MRR at 500 clubs (Year 3)
- Legal Basis: Konsumcannabisgesetz (CanG) §§2, 15-26 — B2B operations software only
- Architecture: Spring Boot 3.x + JPA/Hibernate, multi-tenant (shared schema + tenant_id)
- Source: pi_mcps plans/cannabis-club-saas