From aa38a14cb4eb126891fd1adbad7c3a5ead3624f9 Mon Sep 17 00:00:00 2001 From: Mikkel Georgsen Date: Sat, 28 Feb 2026 16:11:21 +0100 Subject: [PATCH] docs: save roadmap feedback for next session --- .planning/ROADMAP_FEEDBACK.md | 44 +++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 .planning/ROADMAP_FEEDBACK.md diff --git a/.planning/ROADMAP_FEEDBACK.md b/.planning/ROADMAP_FEEDBACK.md new file mode 100644 index 0000000..0e3acbf --- /dev/null +++ b/.planning/ROADMAP_FEEDBACK.md @@ -0,0 +1,44 @@ +# Roadmap Feedback (to apply in next session) + +Applied: 2026-02-28 — Context exhausted before changes could be made to ROADMAP.md + +## Changes to make + +### 1. Slim down Phase 1 (move 4 requirements to later phases) +- **NET-06** (lazy connections for 500+ venues) → Move to Phase 10 or later +- **NET-07** (custom domains) → Move to Phase 9 or 10 +- **AUTH-04** (Core Admin with mandatory MFA) → Move to Phase 2 (depends on Core) +- **AUTH-09** (NATS subject namespacing) → Move to Phase 2 (multi-tenant concern) +- Phase 1 goal: "Leaf binary boots, serves HTTP, NATS works, LibSQL works, basic PIN auth works, Netbird mesh connects, CI builds ARM64" + +### 2. Interleave UI with engine work (Phases 3-6) +- Building all engines headless then all UI at once is unnatural for a solo dev +- Consider: build tournament clock UI while building clock engine, financial UI while building financial engine +- This is a planning consideration for /gsd:discuss-phase, not necessarily a phase restructure +- Alternative: merge Phase 6 into Phases 3-5 (each phase builds its own UI slice) + +### 3. Move EXPORT out of Phase 2 +- EXPORT-01 through EXPORT-04 → Move to Phase 8 or later +- Not a dependency for anything; keeps Phase 2 focused on "identity + sync" + +### 4. Basic sound events earlier +- Basic sound triggers (level change, break start, bubble) are TDD table-stakes +- Consider: move basic play_sound action to Phase 3 (Tournament Engine) +- Full visual rule builder (EVENT-01 through EVENT-04) stays in Phase 9 + +### 5. Virtual Leaf (ARCH-02) needs a home +- Free tier runs virtual Leaf instances on cloud infrastructure +- Leaf binary must run headlessly on Core, managed as containers +- Different startup path than physical Leaf +- Should be part of Phase 2 (alongside Core sync) or its own phase +- Without this, there's no free tier to deploy + +### 6. Add offline duration test to success criteria +- Phase 3 or Phase 5 should include: "A 4-hour tournament with 40 players, including rebuys, bust-outs, table balancing, and payouts, completes successfully with the Leaf completely offline the entire time" + +### 7. Clarify 8hr vs 4hr soak test (Phase 7) +- Phase 7 success criterion 5 says "8+ hours" — more ambitious than pitfalls doc (4hr) +- If intentional, great — but soak test on Pi Zero 2W hardware needs to happen early in Phase 7, not at the end + +## Also update REQUIREMENTS.md traceability +- After moving requirements between phases, update the traceability table to match