Project State

Project Reference

See: .planning/PROJECT.md (updated 2026-02-28)

Core value: A venue can run a complete tournament offline on a €100 device with wireless displays and player mobile access — and it just works, on any network, with zero IT involvement. Current focus: Phase 1 — Foundation

Current Position

Phase: 1 of 11 (Foundation) Plan: 0 of TBD in current phase Status: Ready to plan Last activity: 2026-02-28 — Roadmap created (11 phases, 126 v1 requirements mapped)

Progress: [░░░░░░░░░░] 0%

Performance Metrics

Velocity:

Total plans completed: 0
Average duration: -
Total execution time: 0 hours

By Phase:

Phase	Plans	Total	Avg/Plan
-	-	-	-

Recent Trend:

Last 5 plans: none yet
Trend: -

Updated after each plan completion

Accumulated Context

Decisions

Decisions are logged in PROJECT.md Key Decisions table. Recent decisions affecting current work:

[Init]: Go monorepo, shared internal/, cmd/leaf and cmd/core are the only divergence points
[Init]: NATS sync_interval: always required before first deploy (December 2025 Jepsen finding)
[Init]: All monetary values int64 cents — never float64 (CI gate test required)
[Init]: go-libsql has no tagged releases — pin to commit hash in go.mod
[Init]: Netbird reverse proxy is beta — validate player PWA access in Phase 1 before depending on it in Phase 8

Pending Todos

None yet.

Blockers/Concerns

[Phase 1]: go-libsql CGO ARM64 cross-compilation must be validated in CI before any downstream features depend on it
[Phase 1]: Netbird reverse proxy beta status — test the full QR code → HTTPS → WireGuard → Leaf flow early
[Phase 3]: NATS JetStream cross-domain stream mirroring (Leaf → Core) needs integration test before Phase 2 depends on it
[Phase 7]: Pi Zero 2W memory must be profiled on actual hardware with all display views before scaling signage

Session Continuity

Last session: 2026-02-28 Stopped at: Roadmap created, STATE.md initialized — ready to begin Phase 1 planning Resume file: None

2.1 KiB Raw Blame History