Table of Contents

🌿 CannaManage

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

🌿 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

🌿 CannaManage

Documentation Index

Quick Facts

🔧 pi_mcps Wiki

Overview

MCP Servers

Java Projects

🌿 CannaManage