junte/Model
1
0
Fork 0
mirror of https://github.com/Hestia-Homes/Model.git synced 2026-06-08 11:17:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
Model/packages
History
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
..
domain Slice 21e: §4 water heating cascade pins (42/54 PASS) 2026-05-22 23:19:21 +00:00
fetchers added potential file scaffolding: 2026-05-15 10:56:53 +00:00
repos added potential file scaffolding: 2026-05-15 10:56:53 +00:00
utils added potential file scaffolding: 2026-05-15 10:56:53 +00:00
README.md added potential file scaffolding: 2026-05-15 10:56:53 +00:00

README.md

Shared packages

Workspace packages consumed by services/*. Each package is its own Python distribution with its own pyproject.toml; services import via the workspace dependency mechanism ({ workspace = true }).

Package Purpose
domain/ Shared domain types — Property, BaselinePerformance, Plan, Scenario, EpcPropertyData, etc. No persistence, no IO, no business logic.
repos/ Persistence layer — one repo per aggregate. Owns the SQL. Depends on domain.
fetchers/ External API clients (gov EPC, Ofgem, Google Solar, etc.). Depend on domain for response shapes.
utils/ Cross-cutting infra — logging, S3, CloudWatch URL builders, SQS task helpers.

Adding a new shared package

Only when a real second consumer materialises. Don't pre-shatter (repos-epc, repos-property, ...) — split when a deployment needs to drop a dep, not before.

See ../ara_backend_design.md §11 for the broader monorepo layout and ../CONTEXT.md for the domain glossary that names the types living in domain/.