# ccpk1/choreops architecture

> Architecture diagram of the GitHub repository ccpk1/choreops, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-06-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/ccpk1/choreops
- Repository: https://github.com/ccpk1/choreops

## Overview

1. **Project boundary and runtime**
   - This is a **Home Assistant custom integration** (`custom_components/choreops`) that runs entirely inside the HA process.
   - It is **local-first**: no external backend, no cloud service, and no separate database service. Persistence is handled through Home Assistant storage.

2. **Primary domain**
   - The integration models a household operations platform with several domain areas: **users/profiles, chores, scheduling, rewards, points/XP, badges, statistics, notifications, and dashboards**.
   - The repo supports both **gamified** and **utility-only** usage, so the architecture keeps the game layer separable from chore operations.

3. **Integration entry points**
   - `__init__.py` is the integration root and likely owns setup/teardown and runtime wiring.
   - `config_flow.py` and `options_flow.py` implement Home Assistant’s setup UI and runtime configuration changes.
   - `services.py` plus `services.yaml` expose domain actions to automations/scripts.
   - `manifest.json` defines the HA integration metadata and platform dependencies.

4. **Layered application structure**
   - The `managers/` package is the orchestration layer: it coordinates use cases and cross-domain workflows.
   - The `engines/` package appears to hold the core domain logic for chores, scheduling, economy/points, gamification, and statistics.
   - The split suggests a clean boundary: **managers decide “what to do,” engines compute “how it should behave.”**

5. **Core orchestration managers**
   - `chore_manager`, `reward_manager`, `economy_manager`, `gamification_manager`, `statistics_manager`, `notification_manager`, `system_manager`, `ui_manager`, and `user_manager` each own a major subsystem.
   - These are the main application-service boundaries to show in a diagram, because they translate HA events and service calls into domain actions.

6. **Domain engines**
   - `chore_engine.py`, `schedule_engine.py`, `economy_engine.py`, `gamification_engine.py`, and `statistics_engine.py` represent reusable business logic.
   - The engine layer is where recurrence, rotation, streaks, badges, point accounting, and reporting rules are computed.
   - This is the strongest candidate for the “core logic” box in an architecture diagram.

7. **Entity and platform surface**
   - The integration exposes Home Assistant-native entities through `sensor.py`, `button.py`, `select.py`, and `calendar.py`, with `sensor_legacy.py` retained for compatibility.
   - `entity.py` is the shared entity base, so the runtime surface is not a custom app UI only; it is also a set of HA entities that automations can consume.
   - `notification_action_handler.py` closes the loop for actionable notifications, feeding user responses back into the domain flow.

8. **State, storage, and migrations**
   - `store.py` is the persistence boundary for integration data.
   - `migrations/modern.py` and `migrations/pre_v50.py` show that the project has a significant schema evolution history, including compatibility with older KidsChores data.
   - `integrity/boot_repairs.py` indicates startup repair logic for inconsistent or partially migrated state.
   - Diagram-wise, storage sits between the managers/engines and the HA entity layer.

9. **Data transformation helpers**
   - `helpers/`, `data_builders.py`, and `type_defs.py` provide the translation layer between domain objects and HA-facing payloads.
   - `helpers/dashboard_builder.py` and `helpers/dashboard_helpers.py` support dashboard generation, while `entity_helpers.py`, `flow_helpers.py`, `storage_helpers.py`, and `translation_helpers.py` keep setup and runtime wiring manageable.
   - `utils/` contains repository tooling and validation scripts, not runtime logic.

10. **Dashboard subsystem**
   - `custom_components/choreops/dashboards/` contains dashboard registry data, template YAML, preferences, and translated dashboard labels.
   - The repo supports generated or templated dashboards for different personas and layouts, including admin/shared/user variants.
   - This subsystem is a separate presentation layer that consumes runtime state and helper payloads rather than duplicating business logic.

11. **Localization and branding**
   - `translations/` and `translations_custom/` provide integration text plus specialized notification/report strings.
   - Dashboard-specific translations live separately under the dashboards package.
   - `brand/`, `icons.json`, and related assets support consistent Home Assistant presentation and entity naming.

