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 f37970666e §8c slice 3: CalculatorInputs + MonthlyEntry + SapResult + cert_to_inputs wiring (atomic) 
Full §8 mirror per Q9 grilling: CalculatorInputs.space_cooling_monthly_kwh (default (0,)*12), MonthlyEntry.space_cool_requirement_kwh, SapResult.space_cooling_kwh_per_yr. _solve_month indexes into the cooling tuple and calculate_sap_from_inputs sums the per-month entries.

cert_to_inputs calls space_cooling_monthly_kwh with f_C=0 and cooling_gains=(0,)*12 — RdSAP convention since the cert never lodges cooled-area data and every `has_fixed_air_conditioning=False` cert collapses (107) to zero. The first cooling-enabled fixture needs a cooling_gains_from_cert helper + RdSAP cooled-area defaulting rule (deferred — SPEC_COVERAGE §8c row).

Round-trip test pins inputs.space_cooling_monthly_kwh = (0,)*12, result.space_cooling_kwh_per_yr = 0.0, and every MonthlyEntry.space_cool_requirement_kwh = 0.0 for a typical SAP10 minimal cert.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 07:58:34 +00:00
..
domain §8c slice 3: CalculatorInputs + MonthlyEntry + SapResult + cert_to_inputs wiring (atomic) 2026-05-21 07:58:34 +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/.