mirror of
https://github.com/Hestia-Homes/Model.git
synced 2026-06-08 11:17:27 +00:00
Wires PCDB main heating index + secondary heating type into the three open fixtures. All three certs lodge: - Vaillant ecoTEC PCDB index (000480=16839 pro 28, 000487=18119 sustain 28, 000516=18118 sustain 24) at main_heating_data_source=1. - Electricity Electric Panel/convector secondary (SAP code 691) at Table 11 fraction 0.10 (gas main + any secondary, page 188). - number_baths (000480=0, 000487=1, 000516=1). Confirmed against SAP 10.2 (14-03-2025) Table 11 page 188: "All gas, liquid and solid fuel systems" main + "all secondary systems" → fraction 0.10. PDF arithmetic on each fixture matches: 000480: 12398.58 × 0.10 = 1239.86 kWh secondary ✓ 000487: 10834.78 × 0.10 = 1083.48 kWh secondary ✓ 000516: 12410.32 × 0.10 = 1241.03 kWh secondary ✓ Impact on continuous SAP delta (target <0.01): fixture | pre S18a | post S18a | status --------|----------|-----------|--------- 000480 | +7.0885 | +0.0012 | ✓ within 0.01 000487 | +5.5285 | -1.9586 | over-corrected 000516 | +6.8375 | +0.0349 | nearly closed (0.04) 000480 hits the 0.01 continuous gate — first time outside 000490. 000516 is within 0.04 (was +6.84). 000487 swung from +5.5 to -2.0, suggesting the PCDB 18119 efficiency cascade diverges from what the PDF assumes for that specific boiler — separate slice. The previous fixture-lodgement gap was the dominant cost residual: (242) secondary cost was £0 and (240) main heating was over-counting because no PCDB efficiency was applied. Both close in this slice. The remaining (251) standing charges (£120) gap is a calculator-side issue addressed in the next slice (Table 12a page 191). 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/.