Model/packages
Khalim Conn-Kowlessar 2d3355ee48 Slice 86: 1:1 windows expansion in cohort 000516 (2 → 5 entries)
Closes the final `sap_windows: LEN 5 vs 2` divergence by replacing
the cohort 000516 hand-built's 2-window collapsed encoding with 5
SapWindow entries mirroring the Summary §11 1:1. Single-bp dwelling;
single glazing-type group (PVC double / g⊥=0.76 / U=2.8); per-
orientation totals preserved:

  NE (orient=2): 3.88 m² split 2.15 + 1.73 (2 rows)
  SW (orient=6): 4.43 m² split 1.94 + 1.67 + 0.82 (3 rows)

Mapper interleaves NE/SW rows; hand-built mirrors that order so
list-position diffs are zero.

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

**Cohort 000516 is now fully Layer-2 GREEN.**

**All 6 cohort certs (000474, 000477, 000480, 000487, 000490, 000516)
are now Layer-2 zero-diff** — the mapper produces a load-bearing-
field-equivalent EpcPropertyData for every cohort cert. This clears
the way for closing cert 001479 (the load-bearing API↔Elmhurst
parity-test fixture; Slice 62 skeleton at 2/11 cascade pins green,
gap −3.02 SAP) and then adding the API mapper diff test (Layer 3)
and the production acceptance test (Layer 4 — ±0.5 of published SAP
69 for cert 0535-9020-6509-0821-6222).

Full sweep: 107 passed (was 105 pre-Slice-84; +2 new diff tests for
000490 + 000516), 10 failed (same 10 001479-related). Pyright net-
zero on every touched fixture across Slices 71–86.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:19:51 +00:00
..
domain Slice 86: 1:1 windows expansion in cohort 000516 (2 → 5 entries) 2026-05-25 18:19:51 +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

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/.