mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
f09e83b6a1
P5.9 exposed the four primary-energy components as absolute kWh/yr keys (space_heating_primary_kwh_per_yr, …). HANDOVER_SYSTEMATIC_REVIEW §11 specifies these as `_pe_kwh_per_m2` because primary energy enters the rating equation per floor area. Renamed to match the sketch: - space_heating_pe_kwh_per_m2 - hot_water_pe_kwh_per_m2 - other_pe_kwh_per_m2 - pv_pe_offset_kwh_per_m2 Chain check now verifies max(0, sum − pv_offset) ≈ result.primary_energy_kwh_per_m2 (the top-level per-m² field). Absolute kWh/yr values remain recoverable via tfa_m2 on `intermediate`. |
||
|---|---|---|
| .. | ||
| src/domain | ||
| pyproject.toml | ||
| README.md | ||
domna-domain
Shared domain types — Property, Properties, BaselinePerformance, Plan, PlanPhase, Scenario, ScenarioPhase, ScenarioSnapshot, Recommendation, OptimisedPackage, EpcPropertyData, etc.
Boundary: types only. No persistence, no IO, no business logic. Other packages and services depend on domna-domain; this package depends on nothing internal.
Domain definitions live in ../../CONTEXT.md. New types added here must match the glossary terms.
Layout
src/domain/
├── __init__.py
├── property.py # Property, Properties, PropertyIdentity
├── site_notes.py
├── landlord_overrides.py
├── baseline_performance.py # lodged + effective pair (ADR-0004)
├── plan.py # Plan, PlanPhase, OptimisedPackage
├── scenario.py # Scenario, ScenarioPhase, ScenarioSnapshot (ADR-0005)
├── recommendation.py
├── geospatial.py
├── solar.py
├── anomaly_flags.py
└── ml/
├── __init__.py
├── transform.py # EpcMlTransform (versioned per §8.3)
└── schema.py
When datatypes/epc/domain/ folds in, the EPC schema types move under src/domain/epc/.