This directory records architectural decisions that would be hard to infer from code alone.
ADRs are intentionally short. They explain what was decided and why; detailed implementation guidance belongs in the architecture documents.
Every ADR carries one explicit status:
proposed: direction under evaluation; do not treat it as canonical shipped behavior without current code/product evidence.accepted: the current decision. It can describe implemented direction that has not yet appeared in a public release.superseded: historical context replaced by a newer ADR, which the record must link.
ADR status describes decision maturity, not release status.
- 0001 Platform Layer for OS-specific Hardware Access
- 0002 Core / App Split
- 0003 Storage Health Device Identity
- 0004 Separate Storage Health History
- 0005 Storage Health Naming
- 0006 Live Storage Health on Demand
- 0007 Elevated Startup Mode
- 0008 Selected Storage Device Overrides Focus Alarm
- 0009 Generated App Hardware DTOs
- 0010 Grouped Navigation with Classic Fallback
- 0011 Experimental Sensor Enablement for Recognized-but-Unverified Hardware