Model/packages
Khalim Conn-Kowlessar 4ac4f7da27 Cohort residual slice 14: 000477 detailed RR lodgement closes to delta=0
Updates 000477's build_epc to lodge the Detailed §3.10 RR per the U985
worksheet — 2 stud walls @ 100mm mineral wool (U=0.36), 2 slope panels
uninsulated (U=2.30), 2 gable walls (U=0.25), plus roof_insulation_
thickness=300 on the storey-1 ceiling (the 16.20 m² External roof Main
@ U=0.14 line). Door count corrected 2 → 1 to match the worksheet's
single external door entry (3.70 W/K at 1.85 m² × 2.0).

Impact (e2e):
  SAP integer 67 → 65 = PDF (Δ=0). 000477 un-xfailed (third Elmhurst
  fixture at delta=0 after 000474 + 000490).

Side effect: golden cert 0240-0200-5706-2365-8010 (detached TFA 202
age J) drifts from Δ=0 → Δ=-12. Its API response carries
`sap_room_in_roof.room_in_roof_type_1` (gable lengths + types) +
description "Roof room(s), insulated (assumed)" that our mapper
doesn't yet extract — so the Simplified Type 1 fallback at U_RR_
default(J)=0.30 adds the missing RR heat loss for an 83.2 m² RR
floor. _SAP_TOLERANCE widens 11 → 13 with documentation; tightens
back once the mapper extracts gable lengths + retrofit-insulation
description signal (handover ticket).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-22 19:44:54 +00:00
..
domain Cohort residual slice 14: 000477 detailed RR lodgement closes to delta=0 2026-05-22 19:44:54 +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/.