Automates evaluation and tracking of non-compliant line items from RFP/RFI/bid compliance documents: parses compliance matrices with AI-assisted extraction, orchestrates task assignments through a defined state lifecycle (To-Do → In Progress → Ready for Review → Done → Closed), and generates executive risk/ effort reports.
Stack: Next.js 14 (App Router) · Supabase (Postgres, Auth, Storage) · Anthropic Claude (compliance-matrix parsing) · Resend (email)
- Node.js 20+
- Rancher Desktop (free, no enterprise licensing restrictions — set container engine to dockerd (moby) in Preferences; optional if running the app via
npm run dev, but still required for the Supabase CLI backend below) - Supabase CLI (local Postgres/Auth/Storage/Studio stack)
# 1. Backend — applies supabase/migrations/*.sql automatically
supabase start
# 2. Environment
cp .env.example .env.local # fill in values printed by `supabase status`
# 3. App
npm install
npm run dev # http://localhost:3000To run the app in Docker instead of npm run dev, see
docs/docker-local.md for the full workflow, seed data,
and smoke tests.
| Command | What |
|---|---|
npm run dev |
Start the Next.js dev server |
npm run build |
Production build |
npm run start |
Run a production build |
npm run lint |
ESLint |
npm run typecheck |
tsc --noEmit |
| Doc | Purpose |
|---|---|
| CLAUDE.md | Build workflow, domain rules, state-transition gates |
| docs/PRD.md | Product requirements |
| docs/engineering/engineering-doc.md | Architecture, flows, DB design |
| docs/specs/ | Implementation specs + supabase-schema.sql (hosted-Supabase reference) |
| docs/security/security-plan.md | Security controls |
| docs/docker-local.md | Local dev with Rancher Desktop + Supabase CLI |
| docs/MOP-fresh-machine-setup.md | Method of Procedure: run this codebase on a brand-new machine |
| docs/DESIGN_SYSTEM.md | Design system (Campaign Sky palette) |
| docs/CHANGELOG.md | Dated log of feature/architecture changes |
Dockerfile and docker-compose.yml build a standalone Next.js container
suitable for self-hosting. Point NEXT_PUBLIC_SUPABASE_URL /
SUPABASE_SERVICE_ROLE_KEY at a hosted Supabase project (rather than the
local CLI stack) for production. No production infrastructure target has been
locked in yet — both self-hosted-Docker and Vercel + Supabase Cloud are
viable with the current setup.