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 1821f3fef3 Slice 27: round BS EN ISO 13370 floor U to 2 d.p. per RdSAP10 §5.12 
Spec text (RdSAP 10 §5.12, p.46): "Unless provided by the assessor the
floor U-value is calculated according to BS EN ISO 13370 using its area
(A) and exposed perimeter (P) and rounded to two decimal places." Our
u_floor returned the raw formula output — that's a 0.0040 W/m²K precision
gap vs the PDF that was costing 0.03–0.13 W/K on §3 LINE_33 for 4 fixtures.

§3 LINE_33 residuals collapsed:
  000474: 0.0296 → 0.0032
  000477: 0.1246 → 0.0013
  000480: 0.0168 → 0.0075
  000490: 0.0282 → 0.0013
  000516: 0.0038 → 0.0038 (exposed floor, Table 20 — unaffected)
  000487: 37.88 (RR defect, slice 25)

+3 SapResult pin closures (000474/477/490 ECF now pass at abs=1e-4).
Pin counts: section_cascade 151/35 unchanged (residuals shrunk but still
> 1e-4); e2e SapResult 24→27 PASS.

Remaining LINE_33 0.001–0.0075 W/K is wall + party-wall area precision —
PDF stores 2-d.p.-rounded element areas (slice 27b).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-23 08:50:33 +00:00
..
domain Slice 27: round BS EN ISO 13370 floor U to 2 d.p. per RdSAP10 §5.12 2026-05-23 08:50:33 +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/.