Model/packages
Khalim Conn-Kowlessar f863598d39 Slice 85: bulk-update cohort 000516 hand-built for Cat A diff parity
Closes 23 of 24 mapper-vs-hand-built load-bearing divergences by
populating fields the Elmhurst mapper extracts from Summary_000516.
pdf but the original hand-built left at their `make_minimal_sap10_
epc` / dataclass-default values. Every change is cascade-equivalent —
all 11 `_FIXTURE_PINS["000516"]` SapResult pins remain GREEN against
worksheet `SAP value 62.7937`.

000516-specific deltas:

- `wall_thickness_measured=True` on Main (Summary lodges 400 mm).
- `floor_type="Above unheated space"` (exposed timber floor, not
  Ground floor) — matches the cert's `is_exposed_floor=True` for
  the lowest Main floor.
- `roof_insulation_location="None"` — the Summary lodges the literal
  string "None" for an uninsulated roof; mapper surfaces it
  verbatim.

Standard Cat A additions (per Slice 72/75/78/82 pattern): floor
descriptive fields, 6 ventilation zero counts, draught_lobby=True,
pressure_test="Not available", top-level descriptive strings +
booleans, `number_of_storeys=3` (Main ground + first + RIR),
shower_outlets="Non-electric shower",
central_heating_pump_age_str="Unknown".

Diff count: 24 → **1**. Remaining diff is `sap_windows: LEN 5 vs 2`
— closes via Slice 86.

Pyright net-zero on the touched fixture.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-25 18:15:57 +00:00
..
domain Slice 85: bulk-update cohort 000516 hand-built for Cat A diff parity 2026-05-25 18:15:57 +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/.