Roadmap md

# Create ROADMAP.md

You are Codex, acting as the product delivery planner for this repository.

Goal:
Create (or update) ROADMAP.md that turns SPEC.md + ARCHITECTURE.md into a sequence of shippable vertical slices (milestones). The roadmap must optimize for learning + shipping, not “build layers first”.

Process:
1) Read SPEC.md and ARCHITECTURE.md.
2) Identify:
- the top user journeys that define “MVP works”
- the highest-risk assumptions (tech, UX, compliance, integrations)
- dependencies that must happen early (auth, data model, payments, etc.)
3) Propose 6–10 milestones max, each as a vertical slice that can be demoed and (ideally) deployed.
4) For each milestone, define scope boundaries and acceptance criteria.

ROADMAP.md structure (keep it practical, no fluff):
- 1) Roadmap principles (how we slice work, what we optimize for)
- 2) MVP definition (what “usable” means, non-goals for MVP)
- 3) Milestones (6–10 max)
For each milestone include:
- Name + objective (1–2 sentences)
- User-visible outcome (what someone can do now)
- Key deliverables (bullets, not detailed tasks)
- Dependencies (on earlier milestones)
- Risks + mitigations (top 2–4)
- Acceptance criteria (checkable)
- “Not included” (explicitly excluded items to prevent scope creep)
- 4) Cross-cutting work (ongoing)
- testing strategy maturation
- security/privacy hardening
- observability
- performance
- docs/runbooks
- 5) Open questions (only the ones that change sequencing)

Rules:
- Prefer slices that validate assumptions early (prototype risky integrations sooner).
- Avoid “setup-only” milestones unless they end in a demonstrable user outcome.
- Keep milestones small enough to land as 1 PR or a small set of PRs per milestone.
- If the repo already has a backlog or TASK_QUEUE, do NOT copy everything into ROADMAP.md. ROADMAP is milestones only.

Output — write to files (required):
1) Create/update ROADMAP.md with the v0 content.
2) Append an “## Open Questions” section at the bottom of ROADMAP.md with all sequencing questions (must-answer vs can-defer, with recommended defaults).

Do NOT leave questions only in chat. A new session must be able to read ROADMAP.md and see exactly what needs answering.

Output (chat):
- Confirm ROADMAP.md written
- List MVP definition + key assumptions (short bullets)
- State how many open questions remain

Now do it.