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 43cc16bc65 §8f slice 1: fabric_energy_efficiency_kwh_per_m2_yr + 6-fixture conformance + atomic wiring 
Spec line 7898: (109) = (98a) ÷ (4) + (108). New `worksheet/fabric_energy_efficiency.py` exposes a free function (no dataclass — single scalar output); `SpaceHeatingResult.space_heating_requirement_kwh_per_yr` (Σ(98a)) added so the spec literal — pre Appendix H solar offset — is the FEE input, not Σ(98c).

cert_to_inputs computes FEE from local SpaceHeatingResult + SpaceCoolingResult and passes via new `CalculatorInputs.fabric_energy_efficiency_kwh_per_m2_yr` (default 0.0 for backwards compat); calculator pass-through to `SapResult.fabric_energy_efficiency_kwh_per_m2_yr`. MonthlyEntry untouched — FEE has no per-month physics, only an annual scalar.

Six Elmhurst fixtures all (98b)=0 + (108)=0 → LINE_109 = LINE_99 exactly; ALL_FIXTURES asserts within 5e-3 tolerance (display-rounding floor inherited from LINE_98C_ANNUAL_KWH pins). Round-trip test asserts SapResult.fee equals space_heating_kwh_per_yr / TFA for the SAP10 minimal cert.

§11 compliance conditions (different ventilation / HW / lighting / gains column) are deferred — the FEE here is computed off rating-conditions inputs as a transparency output. Future §11 slice invokes the same function with §11-conditions upstream values.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 08:12:45 +00:00
..
domain §8f slice 1: fabric_energy_efficiency_kwh_per_m2_yr + 6-fixture conformance + atomic wiring 2026-05-21 08:12:45 +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/.