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 3b9fa936f0 §8c slice 2: 6-fixture ALL_FIXTURES conformance (all-zero) with shared template constants 
Shared SECTION_8C_ALL_ZERO_MONTHLY / SECTION_8C_ETA_LOSS_ALL_ONE / SECTION_8C_INTERMITTENCY_MONTHLY constants live in _elmhurst_fixtures.py; each of the 6 fixtures references them via plain attributes plus SECTION_8C_COOLED_AREA_FRACTION = 0.0 and the per-line LINE_103/106/107/108 + LINE_107_ANNUAL_KWH pins.

(100), (102), (104) values depend on H × (24−T_e) per fixture and are not pinned here — the algebra is exercised by the synthetic-positive leaf/orchestrator tests in slice 1. First cooling-enabled cert will need a fixture pinning those lines; deferred per Q10 grilling decision.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-21 07:54:55 +00:00
..
domain §8c slice 2: 6-fixture ALL_FIXTURES conformance (all-zero) with shared template constants 2026-05-21 07:54:55 +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/.