# ADR 0001: Restrict MVP Scope

## Status
Accepted

## Context
The original concept assumes wide hot-swap capability across batteries, cameras, compute modules, and user interface layout. That ambition is attractive but too broad for a first hardware generation.

## Decision
The MVP will support:

- fixed display assembly
- hot-swappable battery modules
- replaceable camera and IO modules
- replaceable modem or wireless modules only if power and RF isolation are validated
- one compute module installed at boot, not live-swapped during normal operation

The MVP will not support:

- live CPU swapping
- arbitrary high-bandwidth modules over a single universal connector profile
- waterproofing claims beyond what can be validated with replaceable modules
- user-visible dynamic theming based on module cosmetics as a core requirement

## Consequences

### Positive
- lower electrical and software complexity
- more realistic validation path
- clearer manufacturing target
- easier developer kit definition

### Negative
- weaker headline marketing story
- less visible differentiation in the first release
- some long-term concepts move to later phases

## Follow-up
- define module classes and descriptor schema
- define power handover targets
- define compatibility versioning rules