RDC 1.014 compliance with immutable traceability — and open-source code your board can audit.

Operational compliance spine for Brazilian medical cannabis patient associations (regulated non-profits licensed to import/cultivate/dispense medical cannabis) — dispensation, traceability, and audit trail. LGPD-by-design. SNGPC integration in development (mock today; ANVISA XSD schema pending Jun/2026). Cultivation and financials on the v1.0 roadmap (2028). Self-hosted or managed — your data stays with you.

Explore the Code

Dedicated repo being organized — v0.3 (Jul 2026). Today: development vault.

v0.1.0 · usable foundation · 154/154 tests · canna-br.fonsecagabriel.com.br

Apresentação canna-br

Regulatory alert

August 4, 2026 — the window closes. Associations without a compliant system are increasing their regulatory exposure.

RDC 1.014/2026 is Brazil's first formal administrative regime for patient associations (replaces case-by-case habeas corpus from STJ Tema 16 IAC, 2023). From August onward, direct ANVISA (Brazil's FDA equivalent) inspection requires an immutable audit trail, integrated SNGPC (Brazil's controlled-substances tracking system), RBAC with segregation of duties, and full seed-to-dispensation traceability.

LGPD personal liability

Health data in a closed SaaS without a DPA and designated DPO exposes board members to personal liability (LGPD Art. 5 II — Brazil's GDPR equivalent personal liability clause). Mitigation: self-host + DPO + contracts.

see legal details →

ANVISA fine + license revocation

Absence of audit trail and compliant SNGPC reporting results in infraction notices, suspension, and revocation of operating authorization.

see legal details →

LGPD regulatory exposure (Art. 5 II)

Software without crypto-deletion (Art. 18 IV) prevents effective erasure of sensitive health data — a non-waivable legal obligation.

see legal details →

Confirmed gap: no solution covers LGPD + SNGPC + self-hosted + auditable code simultaneously. openthc/pos, cannlytics, XURU, BudApp — none of them.

Why canna-br

Three pillars that don't exist together in any other system

LGPD-by-design

Technical control of health data (LGPD-by-design) — mitigates technical risk (full elimination still requires more than software: designated DPO, pharmaceutical technical officer, documented RIPD, contracts). Per-member AES-256-GCM cryptographic envelope. Crypto-deletion guaranteed (Art. 18 IV LGPD). Optional self-host. Each association owns its own data.

Per-member crypto · Self-hosted · LGPD Art. 18 IV

SNGPC in development

Architecture ready for RDC 1.014 (SNGPC homologation pending). XML conforming to the regulation implemented in mock — the specific XSD schema for associations has not yet been published by ANVISA (Jun/2026). Durable retry with BullMQ. Immutable audit log via event sourcing. Complete seed-to-dispensation traceability.

SNGPC mock — ready to integrate when ANVISA publishes XSD

RDC 1.014 · SNGPC mock · 7 ANVISA KPIs

Auditable OSS

Immutable and audit-proof traceability. AGPL-3.0 — open source, no lock-in, forks permitted. Any association lawyer can review every line that processes member data. 100% verifiable ledger.

AGPL-3.0 · Event Sourcing · Audit trail

AI and government automation ready — every business operation exposed as an MCP tool before any UI. Integrates with agents, external automations, and ANVISA pipelines without scraping or workarounds.

How it works

From onboarding to audit in 4 steps.

Built for small teams: you don't need dedicated IT. Operations happen in chat.

01

Diagnosis

Onboarding call (1h). We map your current legal structure (habeas corpus vs. RDC), dispensation workflow, SNGPC integration status (or absence).

Output: current-state dossier + RDC 1.014 adoption roadmap.

02

Secure setup

We provision your instance (self-host or canna-br.fonsecagabriel.com.br). Import member registry, batches, prescriptions. Crypto keys generated locally.

Output: isolated environment + migrated data + trained technical officer.

03

Operations in chat

Pharmacist dispenses via Open WebUI: "Record dispensation 5g patient X batch Y". System validates quota, deducts inventory, generates SNGPC, records immutable event.

Output: dispensation without parallel spreadsheets, zero-friction SNGPC.

04

Automatic audit

ANVISA inspector arrives? Board opens dashboard, generates signed quarterly report, exports immutable seed-to-dispensation trail. No spreadsheet treasure hunt.

Output: auditable dossier in minutes, not days.

Recorded demo

Walkthrough: pharmacist + auditor + RDC report — recording scheduled for Q3 2026.

Walkthrough of pharmacist dispensing + auditor tracing a batch + board generating RDC report. Will be recorded on the first pilot association's instance after onboarding.

Recorded demo · Q3 2026

Product in practice

Not a deck. Here's the system running in smoke validation.

Real captures of Open WebUI v0.9.6 + canna-br MCP server on 2026-06-08. There is no separate Next.js admin — operations happen inside the chat with inline MCP Apps. What you see below is what your team uses.

MCP App · Member

Member quota and history

Dispenser asks "what's João's quota?" — inline app shows active prescription, monthly quota, used dispensations. Zero CRUD screen.

MCP App · Dispensation

Inline dispensation recording

Form rendered in chat with approval gate. Commit generates atomic DispensationRecorded + LotQuantityDeducted events in the ledger.

MCP App · Traceability

Seed-to-dispensation chain of custody

Auditor asks "trace batch LT-001" — timeline with cultivation, harvest, approved COA report, dispensations. Immutable trail.

Admin · Integrations

canna-br MCP server connected

Open WebUI Admin → Settings → Integrations. canna-br MCP server registered, tools enumerated, healthcheck green.

Operations · Chat

Your team uses the OWUI chat

Open WebUI v0.9.6 — chat with AI model + canna-br tools available. Same UX as ChatGPT/Claude, with the full operational power of the association.

Smoke 2026-06-08

3 MCP Apps validated end-to-end

Stack: Postgres 16 + Redis 7 + OWUI v0.9.6 + canna-br MCP. Cold start 44s, 3 GB RAM steady. postMessage contract OK.

Alpha honesty: these are real MCP Apps running against the domain kernel. Not Figma mockups. But it is alpha — aesthetics and internal copy will be polished by v1.0 (gate: "awesome UX polished"). See the technical write-up in release v0.2.1.

Main circle · open invitations

The team being built.

This is not an institutional team page. These are people being invited — one by one, with real names, proposed roles, and the why. Each card is a live invitation. If you're here and want to propose a different framing, write to Gabriel .

Current state · v0.1.0 → v1.0

What's ready, in progress, and planned — by area.

No opacity. See exactly where we are in v0.1.0, what ships in v0.2 (multi-tenant), v0.3 (pilot hardening), and v1.0. Red line = external blocker (sandbox, RDC, partner).

Area Capability v0.1.0 today v0.2 multi-tenant v0.3 pilot v1.0 GA
LGPD AES-256-GCM envelope per member ✓ ready
Crypto-deletion (Art. 18 IV) ✓ ready
Versioned consent + RIPD partial partial ✓ ready
SNGPC XML schema + mock submit ✓ ready
BullMQ retry/DLQ worker scaffold scaffold ✓ ready
ANVISA production homologation (awaiting ANVISA XSD schema) tracking ✓ planned
AI / MCP MCP server + tools (levels 1-3) L1/L2 ✓ · L3 operational (pilot validation)
Inline MCP Apps (3 → 12) 3 apps 5 apps 7 apps 12 apps
Open WebUI sidecar + OAuth 2.1 auth smoke smoke ✓ ready
Gov. O2 RBAC + TOTP (segregation of duties) partial partial ✓ ready
Versioned O2 roles (agreements as code) scaffold scaffold partial ✓ planned
Quarterly BSPO signed by technical officer + RIPD via MCP App partial ✓ planned
✓ ready

Covered by tests; in production/demo.

partial / scaffold

Structure exists; missing hardening or coverage.

tracking

Blocked by external actor (ANVISA/partner).

— planned

Declared roadmap; not started.

Detailed quarterly roadmap at /roadmap. Releases at /releases.

Start as

Each role has a direct path.

Identify your pain, see what canna-br solves, go straight to the documentation that matters.

Board of Directors

Pain

Personal criminal liability from health data in a closed SaaS (LGPD Art. 5 II).

Outcome

Immutable trail + crypto-deletion + self-host reduce the technical risk vector (final legal exposure remains the board's + designated DPO's responsibility).

See liability risk →

Legal Counsel

Pain

Mapping RDC 1.014 + LGPD + SNGPC obligations in a system not designed for this.

Outcome

Legal framework mapped article by article + signed ADRs + unquestionable audit log.

See legal framework →

Technical Pharmacist (RT)

Pain

Manual dispensation + out-of-band SNGPC + parallel spreadsheets = inspection impossible.

Outcome

MCP chat records dispensation, deducts quota, generates SNGPC without leaving the workflow.

See dispensation flow →

Association IT

Pain

Proprietary SaaS = lock-in, no code audit, no self-host for sensitive data.

Outcome

Auditable OSS stack, docker-compose in 10 min, versioned ADRs, forks permitted.

See stack + setup →

Trust & Transparency

Everything that backs the thesis, in public links.

Organic Governance · O2

Organic Organization: explicit roles, living circles, tensions as fuel.

canna-br adopts O2 (Organic Organization) from Target Teal — Brazilian OSS social technology for self-management. No command chain, no fixed titles. Structure is a map of agreements that evolves through real tensions.

01

Distributed Authority

Individual autocratic operational decisions by default. Everything is permitted unless explicitly prohibited.

02

Roles and Circles

Structure by purpose and granular accountabilities. No "CTO" or "CEO" title — only explicit roles.

03

Evolution through Tensions

Real problems and opportunities feed structural adaptations. Agreements versioned as code.

04

5 Interaction Modes

Review · Sync · Adapt · Select · Care. Meetings with a clear objective, not a loose agenda.

05

Tribal Space

Care Mode isolates human relationships from work. Empathy and vulnerability have their own space.

Differentiator: O2 avoids the proprietary density of Holacracy (includes Care Mode) and the slowness of excessive consent in Sociocracy 3.0 (individual autocracy default). Adopted by Tera, eduK, Take, More Than Real, Kanpai BH, and more.

Initiator · circle lead

Gabriel Fonseca

Founder Via Corretor · Senior AI Engineer (Mukutu) · Software Zen Kanban

Engineer with 12+ years in regulated systems (event sourcing, compliance, operational kanban). Medical cannabis patient — experienced firsthand the operational friction that canna-br resolves. Conceived the project after mapping the OSS gap in the Brazilian sector ahead of the RDC 1.014 window.

Current accountabilities

  • Circle purpose — carries the aim until new roles anchor
  • Domain modeling — Emmett-pure, Event Sourcing, versioned ADRs
  • Infra ops — VPS, Kamal, hosted canna-br.fonsecagabriel.com.br
  • MCP-first surface — gate for awesome UX production polish
  • Pilot on-call — WhatsApp direct during seed
  • Seed recruiter — 5 association slots, curation + onboarding
  • Compliance liaison — RDC 1.014, LGPD, SNGPC tracking
  • Caretaker (O2 Mode) — tribal space of the circle

Explicit roles derived from active premises in the /manager ledger (governance + infra + ops + product + hard_rule). Structure evolves through tensions — roles will be partitioned when RT compliance, infra-owner, and association-relations roles anchor.

Current team

One founder, open source, nascent community. No hired staff, no incorporated entity yet. canna-br is a serious project in pre-commercial-MVP stage — the ambition is to hire 2 roles (technical + legal) when the pilot validates PMF. Full transparency: /about/ + /trust/.

For market analysts

TAM R$130M (~US$26M) by 2030. SOM R$27M (~US$5.4M). Comparable: Cannanas DE (€7.2M ARR).

Full financial model — TAM/SAM/SOM, 24-month projection in 3 scenarios (pessimistic/conservative/optimistic), validated German reference, explicit assumptions — lives on a dedicated page. Homepage focuses on value + proof; market analysis stays separate.

See market, TAM/SAM/SOM and projections →

Technical-legal disclaimer

canna-br is a software tool. Legal compliance (LGPD, RDC 1.014, Portaria 344/98) is the sole responsibility of the adopting association and its lawyers/DPO. No technical mechanism substitutes a proper legal opinion or formal appointment of a pharmaceutical technical officer (RT) and DPO as required by law. See /trust/ — Privacy Policy, Terms, and DPO.

5 slots · deadline Sep 30 2026 · 2 available

Get in before the public call. Influence the roadmap. Receive the ANVISA dossier template ready to go.

We are looking for 5 associations to co-develop the SNGPC integration and the ANVISA application template dossier. Pilot associations influence the roadmap and get early access to the system's auto-documented template.

See slots and criteria

Applications open through September 30, 2026. Free for pilots.

Candidatura · Associação Piloto

Grave seu vídeo de até 3 minutos

Clique para permitir câmera + microfone

Você pode pré-visualizar antes de começar a gravar.