Components
Cabin component inventory and taxonomy for AAOS cabin HMI. Every component is specified for Compose and Views, shares tokens, and declares compliance hooks.
Taxonomy
| Tier | Meaning | Examples |
|---|---|---|
| Primitive | Low-level building blocks | Button, IconButton, Chip, ListItem, Banner |
| Chrome | System-level frames | System bars, status bars |
| Domain | Cabin feature surfaces | Media, EV, HVAC, vehicle controls |
| Pattern | Multi-component flows | Restricted browse, fault recovery |
Primitives will be detailed as implementation proceeds; this phase focuses on chrome and domain coverage OEMs expect on day one.
Classification (safety)
Each component documents one of:
- Informational — glance status
- Convenience — comfort / media / settings
- Safety-critical — see safety-critical
Inventory map
| Area | Doc | Priority for early phases |
|---|---|---|
| System bars | system-bars.md · MVP spec | MVP (Views-first) |
| Status bars | status-bars.md · MVP spec | MVP (Views-first) |
| Media | media.md | After MVP |
| EV / energy | ev.md | After MVP |
| HVAC | hvac.md | After MVP |
| Vehicle controls | vehicle-controls.md | After MVP |
| OEM extensions | extension-model.md | Continuous |
Dual-stack contract template
Every component page includes (or will include at implementation):
- Purpose and placement in the cabin
- States / signals
- Compliance (driving, UX, a11y, safety class)
- Token dependencies
- Planned Compose API
- Planned Views API
- Acceptance criteria / parity notes
Planned module ownership
| Component family | Primary modules |
|---|---|
| Chrome (system/status) | cabin-views first; Compose mirrors for apps |
| Media / EV / HVAC / controls | cabin-compose + cabin-views |
| Shared banners, buttons | both |