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 049694e1e6 Slice 29: §9a energy requirements cascade pin (72/72) 
Adds `energy_requirements_section_from_cert(epc)` to the cert→inputs
cascade. Composes §8 (98c)m + Table 11 secondary fraction + per-system
efficiencies into (201)..(221) line refs via the existing
`space_heating_fuel_monthly_kwh` orchestrator.

Extracts `_main_heating_efficiency(epc)` as a shared helper — same eff
derivation as the inline `cert_to_inputs` flow (PCDB winter override →
Table 4a/4b seasonal → heat-network 1/DLF override). Single source of
truth for §4 and §9a.

Worksheet display convention: when no secondary system is lodged the
PDF displays (208) = 0 (not the fallback 100% electric efficiency). The
per-system fuel formula already collapses to 0 via fraction_201 = 0, so
this is presentation-only; the helper zeros (208) when
`secondary_fraction == 0`. 000474 (no secondary) now matches exactly.

Adds §9a LINE_ constants to all 6 fixtures — (201), (202), (206), (207),
(208), (211)m, (211), (213)m, (213), (215)m, (215), (221). Extracted
from `sap worksheets/U985-0001-NNNNNN.txt` PDF blocks.

Cascade scoreboard: 396/396 → 468/468 (§7..§9a closed).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-24 00:16:12 +00:00
..
domain Slice 29: §9a energy requirements cascade pin (72/72) 2026-05-24 00:16:12 +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/.