Repository navigation
Decisions
Patrick Stähle edited this page Oct 30, 2026
·
1 revision
Snapshot of
docs/decisions/README.mdat commit707b4a0, preserved before the docs were compacted. History only: the current specs are in the repository.
Short records of decisions that shape the repo. One file per decision, numbered, never rewritten: a changed decision gets a new ADR that supersedes the old one.
| # | Decision | Status |
|---|---|---|
| 0001 | Monorepo layout, labels, squash merges | accepted |
| 0002 | Separate version streams; firmware binaries published next to the app (OTA part superseded by 0006) | accepted |
| 0003 | Community platform in platform/, program schema in spec/
|
proposed |
| 0004 | Platform: modular monolith, use cases exposed as REST (apps) and MCP (AI clients), magic link + passkeys | proposed |
| 0005 | Live results over BLE during the game: BLE stays connected on the central (fallback: reports after the game / over USB), decided by hardware test #38: 100 ms interval, central start on a timer | accepted |
| 0006 | No OTA firmware updates for now; pods are flashed over USB | accepted |
Template: Context · Decision · Consequences.
For users and coaches
Repository and workflow
Firmware
- Firmware Overview
- Firmware Architecture
- Firmware Link Protocol
- Firmware Config API
- Firmware Programs
- Firmware Testing
- Firmware Timing
- Firmware Host Syntax Check
Config App
Community platform (on hold)
Decisions (ADRs)
- Decisions
- ADR 0001 Repo Layout and Workflow
- ADR 0002 Versions and Firmware Delivery
- ADR 0003 Community Platform
- ADR 0004 Platform Architecture
- ADR 0005 Live Results over BLE
- ADR 0006 No OTA
- ADR 0007 Platform on Hold
Archive