mirror of https://github.com/Hestia-Homes/Model.git synced 2026-06-08 11:17:27 +00:00

History

Khalim Conn-Kowlessar aa2c7a9171 slice S-B7: per-end-use fuel cost — HW uses water-fuel, lighting always electric SAP 10.3 §12 charges fuel costs by end-use, not by main heating fuel. For a gas-heated dwelling with an electric immersion hot-water cylinder, HW bills at the electric rate (13.19 p/kWh) not the gas main-heating rate (3.48 p/kWh) — a 3.8× cost difference for HW that propagates straight to ECF. Lighting, central-heating pumps, and fans always electric regardless of main fuel. Discovered by hand-tracing cert 8035-9023 (Detached bungalow, actual SAP 43, predicted 63). Trace showed our hot-water + lighting + pumps lines were charging mains-gas rates throughout, under-counting cost by ~£290/yr. 100-cert parity probe (biggest single Session-B slice so far): MAE 5.70 → 4.90 (-0.80, -14%) RMSE 7.48 → 6.68 (-11%) within ±1: 20% → 24% within ±3: 37% → 46% within ±5: 54% → 67% bias +1.50 → -1.44 (over-corrected by ~3 SAP points) The over-correction (bias now slightly negative) means we're now under-predicting on average. Next slice tackles where we're charging too much electricity — probably HW on dwellings with combi boilers (no immersion, water still on main fuel) and the water_heating_code 901 ("from main system") inheritance path. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>		2026-05-18 14:54:24 +00:00
..
src/domain	slice S-B7: per-end-use fuel cost — HW uses water-fuel, lighting always electric	2026-05-18 14:54:24 +00:00
pyproject.toml	slice 13: to_rows(properties) returns pd.DataFrame	2026-05-16 16:43:28 +00:00
README.md	added potential file scaffolding:	2026-05-15 10:56:53 +00:00

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/.