# War Room — Startup Org & Ticket System

A lightweight, git-native "Jira" the AI startup org uses to audit and finish the
product. Source of truth is **`board.json`**; the human-readable kanban
**`BOARD.md`** is generated from it.

## The org
Five C-level leads, each running a team:

| Lead | Team | Owns |
|------|------|------|
| **CEO** | Strategy & BizDev | prioritization, GTM (compliance-first), positioning, go/no-go |
| **CTO** | Engineering (BE/FE/DevOps/QA) | architecture, security, reliability, data model, tests, deploy |
| **CPO** | Product & Design | Know-Yourself + data-acquisition flow, onboarding, UX, i18n, conversion |
| **CMO** | Growth, Content & SEO | funnel, SEO (VI/pt-BR), WhatsApp, brand/trust, compliance-safe acquisition |
| **COO** | Ops, Legal & Finance | CVM/ad-platform compliance, payments (PIX/rails), KYC, withdrawals, support, launch checklist |

## Ticket lifecycle (status)
`backlog → todo → in_progress → review → done` (`blocked` is a flag via `deps`).

Priority: **P0** (launch blocker) · P1 (before public launch) · P2 (fast-follow) · P3 (later).
Effort: S (<½d) · M (~1-2d) · L (~1wk) · XL (multi-wk).

## How to update
1. Edit `board.json` (add/modify a ticket, change `status`, append to `comments`).
2. Run `node warroom/build-board.mjs` to regenerate `BOARD.md`.
3. Commit. Cross-team communication happens in each ticket's `comments[]`.

Ticket id = `<ROLE>-NNN` (e.g. `CTO-001`). `deps` reference other ticket ids.