mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
3aba735eee
Updates 000480's build_epc to lodge the §3 worksheet inputs that the prior Simplified Type 1 fallback was approximating: - Detailed §3.10 RR (7 surfaces on Main): 1 flat ceiling 2.31 + 2 stud walls 4.24 + 2 slopes 10.78 — all uninsulated (Table 17 row "none" → U=2.30); plus 2 gable walls 11.33 / 8.47 routed to party at U=0.25 (Table 4 "as common wall"). Per [[feedback-no- misleading-insulation-type]] uninsulated surfaces leave insulation_type unset. - roof_insulation_thickness=300 on Ext1 (Main has no storey-below external roof — the RR floor 19.83 m² covers the entire Main footprint 15.28 m²). Back-solves from U=0.14 / Table 16 row 300mm. - is_exposed_floor=True on Ext1 floor=0 — 000480 line 207 lodges "Exposed floor Ext1 17.01 × U=1.20" (28b), routing via Table 20 rather than the BS EN ISO 13370 ground-contact cascade. The Ext1 sits over an unheated space (passageway / over-garage), not soil. Impact: SAP integer 65 → 67 mid-slice (the Simplified Type 1 fallback was over-estimating the RR shell; detailed lodgement + exposed-floor corrects toward worksheet). The remaining +6 overshoot is the LINE_31 gable_wall overcount bug — closed in slice 16b alongside the new e2e test pin and 000477 door_count revision. No tests pinned for 000480 yet — the new e2e test_elmhurst_000480_ end_to_end_sap_score_matches_pdf lands in 16b once the calculator fix closes Δ=0. Existing 409 tests stay green at this commit. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| domain | ||
| fetchers | ||
| repos | ||
| utils | ||
| 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/.