Model/packages
Khalim Conn-Kowlessar d56fef4d62 §6 slice 3: _g_perpendicular honours SapWindow.window_transmission_details
Elmhurst lodges per-window g⊥ via Manufacturer-source
window_transmission_details.solar_transmittance on every window — the
Table 6b code lookup is the cascade fallback, not the primary path.
Without this the orchestrator picks Table 6b defaults that don't match
the worksheet (e.g. glazing_type=4 defaults to low-E soft 0.63, but the
manufacturer-declared value 0.76 is what the §6 row uses).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-20 20:34:05 +00:00
..
domain §6 slice 3: _g_perpendicular honours SapWindow.window_transmission_details 2026-05-20 20:34:05 +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/.