Model/packages/domain
Khalim Conn-Kowlessar 778b150c98 Slice 21e: §4 water heating cascade pins (42/54 PASS)
Extracts `water_heating_section_from_cert(epc) -> WaterHeatingResult`
helper to expose the full §4 cascade output for tests (mirrors the
existing private `_water_heating_worksheet_and_gains`, drops unused
args).

§4 pins at abs=1e-4:
  scalar (2 line refs × 6 = 12): (42) occupancy, (43) annual avg L/day
  monthly (7 line refs × 6 × 12 months = 504 assertions across 42
   parametrized cases): (44)m daily, (45)m energy content,
   (46)m distribution loss, (61)m combi loss, (62)m total demand,
   (64)m output, (65)m heat gains

Per-fixture results:
  000474:    9/9 PASS  ✓
  000477:    5/9       — combi loss (61)m diverges → cascades to
                          62/64/65 monthly
  000480:    9/9 PASS  ✓
  000487:    1/9       — LINE_43 + every monthly fails (HW lodgement
                          defect: number_baths=1 but PDF arithmetic
                          suggests different shower/bath profile)
  000490:    9/9 PASS  ✓
  000516:    9/9 PASS  ✓

4/6 fixtures close §4 fully — strong cascade floor. The 000477 combi
loss residual is a specific Table 3c sub-row issue; the 000487 §4 gap
is part of its broader cert lodgement defect (RR + HW lodgement).

Cumulative scoreboard:
  §1: 12 PASS / 0 FAIL
  §2: 96 PASS / 0 FAIL
  §3:  1 PASS / 23 FAIL  (precision residuals + 000487 RR)
  §4: 42 PASS / 12 FAIL
  ---
  total: 151 PASS / 35 FAIL

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-22 23:19:21 +00:00
..
src/domain Slice 21e: §4 water heating cascade pins (42/54 PASS) 2026-05-22 23:19:21 +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

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