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 9113f30aa8 §8 slice 1: space_heating_monthly_kwh orchestrator + summer clamp + SpaceHeatingResult 
Adds the §8 orchestrator producing (95)..(99) line refs for all 12 months.
Composes the existing monthly_heat_requirement_kwh leaf with the spec
inclusion rule (Table 9c step 10 final clause):

  "Include the heating requirement for each month from October to May
   (disregarding June to September)"

Jun..Sep are zeroed regardless of computed value, on top of the per-month
value clamp (< 1 kWh / negative).

SpaceHeatingResult exposes (95) useful gains, (97) heat loss rate, (98a)
space heating requirement, (98b) solar space heating (always 0 — Appendix
H deferred), (98c) total, Σ(98c) annual + (99) per-m². All length-12
tuples + 2 scalars.

Driven by Elmhurst 000490 (98c) annual = 11183.2752 kWh to abs=5e-3 kWh.
Without the summer clamp the current calculator over-predicts annual by
+1575 kWh (+14%) on this fixture; the clamp closes the gap to spec.

Slice 3 wires CalculatorInputs.space_heating_monthly_kwh + cert_to_inputs;
calculator stops calling monthly_heat_requirement_kwh inline.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 22:11:22 +00:00
..
domain §8 slice 1: space_heating_monthly_kwh orchestrator + summer clamp + SpaceHeatingResult 2026-05-20 22:11:22 +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/.