- Constitution and project spec (spec.yml) - 7 comprehensive feature specs (tasks, batches, labor, compliance, inventory, integrations, comms) - Phase 1 implementation plan (6-week roadmap) - Week 1 task breakdown (15 concrete tasks) - Architecture and compliance documentation - Backend and frontend setup guides - Deployment guide for nexus-vector - CI/CD workflows (Forgejo Actions) - Quick start guide for developers Project is ready for implementation with: - Automated testing on every push - Automatic deployment to nexus-vector on push to main - Database migrations handled automatically - Health checks and monitoring Stack: TypeScript, Fastify, React, Vite, PostgreSQL, Prisma, Docker
1.5 KiB
1.5 KiB
CA Grow Ops Manager — Constitution
This is a summary of the full constitution located at
.specify/memory/constitution.md
Mission
Reduce cognitive load for teams managing licensed California cannabis cultivation facilities by centralizing operations, labor tracking, compliance recordkeeping, scheduling, and team communication.
Core Principles
- Opinionated & Simple: Every critical workflow completable in ≤ 3 screens
- Floor-Optimized: Big tap targets, dark mode, offline-friendly
- API-First: All features exposed via typed HTTP/JSON APIs
- Security & Compliance: Strict auth, RBAC, audit logs, METRC as system of record
- Spec Kit Workflow: Every feature starts as spec → plan → tasks → implementation
Stack
- Backend: TypeScript, Node.js, Express/Fastify, PostgreSQL, Prisma
- Frontend: TypeScript, React, Vite/Next.js, Radix/shadcn components
- Mobile: Web-first (tablet-optimized), React Native as stretch goal
Domains
- CultivationOps (tasks, batches, rooms)
- Compliance (recordkeeping, audit packets)
- Labor (timeclock, hours, cost tracking)
- Inventory (materials, nutrients, supplies)
- Integrations (METRC, environmental monitoring)
- Communications (notifications, announcements)
Governance
- Changes must not violate the constitution; if they need to, update the constitution explicitly
- All features follow the Spec Kit loop: spec → plan → tasks → implement
For full details, see .specify/memory/constitution.md