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 67564caffc Slice 76: 1:1 windows expansion in cohort 000480 (2 → 7 entries) 
Closes the final `sap_windows: LEN 7 vs 2` divergence by replacing
the cohort 000480 hand-built's 2-window collapsed encoding with 7
SapWindow entries mirroring the Summary §11 1:1. Single glazing-type
group (PVC double / g⊥=0.76 / U=2.8); per-bp totals preserved:

  Main NE (orient=2): 8.74 m² split into 2.16 + 1.92 + 0.6 + 1.32
    + 2.04 + 0.7 (6 rows)
  Ext1 SW (orient=6): 1.80 m² unchanged

Mapper interleaves the Ext1 SW row between Main NE rows 4 and 5; the
hand-built mirrors that order so list-position diffs are zero.
`window_location` carries "Main" or "1st Extension" — same string-
encoded per-bp lookup pattern as Slice 69 (cohort 000474).

Cascade output unchanged: all 11 `_FIXTURE_PINS["000480"]` SapResult
pins remain GREEN at 1e-4 against worksheet `SAP value 61.2986`.

**Cohort 000480 is now fully Layer-2 GREEN** —
`test_from_elmhurst_site_notes_matches_hand_built_000480` passes with
zero load-bearing divergences between the mapped EpcPropertyData and
the hand-built fixture.

Full sweep: 104 passed (was 103 pre-Slice-74; +1 new diff test),
10 failed (same 10 001479-related as before). Pyright net-zero.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 17:53:53 +00:00
..
domain Slice 76: 1:1 windows expansion in cohort 000480 (2 → 7 entries) 2026-05-25 17:53:53 +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/.