Model/packages
Khalim Conn-Kowlessar b536b46ab4 Cohort residual slice 3: Table 4f gas-combi pumps_fans = 160 kWh/yr
Replaces the static `_DEFAULT_PUMPS_FANS_KWH_PER_YR = 130` for
gas-combi main heating systems with the SAP10.2 Table 4f cascade
value: 115 kWh/yr (230c central heating pump, post-2013 install) +
45 kWh/yr (230e main heating flue fan, balanced/condensing) = 160.
Selection keyed by `main.main_heating_category` — currently only
category 2 (Gas-fired boilers); other categories fall back to the
legacy 130 sentinel pending the next fixture exercising them.

Adds `_PUMPS_FANS_KWH_BY_MAIN_CATEGORY` lookup. Both `CalculatorInputs.
pumps_fans_kwh_per_yr` and the `_fuel_cost(...)` pumps_fans arg now
share the same per-cert value.

E2E pins: new parametrized test
`test_elmhurst_end_to_end_pumps_fans_kwh_matches_u985_worksheet`
asserts `result.pumps_fans_kwh_per_yr == 160` at abs=1e-3 for the
2 e2e fixtures (000474, 000490).

Impact on 000490: cost £803.62 → £807.58 (PDF £807.54, Δ +£0.04 ≈ 0%);
continuous SAP 57.77 → 57.57 (PDF 57.40, Δ +0.17 — was +0.38).
SAP integer still 58 vs PDF 57 — remaining residual is the SAP
rating constants (rating.py uses SAP 10.3 deflator 0.36 / slope
16.21/120.5; PDF lodges SAP 10.2 0.42 / 13.95/121) — next slice.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-22 11:21:14 +00:00
..
domain Cohort residual slice 3: Table 4f gas-combi pumps_fans = 160 kWh/yr 2026-05-22 11:21:14 +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

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