12. **Testing and validation model**
   - The `tests/` tree is extensive and scenario-driven, with fixtures, migration samples, golden master data, and end-to-end workflow tests.
   - Coverage spans config flows, services, entity behavior, scheduling, gamification, notifications, dashboard generation, migration, and performance.
   - This means the architecture is not just layered in code; it is also enforced by contract and scenario tests across the major boundaries.

13. **Operational and release tooling**
   - GitHub Actions, pre-commit, lint/type configs, and HACS metadata show that the repo is built for strict quality gates and Home Assistant distribution.
   - The presence of release, validation, and dashboard asset workflows indicates the repo treats generated assets and integration packaging as part of the architecture, not just build plumbing.

14. **End-to-end data flow**
   - A typical flow is: **Home Assistant config/options → stored integration state → managers/orchestrators → domain engines → updated storage and entity state → dashboards, sensors, actions, and notifications**.
   - User actions can re-enter through services, entity commands, or notification responses, making the system a closed loop inside Home Assistant rather than a one-way data publisher.

Main entry points: [`custom_components/choreops/store.py`](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/store.py) (Store), [`custom_components/choreops/entity.py`](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/entity.py) (Entities), [`custom_components/choreops/services.py`](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/services.py) (Services), [`tests/README.md`](https://github.com/ccpk1/choreops/blob/main/tests/README.md) (Tests)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_runtime["HA integration"]
  node_init["Integration<br/>setup/teardown<br/>[__init__.py]"]
  node_config_flow["Config flow<br/>HA config<br/>[config_flow.py]"]
  node_options_flow["Options flow<br/>HA options<br/>[options_flow.py]"]
  node_services["Services<br/>[services.py]"]
  node_notification_actions(("Action handler<br/>notification callbacks"))
end

subgraph group_application["Application layer"]
  node_ui_manager["UI manager<br/>orchestrator<br/>[ui_manager.py]"]
  node_system_manager["System manager<br/>orchestrator<br/>[system_manager.py]"]
  node_user_manager["User manager<br/>profile orchestration<br/>[user_manager.py]"]
  node_chore_manager["Chore manager<br/>workflow orchestration<br/>[chore_manager.py]"]
  node_reward_manager["Reward manager<br/>reward orchestration<br/>[reward_manager.py]"]
  node_economy_manager["Economy manager<br/>points orchestration<br/>[economy_manager.py]"]
  node_gamification_manager["Gamify manager<br/>game orchestration"]
  node_statistics_manager["Stats manager<br/>report orchestration"]
  node_notification_manager["Notification manager<br/>alert orchestration"]
end

subgraph group_domain["Domain engines"]
  node_chore_engine{{"Chore engine<br/>domain logic<br/>[chore_engine.py]"}}
  node_schedule_engine{{"Schedule engine<br/>domain logic<br/>[schedule_engine.py]"}}
  node_economy_engine{{"Economy engine<br/>domain logic<br/>[economy_engine.py]"}}
  node_gamification_engine{{"Gamify engine<br/>domain logic"}}
  node_statistics_engine{{"Stats engine<br/>domain logic"}}
end

subgraph group_data["State & migration"]
  node_store[("Store<br/>persistent storage<br/>[store.py]")]
  node_migrations["Migrations<br/>schema evolution<br/>[modern.py]"]
  node_boot_repairs["Boot repairs<br/>startup repair<br/>[boot_repairs.py]"]
end

subgraph group_presentation["Presentation"]
  node_entities["Entities<br/>[entity.py]"]
  node_sensors["Sensors<br/>entity platform<br/>[sensor.py]"]
  node_legacy_sensors["Legacy sensors<br/>compat entity<br/>[sensor_legacy.py]"]
  node_buttons["Buttons<br/>entity platform<br/>[button.py]"]
  node_selects["Selects<br/>entity platform<br/>[select.py]"]
  node_calendar["Calendar<br/>entity platform<br/>[calendar.py]"]
  node_helpers["Helpers<br/>transformation layer<br/>[__init__.py]"]
  node_dashboard_builder["Dashboard builder<br/>presentation helper"]
  node_dashboards["Dashboards<br/>templated UI"]
  node_translations["Translations<br/>i18n<br/>[en.json]"]
  node_brand["Branding<br/>assets"]
end

subgraph group_tooling["Tooling & QA"]
  node_tests["Tests<br/>[README.md]"]
end

node_config_flow -->|"creates state"| node_store
node_options_flow -->|"updates state"| node_store
node_init -->|"wires lifecycle"| node_system_manager
node_init -->|"registers"| node_services
node_init -->|"registers entities"| node_entities
node_services -->|"dispatches"| node_chore_manager
node_services -->|"dispatches"| node_reward_manager
node_services -->|"dispatches"| node_economy_manager
node_services -->|"dispatches"| node_gamification_manager
node_services -->|"dispatches"| node_statistics_manager
node_notification_actions -->|"feeds back"| node_notification_manager
node_chore_manager -->|"uses"| node_chore_engine
node_chore_manager -->|"uses"| node_schedule_engine
node_reward_manager -->|"uses"| node_economy_engine
node_economy_manager -->|"uses"| node_economy_engine
node_gamification_manager -->|"uses"| node_gamification_engine
node_statistics_manager -->|"uses"| node_statistics_engine
node_system_manager -->|"loads/saves"| node_store
node_store -->|"evolves via"| node_migrations
node_system_manager -->|"repairs"| node_boot_repairs
node_helpers -->|"supports"| node_dashboard_builder
node_dashboard_builder -->|"renders"| node_dashboards
node_ui_manager -->|"coordinates"| node_dashboard_builder
node_ui_manager -->|"syncs"| node_entities
node_entities -->|"implements"| node_sensors
node_entities -->|"implements"| node_buttons
node_entities -->|"implements"| node_selects
node_entities -->|"implements"| node_calendar
node_entities -->|"compatibility"| node_legacy_sensors
node_chore_manager -->|"persists"| node_store
node_economy_manager -->|"persists"| node_store
node_gamification_manager -->|"persists"| node_store
node_statistics_manager -->|"reads"| node_store
node_translations -->|"localizes"| node_dashboards
node_brand -->|"brands"| node_entities
node_tests -->|"covers"| node_config_flow
node_tests -->|"covers"| node_services
node_tests -->|"covers"| node_store
node_tests -->|"covers"| node_dashboards
node_tests -->|"covers"| node_chore_engine
node_tests -->|"covers"| node_gamification_engine

click node_init "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/__init__.py"
click node_config_flow "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/config_flow.py"
click node_options_flow "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/options_flow.py"
click node_services "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/services.py"
click node_notification_actions "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/notification_action_handler.py"
click node_entities "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/entity.py"
click node_sensors "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/sensor.py"
click node_legacy_sensors "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/sensor_legacy.py"
click node_buttons "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/button.py"
click node_selects "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/select.py"
click node_calendar "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/calendar.py"
click node_ui_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/ui_manager.py"
click node_system_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/system_manager.py"
click node_user_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/user_manager.py"
click node_chore_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/chore_manager.py"
click node_reward_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/reward_manager.py"
click node_economy_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/economy_manager.py"
click node_gamification_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/gamification_manager.py"
click node_statistics_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/statistics_manager.py"
click node_notification_manager "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/notification_manager.py"
click node_chore_engine "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/chore_engine.py"
click node_schedule_engine "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/schedule_engine.py"
click node_economy_engine "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/economy_engine.py"
click node_gamification_engine "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/gamification_engine.py"
click node_statistics_engine "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/statistics_engine.py"
click node_store "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/store.py"
click node_migrations "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/migrations/modern.py"
click node_boot_repairs "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/integrity/boot_repairs.py"
click node_helpers "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/helpers/__init__.py"
click node_dashboard_builder "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/helpers/dashboard_builder.py"
click node_dashboards "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/dashboards/dashboard_registry.json"
click node_translations "https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/translations/en.json"
click node_brand "https://github.com/ccpk1/choreops/tree/main/custom_components/choreops/brand"
click node_tests "https://github.com/ccpk1/choreops/blob/main/tests/README.md"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_init,node_config_flow,node_options_flow,node_services,node_notification_actions toneBlue
class node_ui_manager,node_system_manager,node_user_manager,node_chore_manager,node_reward_manager,node_economy_manager,node_gamification_manager,node_statistics_manager,node_notification_manager toneAmber
class node_chore_engine,node_schedule_engine,node_economy_engine,node_gamification_engine,node_statistics_engine toneMint
class node_store,node_migrations,node_boot_repairs toneRose
class node_entities,node_sensors,node_legacy_sensors,node_buttons,node_selects,node_calendar,node_helpers,node_dashboard_builder,node_dashboards,node_translations,node_brand toneIndigo
class node_tests toneTeal
```

## Components

### HA integration

Home Assistant entry points and entity surface

- [Integration](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/__init__.py): setup/teardown · Home Assistant integration root and lifecycle wiring · `custom_components/choreops/__init__.py`
- [Config flow](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/config_flow.py): HA config · Initial setup and discovery flow · `custom_components/choreops/config_flow.py`
- [Options flow](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/options_flow.py): HA options · Runtime configuration changes · `custom_components/choreops/options_flow.py`
- [Services](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/services.py): HA services · Service registration and automation actions · `custom_components/choreops/services.py`
- [Action handler](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/notification_action_handler.py): notification callbacks · Routes actionable notification responses back into workflows · `custom_components/choreops/notification_action_handler.py`

### Application layer

Orchestration managers and service boundaries

- [UI manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/ui_manager.py): orchestrator · Coordinates dashboard and control-state presentation · `custom_components/choreops/managers/ui_manager.py`
- [System manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/system_manager.py): orchestrator · Owns startup, cleanup, and integration-wide coordination · `custom_components/choreops/managers/system_manager.py`
- [User manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/user_manager.py): profile orchestration · Manages household users, roles, and profile state · `custom_components/choreops/managers/user_manager.py`
- [Chore manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/chore_manager.py): workflow orchestration · Coordinates chore lifecycle and cross-domain updates · `custom_components/choreops/managers/chore_manager.py`
- [Reward manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/reward_manager.py): reward orchestration · Handles reward CRUD and redemption workflows · `custom_components/choreops/managers/reward_manager.py`
- [Economy manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/economy_manager.py): points orchestration · Coordinates points, XP, and accounting flows · `custom_components/choreops/managers/economy_manager.py`
- [Gamify manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/gamification_manager.py): game orchestration · Coordinates badges, streaks, and progression flows · `custom_components/choreops/managers/gamification_manager.py`
- [Stats manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/statistics_manager.py): report orchestration · Builds rollups and reporting workflows · `custom_components/choreops/managers/statistics_manager.py`
- [Notification manager](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/managers/notification_manager.py): alert orchestration · Sends reminders and notification updates · `custom_components/choreops/managers/notification_manager.py`

### Domain engines

Core business rules for chores, schedules, economy, gamification, and stats

- [Chore engine](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/chore_engine.py): domain logic · Rules for chore state, availability, and completion · `custom_components/choreops/engines/chore_engine.py`
- [Schedule engine](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/schedule_engine.py): domain logic · Recurrence, rotation, streak, and due-date rules · `custom_components/choreops/engines/schedule_engine.py`
- [Economy engine](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/economy_engine.py): domain logic · Points and XP calculations · `custom_components/choreops/engines/economy_engine.py`
- [Gamify engine](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/gamification_engine.py): domain logic · Badges, streaks, and game-state computation · `custom_components/choreops/engines/gamification_engine.py`
- [Stats engine](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/engines/statistics_engine.py): domain logic · Reporting and aggregate statistics computation · `custom_components/choreops/engines/statistics_engine.py`

### State & migration

Persistence, repair, and schema evolution

- [Store](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/store.py): persistent storage · Home Assistant storage boundary for integration state · `custom_components/choreops/store.py`
- [Migrations](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/migrations/modern.py): schema evolution · Modern and legacy data migration paths · `custom_components/choreops/migrations/modern.py`
- [Boot repairs](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/integrity/boot_repairs.py): startup repair · Repairs inconsistent or partially migrated state · `custom_components/choreops/integrity/boot_repairs.py`

### Presentation

Dashboards, entities, translations, and branding

- [Entities](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/entity.py): HA entities · Shared entity base and integration surface · `custom_components/choreops/entity.py`
- [Sensors](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/sensor.py): entity platform · State exposure for automations and dashboards · `custom_components/choreops/sensor.py`
- [Legacy sensors](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/sensor_legacy.py): compat entity · Backwards-compatible sensor platform · `custom_components/choreops/sensor_legacy.py`
- [Buttons](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/button.py): entity platform · User-triggered control entities · `custom_components/choreops/button.py`
- [Selects](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/select.py): entity platform · Choice and mode entities · `custom_components/choreops/select.py`
- [Calendar](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/calendar.py): entity platform · Schedule-facing calendar entity · `custom_components/choreops/calendar.py`
- [Helpers](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/helpers/__init__.py): transformation layer · Shared adapters between domain objects and HA payloads · `custom_components/choreops/helpers/__init__.py`
- [Dashboard builder](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/helpers/dashboard_builder.py): presentation helper · Builds dashboard content from runtime state · `custom_components/choreops/helpers/dashboard_builder.py`
- [Dashboards](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/dashboards/dashboard_registry.json): templated UI · Registry, templates, preferences, and dashboard translations · `custom_components/choreops/dashboards/dashboard_registry.json`
- [Translations](https://github.com/ccpk1/choreops/blob/main/custom_components/choreops/translations/en.json): i18n · Integration text and custom notification/report strings · `custom_components/choreops/translations/en.json`
- [Branding](https://github.com/ccpk1/choreops/tree/main/custom_components/choreops/brand): assets · Brand assets and icon metadata for HA presentation · `custom_components/choreops/brand`

### Tooling & QA

Repository validation, release, and tests

- [Tests](https://github.com/ccpk1/choreops/blob/main/tests/README.md): scenario/contract tests · Scenario, migration, entity, service, and workflow coverage · `tests/README.md`

## Connections

- Config flow → Store: creates state · Initial setup writes integration state
- Options flow → Store: updates state · Runtime options are persisted
- Integration → System manager: wires lifecycle · Setup and teardown coordination
- Integration → Services: registers · Exposes HA services on setup
- Integration → Entities: registers entities · Attaches platform entities
- Services → Chore manager: dispatches · Service calls enter chore workflows
- Services → Reward manager: dispatches · Service calls enter reward workflows
- Services → Economy manager: dispatches · Service calls enter points workflows
- Services → Gamify manager: dispatches · Service calls enter game workflows
- Services → Stats manager: dispatches · Service calls enter reporting workflows
- Action handler → Notification manager: feeds back · Action responses re-enter notification workflows
- Chore manager → Chore engine: uses · Delegates chore rules to domain logic
- Chore manager → Schedule engine: uses · Delegates scheduling and recurrence rules
- Reward manager → Economy engine: uses · Reward costs and payouts affect economy rules
- Economy manager → Economy engine: uses · Points and XP calculations
- Gamify manager → Gamify engine: uses · Badge and progression logic
- Stats manager → Stats engine: uses · Rollups and reporting aggregates
- System manager → Store: loads/saves · Owns state persistence lifecycle
- Store → Migrations: evolves via · Storage schema is migrated across versions
- System manager → Boot repairs: repairs · Startup repair handles inconsistent state
- Helpers → Dashboard builder: supports · Helper layer feeds dashboard generation
- Dashboard builder → Dashboards: renders · Generated payloads populate templates and registry
- UI manager → Dashboard builder: coordinates · Presentation orchestration for dashboards and controls
- UI manager → Entities: syncs · Keeps UI state aligned with entities
- Entities → Sensors: implements · Primary sensor surface
- Entities → Buttons: implements · Button control surface
- Entities → Selects: implements · Select control surface
- Entities → Calendar: implements · Calendar surface
- Entities → Legacy sensors: compatibility · Legacy sensor support remains available
- Chore manager → Store: persists · Chore updates are written back to storage
- Economy manager → Store: persists · Points/accounting state is stored
- Gamify manager → Store: persists · Progression state is stored
- Stats manager → Store: reads · Reports consume stored operational data
- Translations → Dashboards: localizes · Dashboard text is translated separately
- Branding → Entities: brands · Brand assets shape HA presentation
- Tests → Config flow: covers · Setup flow contract tests
- Tests → Services: covers · Service and action contract tests
- Tests → Store: covers · Persistence and migration tests
- Tests → Dashboards: covers · Dashboard generation and template tests
- Tests → Chore engine: covers · Domain logic regression tests
- Tests → Gamify engine: covers · Game logic regression tests
