Commit graph

441 commits

Author SHA1 Message Date
Khalim Conn-Kowlessar
b1478cff63 Slice S0380.145: Table 4e temperature adjustment — apply (92)m → (93)m offset per Table 9c step 8
SAP 10.2 Table 4e (PDF p.170-173) "Heating system controls":

  3. The 'Temperature adjustment' modifies the mean internal
     temperature and is added to worksheet (92)m.

SAP 10.2 Table 9c step 8 (PDF p.184): "Apply adjustment to the mean
internal temperature from Table 4e, where appropriate".

Pre-slice the cascade hardcoded `control_temperature_adjustment_c
=0.0` at all three call sites of `mean_internal_temperature_monthly`
and `space_heating_section_with_results`. The §8 heat loss calc
therefore drove off (92)m unchanged → §8 SH demand under-counted on
every cert whose `main_heating_control` lodges a non-zero adjustment.

Table 4e adjustments by code (full p.170-173 coverage):

  Group 0 — No heating system:
    2699: +0.3
  Group 1 — Boilers with radiators/UFH (+ micro-CHP):
    2101, 2102: +0.6   (no thermo / programmer-only)
    2103..2113: 0
  Group 2 — Heat pumps:
    2201, 2202: +0.3
    2203..2210: 0
  Group 3 — Heat networks:
    2301, 2302: +0.3
    2303..2314: 0
  Group 4 — Electric storage:
    2401 (Manual charge):                  +0.7
    2402 (Automatic charge):               +0.4
    2403 (Celect):                         +0.4
    2404 (HHR controls):                    0
  Group 5 — Warm air:
    2501, 2502: +0.3
    2503..2506: 0
  Group 6 — Room heaters:
    2601: +0.3
    2602..2605: 0
  Group 7 — Other systems:
    2701, 2702: +0.3
    2703..2706: 0

New `_control_temperature_adjustment_c(main)` helper consults
`_CONTROL_TEMPERATURE_ADJUSTMENT_BY_CODE` (52 entries, full Table 4e
coverage). Strict-raises `UnmappedSapCode` on present-but-unmapped
codes per [[reference-unmapped-sap-code]] so spec-coverage gaps
surface at test time. The helper is wired to all three call sites
of the MIT/SH orchestrators in cert_to_inputs.

Corpus impact — closes the +2.5 SAP cluster substantially:

  Variant | control |  pre  →  post  | delta
  ------- | ------- | -------------- | -----
  e3 (401)|  2401   | +2.55 → -0.09  | -2.46  (massive close)
  e6 (404)|  2402   | +1.33 → -0.17  | -1.50
  e7 (408)|  2402   | +1.29 → -0.20  | -1.49
  e2 (524)|  2502   | +0.47 → -0.18  | -0.65
  e5 (402)|  2402   | +0.07 → -1.43  | -1.50  (regressed —
                                              previously net-zero
                                              from offsetting bugs)

Cumulative |ΔSAP| across these 5: 5.71 → 2.07 (-3.64 pts closed).
electric 3 / 6 / 7 / 8 / 9 now all within 0.20 SAP of worksheet.
Golden fixtures unchanged (API certs in those tests don't lodge
non-zero-adjustment control codes; suite stays 888 pass).

Extended handover suite: 888 pass, 0 fail (was 887 + 1 new AAA test).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 21:50:10 +00:00
Khalim Conn-Kowlessar
ec6661cbb6 Slice S0380.144: Table 11 — per-Table-4a-code secondary fraction dispatch for electric storage heaters + remove code 408 from §A.2.2 forced-secondary set
SAP 10.2 Table 11 (PDF p.188) "Fraction of heat supplied by
secondary heating systems" — the "Electric storage heaters (not
integrated)" row splits by Table 4a sub-type:

  - not fan-assisted:                                       0.15
  - fan-assisted:                                           0.10
  - high heat retention (as defined in 9.2.8):              0.10

Plus separate rows:
  Integrated storage/direct-acting electric systems:        0.10
  Electric room heaters:                                    0.20
  Other electric systems (e.g. underfloor):                 0.10

Cross-referenced with SAP 10.2 Table 4a (PDF p.166) Electric
storage codes:

  401: Old (large volume) storage heaters     — not fan-assisted
  402: Slimline storage heaters                — not fan-assisted
  403: Convector storage heaters               — not fan-assisted
  404: Fan storage heaters                     — fan-assisted
  405: Slimline + Celect                       — not fan-assisted
  406: Convector + Celect                      — not fan-assisted
  407: Fan + Celect                            — fan-assisted
  408: Integrated storage + direct-acting      — "Integrated"
  409: High heat retention                     — HHR
  421: Underfloor heating                      — "Other electric"

Pre-slice the cascade defaulted `_secondary_fraction` to 0.10 for
every forced electric-storage code (Elmhurst mapper leaves
`main_heating_category=None`, dispatch falls through to the
`_SECONDARY_HEATING_FRACTION_DEFAULT` 0.10), missing the 0.15
not-fan-assisted sub-row on codes 401/402/403/405/406.

Two compounding spec-citable fixes:

(a) New `_SECONDARY_FRACTION_BY_ELECTRIC_STORAGE_CODE` dispatch dict
    consulted before the category-based lookup in
    `_secondary_fraction`. Routes each Table 4a 4xx code to its
    Table 11 sub-row fraction.

(b) Code 408 removed from `_FORCE_SECONDARY_FOR_MAIN_CODES`.
    SAP 10.2 §A.2.2 (PDF p.~189) verbatim: "This applies to main
    heating codes 401 to 407, 409 and 421" — 408 is explicitly
    NOT in the spec's forced list. The integrated storage+direct-
    acting heater's direct-acting element acts as the secondary
    already, so the calculation doesn't add another.

Corpus impact (electric variants — Elmhurst mapper path):

- electric 3 (SAP 401): sec_frac 0.10 → 0.15; CO2 -117.84 →
  -108.88; PE -1121.97 → -1093.18. SAP / cost residual unchanged
  because the off-peak meter routes the cost calc through the
  `_ZERO_FUEL_COST_FOR_OFF_PEAK` sentinel + legacy scalar-field
  math which bills main and secondary at the same off-peak low
  rate (7.41 p/kWh) — main-vs-secondary split is cost-neutral.
- electric 5 (SAP 402): sec_frac 0.10 → 0.15; CO2 -11.08 → -2.48;
  PE -161.03 → -133.36. Same cost-invariance.
- electric 7 (SAP 408): forced-secondary removed → cascade secondary
  fuel kWh 891 → 0 (matches worksheet); CO2 -37.86 → -53.57;
  PE -498.47 → -549.37. SAP residual unchanged (same off-peak
  cost-invariance).
- electric 4/6/8/9: no change (categories 404/409/421 keep their
  existing 0.10 dispatch).

The remaining +2.55 SAP residual on electric 3 (+1.29 on electric 7)
is now confirmed to be driven by space-heating DEMAND undercount
(cascade SH demand 10083 kWh vs worksheet 11088 kWh for electric 3;
8914 vs 9529 for electric 7), not by sec_frac dispatch. That's a
separate slice — likely §9 MIT calc or §8 gains/HLC for storage-
heater R values, follow-up after this slice.

Extended handover suite: 887 pass, 0 fail (was 886 + 1 new AAA test).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 21:27:46 +00:00
Khalim Conn-Kowlessar
53ceb63624 docs: handover post S0380.141..143 (pcdb 1 closure via §9.4.11 + §4 cylinder gates + RdSAP 10 Table 29 inaccessible-cylinder insulation defaults)
Three slices on top of `8ee877e4` closed cert pcdb 1 from SAP +6.95
to +0.57 (-92% magnitude) via spec-citable fixes in three distinct
cascade areas.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 21:06:11 +00:00
Khalim Conn-Kowlessar
7f9074fca9 Slice S0380.142: §4 (61)m/(59)m cascade — cylinder presence gates combi=0 + primary loss applies for PCDB Table 322 boilers
SAP 10.2 §4 line 7702 (PDF p.137):

  Combi loss for each month from Table 3a, 3b or 3c (enter '0' if
  not a combi boiler)

SAP 10.2 Table 3 (PDF p.160) zero-loss list for primary circuit loss:

  Electric immersion heater
  Combi boiler (including when it is part of a combined heat pump and
  boiler package and provides all the hot water)
  CPSU (including electric CPSU)
  Boiler and thermal store within a single casing
  Separate boiler and thermal store connected by no more than 1.5 m
  of insulated pipework
  Direct-acting electric boiler
  Heat pump (...) with hot water vessel integral to package

Combi boilers are defined by Table 3's zero-loss list entry: they
provide instantaneous DHW with no storage vessel. A cert that lodges
a hot-water cylinder therefore has a non-combi heat generator —
the cylinder bypasses any instantaneous-DHW capability and the
boiler acts as a regular boiler for the DHW circuit.

Two compounding gaps for PCDB Table 322 (gas/oil boiler) records
with a lodged cylinder:

(a) (61)m combi loss: pre-slice the cascade routed every PCDB record
    through `pcdb_combi_loss_override` regardless of cylinder
    presence. For PCDB regular boilers (subsidiary_type=0, store_
    type=0, separate_dhw_tests=0) this dispatched to Table 3a row 1
    "Instantaneous without keep-hot" — 600 kWh/yr. Cert pcdb 1
    (Potterton KOA PCDB 716 + 110 L cylinder) exposed this: worksheet
    (61)m = 0 ; cascade was lodging 600 kWh/yr keep-hot loss on a
    regular oil boiler.

(b) (59)m primary loss: `_primary_loss_applies` gated on
    `main_heating_category in {1, 2}`. The Elmhurst path leaves
    `main_heating_category=None`, so the gate returned False even
    when the cert lodged a PCDB Table 322 (gas/oil boiler) record +
    a cylinder. Worksheet (59)m sum ~1177 kWh ; cascade was zero.

Fix:

- `_water_heating_worksheet_and_gains` now zeroes combi_loss_override
  whenever `epc.has_hot_water_cylinder` is True (top-level gate
  preceding the `pcdb_combi_loss_override` dispatch). Preserves the
  existing non-cylinder fallback for HP / no-PCDB / community-heat
  certs that lack a main_heating_category lodgement.

- `_primary_loss_applies` extends the Elmhurst-path fallback: when
  `main_heating_index_number` resolves to a PCDB Table 322 record,
  return True (the cert is implicitly a boiler — Table 3 row 1 covers
  any "heat generator (e.g. boiler) connected to a hot water storage
  vessel via insulated or uninsulated pipes").

Corpus impact:

- pcdb 1 (Potterton KOA + cylinder, the only PCDB Table 322 + cylinder
  combination in the corpus): SAP +3.40 → +2.86; cost -£75.68 →
  -£63.22; CO2 -397.02 → -328.74; PE -1601.74 → -1257.97.

- Golden cert 0390-2954-3640-2196-4175 (Firebird oil combi PCDF 9005
  + cylinder): PE -26.37 → -28.50; CO2 -2.55 → -2.75. Combi-loss
  removal (-600 kWh/yr) exceeded the primary-loss gain (~5-10 kWh
  given the cert's insulated pipework + thermostat lodging), so the
  net (62) shifted down. Direction is more spec-correct: the spec
  treats a combi feeding a cylinder as a regular boiler for DHW,
  matching the (61)m=0 + (59)m>0 worksheet behaviour.

Extended handover suite: 885 pass, 0 fail.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 20:53:19 +00:00
Khalim Conn-Kowlessar
6636f1c333 Slice S0380.141: §9.4.11 boiler interlock — extend −5pp adjustment to both space-heating efficiency and the PCDB Equation D1 water cascade
SAP 10.2 §9.4.11 (PDF p.30) "Boiler interlock":

  For the purposes of the SAP, an interlocked system is one in which
  both the space and stored water heating are interlocked. If either
  is not, the 5% seasonal efficiency reduction is applied to both
  space and water heating; if both are interlocked no reductions are
  made.

Table 4c (PDF p.169-170) lodges -5 for both Space and DHW columns on
the "No boiler interlock — regular boiler" row. Pre-slice the cascade
applied the -5pp adjustment ONLY to the `water_eff` scalar fallback
(`cert_to_inputs.py:4354`) and missed:

  (a) the SH efficiency path (cascade kept the raw PCDB winter eff for
      space heating);
  (b) the PCDB Equation D1 monthly cascade (Eq D1 received raw
      winter/summer values without the -5pp adjustment).

RdSAP §3 (PDF p.57) defines boiler interlock as "Assumed present if
there is a room thermostat and (for stored hot water systems heated
by the boiler) a cylinder thermostat. Otherwise not interlocked."
Cert pcdb 1 (Potterton KOA PCDB 716 + 110 L cylinder + Cylinder Stat:
No) reproduces the pattern: worksheet (210) = 60% = PCDB winter
65 - 5; worksheet (217)m monthly Eq D1 pivots on (winter 60,
summer 48) not (65, 53).

The SH path is further gated on `pcdb_main is not None` because
§9.4.11 only applies to "gas and liquid fuel boilers" — cert 000565
(ASHP Main 1) keeps its raw SH eff. The combi-fed-cylinder DHW path
(cert 000565 WHC 914 to PCDB combi Main 2) continues to receive its
existing -5pp via the `water_pcdb_main` gate (unchanged).

Corpus impact: pcdb 1 SAP residual +6.95 → +3.40; cost -£157.61 →
-£75.68; CO2 -845.81 → -397.02; PE -3135.30 → -1601.74. No other
variant has PCDB main + cylinder + no thermostat, so the other 24
corpus pins are unchanged.

Extended handover suite: 884 pass, 0 fail (was 883 + 1 new AAA test
pinning the §9.4.11 SH eff path).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 20:33:01 +00:00
Khalim Conn-Kowlessar
8ee877e44c docs: handover update — +2.5 SAP cluster is heterogeneous, not a shared cascade gap
Probed all three variants (electric 3, oil 1, solid fuel 2) in this
thread. Each has a different driver despite the matching magnitude:
- electric 3: §9 useful-demand calc for ctrl=3 storage heaters
- oil 1: HW efficiency for Table 4b oil boiler (cascade 86% vs ws ~65%)
- solid fuel 2: HW kWh lodged in different line ref (re-probe needed)

Tested combined-R hypothesis (effective_R = (1-frac)·R_main + frac·R_sec
per SAP 10.2 §9b) — the cascade currently DOES NOT pass secondary_fraction
to mean_internal_temperature_monthly, so effective_R = R_main. Monkey-
patching to inject combined R REGRESSES electric 3 (+2.55 → +3.17)
because raising R lowers cascade demand — opposite of needed direction.

Recommends taking the three variants as separate per-variant slices.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 19:20:43 +00:00
Khalim Conn-Kowlessar
c389645bfa docs: handover post S0380.138..140 (off-peak tariff cascade + §4 cylinder storage loss)
Three-slice handover covering:
- S0380.138: per-tariff Table 32 low-rate dispatch
- S0380.139: _is_off_peak_meter canonical normalization
- S0380.140: §4 (56)m cylinder storage loss (extractor + cascade)

Ranks next-slice candidates (top: +2.5 SAP cluster across electric 3,
oil 1, solid fuel 2 — likely shared Table 9 MIT bug).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 19:10:16 +00:00
Khalim Conn-Kowlessar
068088bc2f Slice S0380.140: §4 cylinder storage loss — extractor picks up §16 thermostat lodging + Table 2b note b restricts ×0.9 to boiler/warm-air/HP systems
Two compounding bugs were over-counting the SAP 10.2 §4 (56)m cylinder
storage loss by ~76 kWh/yr across all 17 cylinder-with-immersion
corpus variants (cascade HW kWh 2460.40 vs worksheet 2384.12):

(1) **Extractor gap.** Elmhurst Summary §15.1 "Hot Water Cylinder"
    block lodges `Cylinder Size` / `Insulation Thickness` but NOT
    `Cylinder Thermostat`. The thermostat is lodged separately in
    §16 "Recommendations" as `Cylinder thermostat (Already installed)`.
    The extractor only searched §15.1, so `cylinder_thermostat`
    resolved to None for every variant on property 001431. The
    cascade then defaulted `has_cylinder_thermostat=False`, applying
    SAP 10.2 Table 2b's ×1.3 "no thermostat" multiplier.

(2) **Cascade spec gap.** `_separately_timed_dhw` returned True for
    any cylinder-lodged cert regardless of HW fuel. Per SAP 10.2
    Table 2b note b) (PDF p.159):

    > "Multiply Temperature Factor by 0.9 if there is separate time
    >  control of domestic hot water (boiler systems, warm air systems
    >  and heat pump systems)"

    Electric immersion is NOT in the bracketed list — the ×0.9
    reduction is restricted to boiler / warm-air / HP systems. Pre-
    slice the cascade over-applied ×0.9 on electric-immersion certs.

Combined, the cascade computed TF = 0.60 × 1.3 × 0.9 = 0.702 vs the
worksheet's TF = 0.60 (base — thermostat present, immersion exempt).
After both fixes the cascade HW kWh matches the worksheet's (64) at
1e-3 precision (2384.116 vs 2384.12).

Corpus impact (16 cylinder-with-immersion variants on 18-hour meter):

| variant      | SAP_c shift | Cost shift |
|--------------|------------:|-----------:|
| electric 1   | -0.20 →   -0.06 |  -£3.34 |
| electric 2   | -1.27 →   +0.47 |  -£4.44 |
| electric 3   | +2.42 →   +2.55 |  -£2.91 |
| electric 5   | -0.06 →   +0.07 |  -£3.06 |
| electric 6   | +1.19 →   +1.33 |  -£3.20 |
| electric 7   | +1.14 →   +1.29 |  -£3.35 |
| electric 8   | -0.41 →   -0.26 |  -£3.50 |
| electric 9   | -0.24 →   -0.12 |  -£2.91 |
| solid fuel 4-11 | -0.45..-0.09 → -0.29..+0.10 | -£3 to -£4 |

The HW kWh line closes cleanly; some SAP residuals sign-flip slightly
because the cascade's now-correct HW kWh exposes the SH+Sec demand
mismatch for storage heaters (electric 3/6/7 — open driver is the
Table 11 `main_heating_category=None` default for codes 401/402,
queued for a mapper-side slice).

Tests:
- new AAA test `test_separately_timed_dhw_excludes_electric_immersion_per_table_2b_note_b`
- 16 corpus pins re-tightened (8 electric + 8 solid fuel)

Extended handover suite: 883 pass (was 882; +1 new test), 0 fail.
Pyright net-zero on touched files (43 → 43 errors, all pre-existing).

Per [[feedback-spec-citation-in-commits]] +
[[feedback-spec-floor-skepticism]] (the "HW +76 kWh uniform overcount"
across 17 variants traced to TWO spec-citable defaults the cascade
was getting wrong, not a precision floor).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 19:03:58 +00:00
Khalim Conn-Kowlessar
c4db37db19 Slice S0380.139: route _is_off_peak_meter through tariff_from_meter_type canonical dispatch (bare '18 Hour' lodging)
Pre-slice `_is_off_peak_meter` carried its own string-dispatch that
only recognised the RdSAP 10 long form `"off-peak 18 hour"`. The bare
`"18 Hour"` lodging (Elmhurst Summary §14.2 surface form, lodged by
41/41 corpus variants) fell into the catch-all `return False` branch.
That mis-classified every 18-hour cert as non-off-peak for the
secondary / PV cost paths and billed electric secondary heating at
standard 13.19 p/kWh (Table 32 code 30) instead of the 18-hour low
rate 7.41 p/kWh (Table 32 code 40).

The fix routes `_is_off_peak_meter` through `tariff_from_meter_type`
so every lodging form already recognised there (int 1/4/5, `"18 Hour"`,
`"off-peak 18 hour"`, `"Dual"`, `"Dual (24 hour)"`, numeric strings)
is consistently classified. Single (code 2) stays standard; Unknown
(code 3) retains the heuristic "electric end-uses on Unknown meters
typically come from E7-eligible dwellings whose tariff the assessor
couldn't pin down — apply off-peak". Per
[[feedback-zero-error-strict]] the now-dead `_RDSAP_DEFINITELY_OFF_PEAK`
frozenset is deleted (canonical dispatch covers the same codes).

Spec citation per [[feedback-spec-citation-in-commits]]:

> RdSAP 10 §17 page 85 row 10-2 (Electricity meter): "Dual / single /
>  10-hour / 18-hour / 24-hour / unknown"
> RdSAP 10 §12 page 62: "if the meter is dual 18-hour/24-hour it is
>  18-hour/24-hour tariff"

Corpus impact (6 storage-heater / underfloor variants on forced
secondary):

| variant | SAP code | old ΔSAP | new ΔSAP |
|---|---:|---:|---:|
| electric 3 | 401 | -0.10 | +2.42 |
| electric 5 | 402 | -2.48 | -0.06 |
| electric 6 | 404 | -1.14 | +1.19 |
| electric 7 | 408 | -1.08 | +1.14 |
| electric 8 | 409 | -2.54 | -0.41 |
| electric 9 | 421 | -2.76 | -0.24 |

Total absolute SAP residual across the cluster: 10.10 → 5.46.

The 3 sign-flipped variants (electric 3/6/7) surface a separate
cascade bug: `_secondary_heating_fraction_for_category` defaults to
0.10 when the mapper leaves `main_heating_category=None` for electric
storage, but the worksheet for codes 401/402 uses 0.15 = Table 11
Cat 7. Mapper-side fix queued.

Tests:
- new AAA test `test_is_off_peak_meter_recognises_bare_18_hour_lodging`
  covers 7 lodging forms (bare, lowercase, long-form, Single, standard,
  Unknown+electric, Unknown+non-electric)
- 6 corpus pins re-tightened (electric 3/5/6/7/8/9)

Extended handover suite: 882 pass (was 881; +1 new test), 0 fail.
Pyright net-zero on touched files (43 → 43 errors, all pre-existing).

Per [[reference-unmapped-sap-code]] strict-dispatch routing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 18:39:43 +00:00
Khalim Conn-Kowlessar
a830e85565 Slice S0380.138: route every off-peak callsite through the per-tariff Table 32 low-rate (electric +5..+9 SAP cluster + spillover)
Pre-slice every off-peak callsite in `cert_to_inputs.py` —
`_space_heating_fuel_cost_gbp_per_kwh`, `_hot_water_fuel_cost_gbp_per_kwh`,
`_secondary_fuel_cost_gbp_per_kwh`, `_pv_dwelling_import_price_gbp_per_kwh` —
hardcoded `prices.e7_low_rate_p_per_kwh = 5.50` p/kWh (Table 32 code 31,
the 7-hour low rate) regardless of the cert's actual tariff. Every
18-hour cert was thereby under-charged 1.91 p/kWh × off-peak kWh on
its space-heating, hot-water, and secondary-heating cost rows.

Per RdSAP 10 §19 Table 32 (p.95):

> "Electricity ... 7-hour tariff (low rate / off-peak) — code 31 5.50 p/kWh
>  ... 10-hour tariff (low rate) — code 33 7.50 p/kWh
>  ... 18-hour tariff (low rate) — code 40 7.41 p/kWh
>  ... 24-hour tariff — code 35 6.61 p/kWh"

The fix routes through a new `_off_peak_low_rate_gbp_per_kwh(tariff)`
helper that reads the existing per-tariff Table 32 lookup
(`_TARIFF_HIGH_LOW_RATES_P_PER_KWH`). A companion
`_off_peak_low_rate_gbp_per_kwh_via_meter_heuristic(meter_type)` covers
the secondary / PV paths that detect off-peak via the
`_is_off_peak_meter` heuristic (RdSAP meter code 3 = Unknown is treated
as off-peak for electric end-uses), falling back to the SEVEN_HOUR rate
when the meter resolves to STANDARD — codifying the heuristic that the
literal 5.50 constant used to embed.

Per [[feedback-zero-error-strict]] the now-dead
`PriceTable.e7_low_rate_p_per_kwh` field is deleted (no fallback can
silently re-introduce the 5.50 hardcode); the field's docstring +
RDSAP_10_TABLE_32_PRICES instantiation update to point at the new
helpers.

Corpus closure (all 18-hour cohort):

- 8 electric variants — SAP +5.85..+9.64 → -0.10..-2.76; cost
  -£135..-£222 → +£2..+£64
- ashp +5.67 → +0.24 SAP (-£131 → -£5.57)
- gshp +5.16 → +1.15 SAP (-£119 → -£26)
- solid fuel 4..11 — SAP +1.59..+2.04 → ±0.45 (cost ±£10)

Golden 0240 PV path also closes (was raising UnmappedSapCode on
Unknown-meter probe — surfaced an unreachable PV literal that the
meter-heuristic helper now resolves).

Tests:
- new AAA test `test_space_heating_off_peak_fallback_uses_actual_tariff_low_rate_not_e7`
  exercising the EIGHTEEN_HOUR fallback at the helper level
- 19 corpus pins re-tightened (8 electric + ashp + gshp + 8 solid-fuel
  + golden 0240's implicit pin)

Extended handover suite: 881 pass (was 880; +1 new test), 0 fail.
Pyright net-zero on touched files (43 → 43 errors, all pre-existing).

Per [[feedback-spec-citation-in-commits]] +
[[feedback-worksheet-not-api-reference]] +
[[reference-unmapped-sap-code]].

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 18:22:54 +00:00
Khalim Conn-Kowlessar
3be8b8877b docs: handover + next-agent prompt post S0380.131..137
Captures seven slices: heating-oil price flip (S0380.131),
MissingMainFuelType strict-raise (S0380.132), Elmhurst EES → fuel
dispatch (S0380.133), PE pin block-mismatch fix (S0380.134), Table 4a
R-dispatch solid fuel (S0380.135), dual-fuel cost-cascade fix
(S0380.136), Table 4a R-dispatch electric (S0380.137).

Suite: 880 pass / 0 fail at HEAD 3542186f.

Next slice candidate: the +5..+9 SAP cluster across all 7 cascade-OK
electric corpus variants — uniform −£135..−£222 cost under-count
suggests one shared Table 12a tariff-handling gap.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 17:12:10 +00:00
Khalim Conn-Kowlessar
3542186f18 Slice S0380.137: extend Table 4a R-dispatch to electric storage / direct-acting / underfloor / ceiling (cluster)
Continuation of S0380.135's Table 4a per-heating-system responsiveness
dispatch (`_RESPONSIVENESS_BY_SAP_CODE` in cert_to_inputs.py). The
solid-fuel coverage closed 10 corpus variants; this slice extends the
dispatch to the electric heating SAP code ranges from SAP 10.2 Table
4a (PDF p.170):

  401  Old (large volume) storage heaters             R=0.00
  402  Slimline storage heaters                       R=0.20
  403  Convector storage heaters                      R=0.20
  404  Fan storage heaters                            R=0.40
  405  Slimline storage heaters + Celect-type ctrl    R=0.40
  407  Fan storage heaters + Celect-type ctrl         R=0.60
  408  Integrated storage+direct-acting heater        R=0.60
  409  High heat retention storage heaters (§9.2.8)   R=0.80
  421  In concrete slab (off-peak only)               R=0.00
  422  Integrated (storage+direct-acting)             R=0.25
  423  Integrated with low off-peak                   R=0.50
  424  In screed above insulation                     R=0.75
  425  In timber floor / immediately below covering   R=1.00
  515  Electricaire system                            R=0.75
  691  Panel, convector or radiant heaters            R=1.00
  694  Water- or oil-filled radiators                 R=1.00
  701  Electric ceiling heating                       R=0.75

A few electric storage codes (402, 403, 405, 407) carry a *different*
R value in the 24-hour tariff section of Table 4a vs the off-peak
section (e.g. Slimline 402 = R=0.20 off-peak / R=0.40 24-hour). This
dict captures the off-peak value as the default because the 24-hour
tariff is rare in the corpus (no variant lodges it). If a 24-hour-
tariff cert surfaces with one of these codes the dispatch needs to be
promoted to a (sap_code, tariff) lookup; until then the off-peak
default applies.

Heating-systems corpus impact — 6 electric corpus variants re-pinned:

  variant       SAP  R    ΔSAP   was       ΔPE      was
  electric 3    401  0.00 +9.43  +14.70   -1059   -3189
  electric 5    402  0.20 +6.76  +10.97     -96   -1798
  electric 6    404  0.40 +7.82  +10.97    -494   -1770
  electric 7    408  0.60 +7.58   +9.68    -428   -1277
  electric 8    409  0.80 +5.84   +6.89    +200    -224
  electric 9    421  0.00 +6.77  +12.03    +154   -1976

3/6 PE residuals close to ±200 kWh (electric 5/8/9). The remaining
+5..+9 SAP residuals across all electric variants suggest a separate
shared cascade gap (likely Table 12a high/low-rate fraction or pumps/
fans electric handling — fuel cost is consistently under-counted by
~£100-£220 across the cluster). Queued for follow-up.

electric 1 (SAP 191 Direct acting electric boiler) and electric 2
(SAP 524 Air source heat pump) unchanged — both have spec R=1.0
already (matched the Table 4d emitter fallback).

Extended handover suite: 880 pass / 0 fail (+1 new AAA test
covering the 17 electric R-dispatch entries).

Pyright net-zero on touched files (43 → 43).

No golden fixture impact — no golden cert lodges a covered electric
SAP code via the cascade path that would shift residuals.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 17:03:46 +00:00
Khalim Conn-Kowlessar
4d004790db Slice S0380.136: route _is_electric_main / _is_electric_water via the canonical T32-first normaliser (dual-fuel closure)
`_is_electric_main` and `_is_electric_water` hand-rolled a literal set
check `code in {10, 25, 29}` ∪ `{30..40}` to classify a fuel code as
electricity. The set conflated two enums:

  - {10, 25, 29}    — API enum codes (epc_codes.csv row main_fuel):
                        10 = electricity (backwards compat)
                        25 = electricity (community)
                        29 = electricity (not community)
  - {30, 31, ..., 40} — Table 32 codes (RdSAP 10 spec p.95):
                          30 = standard tariff
                          31/32 = 7-hour low/high
                          33/34 = 10-hour low/high
                          35 = 24-hour heating
                          38/40 = 18-hour high/low

API enum codes 1-29 collide with Table 32 codes 1-29 for unrelated
fuels — API 10 = "electricity" vs Table 32 10 = "dual fuel (mineral +
wood)". S0380.135's EES dispatch sets `main_fuel_type` to Table 32
codes (BDI → 10 for dual fuel), so a dual-fuel main was silently
mis-classified as electric. The `_space_heating_fuel_cost_gbp_per_kwh`
tariff branch then re-routed solid fuel 6's space heating cost through
the 18-hour-low electric rate (5.50 p/kWh) instead of dual-fuel 3.99
p/kWh — solid fuel 6 SAP residual −7.38 → −11.37 in S0380.135.

The fix promotes the existing `table_32._is_electric_code` to public
`is_electric_fuel_code` and routes both `_is_electric_main` and
`_is_electric_water` through it. The canonical helper normalises a
fuel code via T32-first then API-translate fallback (same convention
as `unit_price_p_per_kwh`), so a Table-32-code-10 dual-fuel main
classifies as non-electric correctly.

Subtle behaviour change: API enum code 25 ("electricity (community)")
maps via API_FUEL_TO_TABLE_32 to Table 32 code 41 ("heat from electric
heat pump (community)") which is a heat network billed at the heat-
network rate (4.24 p/kWh single rate), not at the off-peak electric
tariff. Pre-S0380.136 the literal-set check would have treated this
as direct electric and applied the Table 12a high/low-rate split —
that was wrong; community heat networks don't have an off-peak split.
The new canonical helper correctly excludes code 41 from
_ELECTRIC_FUEL_CODES.

Heating-systems corpus impact:

  solid fuel 6 (Dual Fuel Anthracite Wood, SAP 160):
    ΔSAP  −11.3731 → +1.9493   (now in cluster with other solid-fuel)
    Δcost +£268.44 → −£44.91
    ΔPE   unchanged (PE wasn't affected by the cost mis-routing)

No other corpus variants moved — none have `main_fuel_type` in the
ambiguous API/T32 collision range that was previously mis-classified.

Extended handover suite: 879 pass / 0 fail (+2 from new AAA tests
covering both `_is_electric_main` and `_is_electric_water` dual-fuel
non-electric classification + API code 29 → electric / API code 25 →
heat-network non-electric semantics).

Pyright net-zero on touched files (43 → 43).

No golden fixture impact — no golden cert lodges `main_fuel_type=10`
(dual fuel) on the cascade path.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 13:37:14 +00:00
Khalim Conn-Kowlessar
829a3318dc Slice S0380.135: dispatch responsiveness via Table 4a SAP code (solid-fuel cluster)
SAP 10.2 spec line 15271:

  "R = responsiveness of main heating system (Table 4a or Table 4d)"

The cascade's `_responsiveness` was keyed solely on `heat_emitter_type`
(Table 4d), which is correct for systems whose responsiveness is
determined by the emitter (gas / oil / HP boilers feeding radiators or
UFH). But for systems with intrinsically low responsiveness — solid-
fuel room heaters, range cookers, independent solid-fuel boilers —
the spec lodges R directly in Table 4a against the heating-system SAP
code, and that value overrides any emitter-based lookup.

For solid fuel 8 (SAP code 160 = "Range cooker boiler (integral oven
and boiler)", lodged with radiators emitter), pre-slice the cascade
returned R = 1.0 (radiators) instead of the spec-correct R = 0.50
(Table 4a p.169). The Table 9b mean-internal-temperature adjustment
then over-estimated heating-system response, under-estimating space
heating demand by ~10% (cascade demand 6874.80 kWh vs worksheet EPC
implied 7566 kWh).

The fix adds a new dispatch `_RESPONSIVENESS_BY_SAP_CODE` consulted
first in `_responsiveness`; SAP codes not in the dict fall through to
the existing Table 4d emitter lookup.

Table 4a entries added (SAP 10.2 PDF p.169-170):

  151  Manual feed independent boiler                R=0.75
  153  Auto (gravity) feed independent boiler        R=0.75
  155  Wood chip/pellet independent boiler           R=0.75
  156  Open fire with back boiler to radiators       R=0.50
  158  Closed room heater with boiler to radiators   R=0.50
  159  Stove (pellet-fired) with boiler to radiators R=0.75
  160  Range cooker boiler (integral oven+boiler)    R=0.50
  161  Range cooker boiler (independent oven+boiler) R=0.50
  631  Open fire in grate                            R=0.50
  632  Open fire with back boiler (no radiators)     R=0.50
  633  Closed room heater                            R=0.50
  634  Closed room heater with boiler (no radiators) R=0.50
  635  Stove (pellet fired)                          R=0.75
  636  Stove (pellet fired) with boiler (no rads)    R=0.75

Heating-systems corpus impact — 10 solid-fuel variants re-pinned:

  variant         ΔSAP   was        Δcost  was      ΔPE     was
  solid fuel 2    +2.64  +4.79     -£60    -£110    -1211   -2292
  solid fuel 3    +1.32  +4.43     -£30    -£102     -935   -2496
  solid fuel 4    +1.59  +4.13     -£37     -£95     +151   -1097
  solid fuel 5    +1.70  +2.71     -£39     -£62     +160    -331
  solid fuel 6   -11.37  -7.38    +£268   +£168      +87   -1313  ← see below
  solid fuel 7    +2.04  +5.82     -£47    -£131      +44   -1638
  solid fuel 8    +1.81  +4.24     -£42     -£98      +88   -1308
  solid fuel 9    +1.71  +3.44     -£39     -£79     +155    -510
  solid fuel 10   +1.75  +5.14     -£40    -£118     +120   -1315
  solid fuel 11   +1.62  +4.35     -£37    -£100     +171    -962

7/10 PE residuals close to ±220 kWh (down from -331..-2496). 9/10 SAP
residuals tighten to +1.32..+2.64 (down from +2.71..+5.82).

solid fuel 6 (Dual Fuel Anthracite Wood, SAP 160) SAP residual
regresses -7.38 → -11.37 while PE closes +87. The dual-fuel cascade
has a separate bug now exposed by the more-accurate demand calc;
queued for a follow-up slice.

Non-solid-fuel variants (15) unchanged — their SAP codes aren't in
the new dispatch dict so they fall through to Table 4d as before.
Electric storage Table 4a rows (193-196, 422-424, 515, 701) and the
spec's other low-responsiveness codes can be added in follow-up
slices as electric corpus variants are unblocked.

Extended handover suite: 877 pass / 0 fail (+1 new responsiveness
AAA test). Pyright net-zero on touched files (43 → 43).

No golden fixture impact — no golden cert lodges a solid-fuel SAP
code via the cascade path.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 13:11:36 +00:00
Khalim Conn-Kowlessar
0aa40b63cd Slice S0380.132: strict-raise MissingMainFuelType on empty main_fuel_type
The cascade's `_main_fuel_code` previously returned None when
`MainHeatingDetail.main_fuel_type` was anything other than an int
(empty string, None, or an unmapped string label). The downstream
`table_32.unit_price_p_per_kwh(None)` then silently defaulted to mains
gas (3.48 p/kWh / CO2 0.21 kg/kWh / η 0.45 / PE 1.22) — a misleading
fallback where cost may happen to be close but CO2 / PE / efficiency
are completely wrong for the actual heating system.

Probe of the heating-systems corpus surfaced 26 of 41 controlled-
variable variants with `main_fuel_type=''`:

  Community heating 1/2/3/4/6 (Table 4a 301-304)        5
  Electric 11/12/13/14 (Table 4a 5xx/6xx/7xx)           4
  No system (SAP code 699)                              1
  Oil 2 (HVO) / oil 3 (FAME) / oil 4 (FAME) /
    oil 5 (bioethanol) / oil 6 (B30K) (Table 4b)        5
  Solid fuel 2..11 (Table 4a 150-160 + 600-636)        10
  pcdb 3 (lodges 'Bulk LPG' string — mapper dict gap)   1

Each pre-slice carried a residual pin in `_EXPECTATIONS` encoding the
broken mains-gas-default state. Solid fuel 8's +0.87 ΔSAP — the
"smallest open residual" the user asked to investigate next — turned
out to be the net of compensating cost/efficiency errors; the CO2
delta was +3525 kg/yr and PE +4103 kWh/yr because the cascade was
costing wood chips as mains gas.

Two changes land together:

1. Add `MissingMainFuelType(ValueError)` to
   `domain/sap10_calculator/exceptions.py`. Semantics distinct from
   the sibling `UnmappedSapCode` (which is for unmapped int dispatch
   codes; this is for "value not resolvable to a SAP fuel code at
   all"). The error message names the lodged value + the
   `sap_main_heating_code` hint so the upstream mapper fix is
   obvious.

2. `_main_fuel_code` in `cert_to_inputs.py` now raises
   `MissingMainFuelType` when `main_fuel_type` is not an int.
   `main is None` still returns None (genuinely no main heating).

The 26 blocked corpus variants are lifted out of the
`_EXPECTATIONS` residual-pin grid into a new tuple
`_BLOCKED_BY_MISSING_MAIN_FUEL_TYPE` driving a new parametrised test
`test_heating_systems_corpus_blocked_variant_raises_missing_main_fuel_type`
that asserts the raise for each blocked variant. As mapper-side fixes
land (deriving fuel from `sap_main_heating_code` via SAP 10.2 Table
4a/4b/4f, or extending `_ELMHURST_MAIN_FUEL_TO_SAP10`), variants move
back onto the residual-pin grid.

Mirrors the [[reference-unmapped-sap-code]] / [[reference-unmapped-
api-code]] strict-raise pattern: forcing function for spec/mapper
completion at the cascade boundary instead of silently producing
wrong outputs.

Extended handover suite at HEAD post-slice: 875 pass / 0 fail (was
874; +1 from the new `_main_fuel_code` strict-raise unit test;
26 blocked corpus pins replaced 1:1 by 26 assert-on-raise tests).

Pyright net-zero (43 → 43 — all pre-existing `pytest.approx` flags).

No golden fixture impact — every golden cert carries an int
`main_fuel_type`.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 09:43:27 +00:00
Khalim Conn-Kowlessar
14eee259b4 Slice S0380.131: flip Table 32 heating-oil price 7.64 → 5.44 (empirical)
The published RdSAP 10 Specification 10-06-2025 PDF Table 32 (p.95)
lists heating oil at 7.64 p/kWh. Two independent operational sources
both use 5.44 p/kWh for the same fuel:

  - Elmhurst P960 worksheets across all five oil-fired variants in
    `sap worksheets/heating systems examples/` (oil 1, oil pcdb 1/2/3,
    pcdb 1) lodge 5.4400 p/kWh on (240) "Space heating - main system 1"
    and (247) "Water heating (other fuel)" for every "FuelType: Heating
    oil" worksheet.
  - The gov.uk EPC register's lodging software back-solves to ~5.48
    p/kWh from cert 0240-0200-5706-2365-8010's lodged SAP 73 (oil + PV
    detached, age J). With heating-oil at 5.44 in the cascade this cert
    closes to ΔSAP = 0 exactly against its lodged value.

The BRE technical papers (`docs/specs/sap10 technical papers/`) carry
no Table 32 errata or fuel-price update, so the change is grounded in
empirical cross-source evidence rather than a spec citation — the
worksheet PDF is the source of truth per the project convention.

Post-flip residuals:

  Heating-systems corpus (cascade − worksheet ΔSAP_c):
    oil 1        −9.7030 → +2.6578
    oil pcdb 1  −11.6343 → +0.4239  ← within 1 SAP of closure
    oil pcdb 2  −11.6343 → +0.4239
    oil pcdb 3  −10.8674 → +1.1597
    pcdb 1       −9.4083 → +6.9521  ← largest remaining oil-cohort gap

  Golden fixtures (cascade − lodged SAP):
    0240-0200-5706-2365-8010  resid −10 → +0  ← EXACT closure
    0390-2954-3640-2196-4175  resid  −6 → +7  ← oil-price bug was
                                                 masking +13 SAP of
                                                 opposite-direction
                                                 cascade gaps; now
                                                 exposed for follow-up

PE / CO2 residuals are unaffected by the unit-price flip (cost-only
change). The 41-variant corpus regression guard (S0380.129) holds; all
other golden cohorts pass unchanged. Extended handover suite: 874 pass.

Bio-FAME (code 73) shows the inverse divergence on oil 3/4 worksheets
(worksheet 7.64 vs spec 5.44 — possible row-swap typo in the spec PDF)
but flipping it has no measurable cascade effect today, so deferred
until a cert that exercises it surfaces.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 09:21:29 +00:00
Khalim Conn-Kowlessar
38e6d18a13 docs: handover + next-agent prompt post S0380.125..130
Captures the heating-systems corpus closure work, the new permanent
residual-pin regression test, and the queued S0380.131 candidate
(heating-oil unit price spec-vs-worksheet divergence).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-31 09:05:24 +00:00
Khalim Conn-Kowlessar
d8cdee4e53 Slice S0380.125: map Elmhurst Summary "18 Hour" meter_type to EIGHTEEN_HOUR
The Elmhurst Summary §14.2 Meters section lodges the electricity meter
type as the bare RdSAP enum form "18 Hour", but `_METER_STR_TO_INT`
only carried the legacy "off-peak 18 hour" alias. All 41 P960-format
heating-system fixtures at `sap worksheets/heating systems examples/`
lodge meter_type "18 Hour", so `cert_to_inputs` strict-raised on every
one of them before this slice.

Per RdSAP 10 Specification §17 page 85 (Electricity meter row 10-2):

  > "Electricity meter: Dual/single/10-hour/18-hour/24-hour/unknown"

Per RdSAP 10 §12 page 62:

  > "if the meter is dual 18-hour/24-hour it is 18-hour/24-hour tariff"

So the bare "18 Hour" lodging routes directly to enum 5 (Off-peak 18
hour) → `Tariff.EIGHTEEN_HOUR`, bypassing the §12 Rules 1-4 dispatch
(which only fires for Dual meters that aren't 18-hour or 24-hour).

After this slice the heating-system corpus probe (`/tmp/probe_*.py`
across 41 variants of the same property × different heating systems)
shifts from "32 raises + 7 mapper gaps + 2 emitter gaps" to
"32 cascade-OK + 7 community-heating + 2 underfloor-emitter + 1
cylinder-size 'No Access'". The 32 newly-OK variants surface a
positive ΔSAP cluster (cascade SAP_c > worksheet SAP_c by +0.87..+30
across boiler types) — that residual layer is queued for the next
slice.

Extended handover suite at HEAD post-slice: **829 pass, 0 fail**
(baseline 775 + test_table_12a.py's 54 incl. the new "18 Hour" entry).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 23:51:47 +00:00
Khalim Conn-Kowlessar
8904ec090b docs: handover + next-agent prompt post S0380.115..124
10 spec-cited slices closed this session:
  .115 — fixture ECF pin typo
  .116 — RdSAP 10 §15 A_RR_shell rounding (cert 000565 truly exact)
  .117 — re-pin golden PE residuals for 0240 + 6035
  .118 — cohort LINE_xx pins → 1e-4 + §15-aware RR test expecteds
  .119 — §5 test EPC builder propagates sap_roof_windows
  .120 — RdSAP 10 §5.11.4 NI vs explicit-0 roof discriminator
  .121 — floor_construction code 4 → "Solid" (basement cert 0712)
  .122 — tighten test_ventilation tolerances
  .123 — pin Table U5 share-column solar fluxes at exact equality
  .124 — tighten dimensions + rating arithmetic pins

Extended handover suite at HEAD `1e69bd39`: 775 pass, 0 fail.

Handover documents:
- HANDOVER_POST_S0380_124.md — full state + cert 0240 hypothesis ranking
- NEXT_AGENT_PROMPT_POST_S0380_124.md — two-task brief (0240 cost-cascade
  diagnosis + golden-corpus audit awaiting user's same-property
  heating-variant Elmhurst fixtures).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 22:15:22 +00:00
Khalim Conn-Kowlessar
1e69bd3979 Slice S0380.124: tighten dimensions + rating arithmetic pins
`test_dimensions.py`:
- gross_wall_area_m2 synthetic test (40×2.5+16×2.4 = 138.4): abs=0.05 → 1e-12 (exact arithmetic).
- Cohort cert LINE_4 TFA / LINE_5 volume pins: abs=0.01/0.05 → 1e-4 (PDF 4-d.p. display floor; actual cohort diff is 1e-14).

`test_rating.py`:
- `test_net_energy_exporter` SAP=100−13.95×(−0.3)=104.185 exact arithmetic — abs=0.05 → 1e-12.

Tests: 29 pass for the two files; 775 pass on extended suite.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 21:48:29 +00:00
Khalim Conn-Kowlessar
49f87160c7 Slice S0380.123: pin Table U5 share-column solar fluxes at exact equality
`test_ne_and_nw_share_table_u5_constants` asserts NE == NW, E == W,
SE == SW orientation-pairs share the same flux value per Appendix U
Table U5's column-sharing convention. The cascade looks up both via
the same dictionary key — the values are bit-identical, not
approximately equal. Tightened from `pytest.approx(..., abs=0.01)` to
exact `==` equality; abs=0.01 masked the fact that the cascade
returns the same float object.

Net pyright: unchanged.
Tests: 17 pass.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 21:46:22 +00:00
Khalim Conn-Kowlessar
9f0dd64570 Slice S0380.122: tighten test_ventilation tolerances
17 hand-crafted ventilation tests had abs=0.001-0.01 tolerances that
masked the actual diff (always 0 or 1e-16 for these direct-arithmetic
formulas). Tightened to abs=1e-12 (essentially exact).

10 cohort cert pins (`LINE_8`/`LINE_10`/.../`LINE_25` against U985 PDF)
had mixed abs=0.0001-0.0005; standardised to abs=1e-4 (PDF 4-d.p.
display floor per [[feedback-e2e-validation-philosophy]]). The looser
0.0005 pins on (8), (16), (18), (21), (22b), (25) admitted up to half
a 4-d.p. unit of drift that the cascade isn't producing — actual
cascade diffs are ~5e-5 (one notch under display precision).

Test movement: all 26 tests pass at the new tolerances. Net pyright
change: 69 → 69.

Per [[feedback-zero-error-strict]] tolerance widening is forbidden;
this slice goes the other way — every pin tightened to its actual
precision floor.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 21:44:43 +00:00
Khalim Conn-Kowlessar
76717dfc3a feat(baseline): BaselineOrchestrator + BaselinePerformance aggregate (#1135)
Stage 2 of First Run. Establishes each Property's Baseline Performance
from persisted source data and writes it back — reads only from repos,
never a Fetcher or HTTP (ADR-0003), so it is byte-identical whether
Ingestion ran milliseconds ago or last week.

Domain (`domain/baseline/`):
- `Performance` VO — the four rated quantities: SAP / EPC Band / CO2 /
  Primary Energy Intensity. `lodged_performance(epc)` reads them off the
  EPC's recorded fields (PEUI = `energy_consumption_current`).
- `BaselinePerformance` (ADR-0004) — the paired `lodged` + `effective`
  Performance + `rebaseline_reason`, plus the no-derivation part of the
  energy block (`space_heating_kwh` / `water_heating_kwh`, off the RHI,
  deterministic per ADR-0006). Both halves always populated.
- `Rebaseliner` port + `StubRebaseliner`: the re-score-on-override seam
  (ADR-0011). SAP10 certs pass through (effective == lodged, reason
  "none"); a pre-SAP10 cert raises `RebaselineNotImplemented` rather
  than fabricating a plausible-but-wrong "none" — ML rebaselining is not
  wired yet. Mirrors the repo's strict-raise culture.

Persistence: new `BaselineRepository` port + `BaselinePostgresRepository`
+ flat-column `baseline_performance` SQLModel (one row per Property). Per
ADR-0004's amendment this is a standalone table, NOT columns on the
retiring `property_details_epc`. Production migration is FE-owned
(Drizzle) — docs/migrations/baseline-performance-table.md.

Docs (grill-with-docs): corrected CONTEXT.md Lodged/Effective Performance
to Primary Energy Intensity (the term collided with its own _Avoid_ entry
under "heat demand") + fixed stale RHI field names; amended ADR-0004
Consequences for the standalone-table decision.

Fuel split + bills (rest of EPC Energy Derivation) deferred to a
follow-up — they need a Fuel Rates source (Ofgem-cap ETL) that does not
exist yet.

TDD, one test -> one impl: 7 tests (lodged read, rebaseliner pass-through
+ raise, orchestrator establish-and-persist + pre-SAP10 raise, Postgres
round-trip + absent). pyright strict clean; AAA layout.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 21:21:34 +00:00
Khalim Conn-Kowlessar
f0305d5452 Slice S0380.120: distinguish NI from explicit int(0) roof_insulation_thickness per RdSAP 10 §5.11.4
RdSAP 10 §5.11.4 (PDF p.44):

  "If retrofit insulation present of unknown thickness use 50 mm."

The cascade encoded "unknown thickness" via the cert's "NI" (Not-
Indicated) sentinel which `_parse_thickness_mm` collapses to int(0).
But that conflates two structurally different signals:

  (a) explicit int(0) — `_api_resolve_sloping_ceiling_thickness`
      returns this for cert 001479 Ext2 PS sloping ceiling age C, a
      per-BP "uninsulated" override of the dwelling-level description
      ("Pitched, insulated" from another BP).
  (b) string "NI" — the cert lodgement marker for "thickness not
      indicated; defer to description"; §5.11.4 should fire when the
      description carries an "insulated" signal.

Pre-slice the heat_transmission cascade dropped `roof_description`
whenever `roof_thickness == 0`, killing the §5.11.4 path in `u_roof`
(line 711) for the (b) case. 346 corpus certs lodge the NI +
"insulated (assumed)" pattern per the §5.11.4 test's arrange comment.

Fix: inspect the raw `part.roof_insulation_thickness` value (pre-
parse) — drop the description only when the lodgement is the literal
int(0), keep it for the "NI" string sentinel so `u_roof`'s §5.11.4
branch fires (`_described_as_insulated` + thickness=0 → return 0.68).

Test movement:
  test_roof_insulated_assumed_with_ni_thickness_uses_50mm_per_section_5_11_4 → PASS
  test_summary_001479_full_chain_sap_matches_worksheet_pdf_exactly → PASS (cohort safe)
  cert 000565 e2e — 11/11 PASS (unaffected — explicit per-BP thicknesses)

Golden corpus impact: cert 0240 had this exact pattern (BP[1] NI + global
description includes "Pitched, insulated (assumed)"). The fix drops its
roof U from 2.30 → 0.68 for that BP, closing massive mapper-gap residuals:

  expected_sap_resid:                 -14    → -10     (Δ +4 SAP)
  expected_pe_resid_kwh_per_m2:    +12.49   → +0.054   (Δ −12.43 kWh/m²)
  expected_co2_resid_tonnes_per_yr:  +0.696 → +0.063   (Δ −0.633 t/yr)

Re-pinned per [[feedback-golden-residuals-near-zero]]: "Re-pin to the
new (smaller) value when a gap closes". The remaining 0240 residuals
(SAP -10 / PE +0.05 / CO2 +0.06) are tiny — the bulk of 0240's mapper
gap is now closed.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 21:10:00 +00:00
Khalim Conn-Kowlessar
a77f1a284d Slice S0380.119: propagate sap_roof_windows in _build_section_5_epc
The §5 test EPC builder threaded sap_windows from the fixture but
discarded `sap_roof_windows` — passing them through `make_minimal_sap10
_epc(...)`. Pre-S0380.110 the `_daylight_factor_from_cert` cascade
read a single aggregate `rooflight_total_area_m2` kwarg + bulk g_L,
so the test EPC builder's omission was masked. Post-S0380.110 the
cascade reads per-rooflight glazing via `epc.sap_roof_windows`
(Appendix L §L2a per-window g_L sum) — Triple / Double / Single
distinctions matter.

For cohort 000516 (the only cohort fixture with a lodged rooflight,
a Double-glazed 1.18 m² × g_L=0.80 × FF=0.70 × Z_L=1.0), the empty
sap_roof_windows on the test EPC undercut the daylight factor →
cascade lighting (67) Jan 33.78 W vs ws 32.68 W (+1.1 W/month) →
lighting_kwh_per_yr 238.65 vs ws 230.88 (+7.77 kWh/yr).

Fix: thread `fixture.build_epc().sap_roof_windows` through the
minimal EPC. Cohorts 000474/477/480/487/490 have no rooflights →
list is None → cascade unchanged for those certs.

Test movement: 000516 (67) Jan 33.78 → 32.68 ✓ EXACT. 000516
lighting_kwh_per_yr 238.65 → 230.88 ✓ EXACT.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 20:53:33 +00:00
Khalim Conn-Kowlessar
55a29f5a1c Slice S0380.118: cohort LINE_xx pins → abs=1e-4 + §15-rounded RR test expecteds
Two changes bundled (same file, same RdSAP 10 §15 spec citation):

1. Tighten cohort cert (000474 / 000490) heat_transmission LINE_xx
   pins from abs=0.01 / 0.1 → abs=1e-4 (4 pins). Pre-slice the cohort
   landed at 1e-4 of the U985 PDF but the test pins were holdovers
   from when the cascade was less precise. Per [[feedback-e2e-
   validation-philosophy]]:

     "per-component tests pin against U985 worksheet line refs at
      <1e-3 tolerance ... 1e-4 since PDF lodges 4 d.p."

   Probe data at HEAD post-§15:
     000474 LINE_33  cascade=209.108439 ws=209.1084 Δ=+4e-5
     000474 LINE_37  cascade=232.116939 ws=232.1169 Δ=+4e-5
     000490 LINE_33  cascade=211.893610 ws=211.8936 Δ=+1e-5
     000490 LINE_37  cascade=236.621110 ws=236.6211 Δ=+1e-5

2. Update `test_room_in_roof_simplified_type_1` and `..._type_2`
   expected-value formulas to round A_RR_shell to 2 d.p. per RdSAP
   10 §15 (p.66) — matching the cascade behaviour now enforced by
   Slice S0380.116. The unrounded expected was 100.9156 / 71.857;
   spec-correct rounded is 100.919 (39.5285 → 39.53) and 71.846
   (32.2749 → 32.27). Same abs=1e-4 pin enforces both arithmetic
   and rounding correctness.

   New import: `_round_half_up` from heat_transmission (the same
   helper the cascade uses for §15 rounding).

Net pyright change: 71 → 71. Net test change: 4 newly-tight pins,
2 newly-passing RR synthetic tests, 670 → 670 passing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 20:39:36 +00:00
Khalim Conn-Kowlessar
854b888465 Slice S0380.117: re-pin golden PE residuals for 0240 + 6035 (track §15)
Slice S0380.116 rounded `A_RR_shell = 12.5 × √(A_RR_floor / 1.5)` to
2 d.p. per RdSAP 10 §15 (p.66). Two certs in the golden corpus have
RR-driven cascade paths that fire this rounding:

  0240 (TFA 118, age J, RR on BP[0]):    PE +12.4941 → +12.4933
  6035 (TFA 128, age A, RR + gas combi): PE +46.0936 → +46.0952

CO2 deltas on both are sub-1e-4 (display-precision noise) so those
pins stay. All 51 cohort-2 certs are unchanged — their A_RR_shell
paths either bypass the Simplified branch (Detailed RR with
`slope`/`flat_ceiling` roof lodgements) or have no RR.

Per [[feedback-golden-residuals-near-zero]] re-pin to track new
cascade output rather than absorb the drift into the test tolerance.
The ±0.01 PE / ±0.001 CO2 absolute tolerances on the pin stay; what
changes is the expected residual value.

Test still passes at ±0.0000 drift on all 53 certs post-repin.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 20:25:47 +00:00
Khalim Conn-Kowlessar
f2e8b657ce Slice S0380.116: A_RR_shell rounded to 2 d.p. per RdSAP 10 §15 (p.66)
RdSAP 10 Specification §15 "Rounding of data" (PDF p.66):

  "For consistency of application, after expanding the RdSAP data into
   SAP data using the rules in this Appendix, the data are rounded
   before being passed to the SAP calculator. The rounding rules are:
     U-values: 2 d.p.
     All element areas (gross) including window areas and conservatory
     wall area: 2 d.p."

The §3.9.1 / §3.10.1 shell formula A_RR_shell = 12.5 × √(A_RR_floor /
1.5) produces a gross element area for the room-in-roof. Pre-slice the
cascade kept the raw float (e.g. cert 000565 BP[0]: 12.5 × √30 =
68.46532...), then subtracted lodged wall surfaces to obtain the (30)
residual roof area. The worksheet rounds A_RR_shell to 2 d.p. (68.47)
BEFORE the subtraction — per §15 above.

Cert 000565 has three BPs that fire this path (Main, Ext1, Ext3 — all
have detailed wall surfaces with no `slope` / `flat_ceiling` /
`stud_wall` lodgement, so §3.10.1 residual fires). Each contributes a
sub-rounding residual that the unrounded cascade was missing:

  BP[0] Main: 68.4653 → 68.47; residual 43.9653 → 43.97 (+0.0016 W/K)
  BP[1] Ext1: 59.5119 → 59.51; residual 18.2519 → 18.25 (−0.0007 W/K)
  BP[3] Ext3: 57.7350 → 57.74; residual 17.3450 → 17.35 (+0.0017 W/K)

Movement (HEAD `d0268a5b` → this slice) for cert 000565:
  roof_w_per_k        51.3768 → 51.3795 ✓ EXACT (Δ −0.0027 → 0.0)
  thermal_bridging   128.6448 → 128.6460 ✓ EXACT (Δ −0.0012 → 0.0)
  total_external_a   857.6323 → 857.6400 ✓ EXACT (Δ −0.0077 → 0.0)
  space_heating_kwh 59008.2363 → 59008.3499 ✓ EXACT (Δ −0.1136 → 0.0)
  main_fuel_kwh     34710.7272 → 34710.7941 ✓ EXACT (Δ −0.0669 → 0.0)
  total_fuel_cost    4680.2515 → 4680.2593 ✓ EXACT (Δ −0.0078 → 0.0)
  co2_kg_per_yr      6447.6161 → 6447.6263 ✓ EXACT (Δ −0.0102 → 0.0)
  sap_score_cont       28.5087 → 28.5087 ✓ EXACT (Δ +4.2e-5 → −4.7e-5)
  sap_score (int)           29 ✓ EXACT (preserved)
  ecf                  5.38682 → 5.38683 (vs ws 5.3868, Δ +3.2e-5)

Cert 000565 truly closes — every SAP-result field within 1e-4 of the
worksheet PDF.

Cohort safety: 6 cohort certs (000474..000516) unchanged — cohort
000516's roof routes through the Detailed branch with `slope` /
`flat_ceiling` / `stud_wall` lodgements, so `has_roof_lodgement=True`
short-circuits the §3.10.1 residual block. Cohort certs 000474/477/
480/487/490 are pre-S0380.103 hand-built fixtures whose RR fields don't
exercise the simplified A_RR_shell path (rir.floor_area=0 or
detailed_surfaces only).

Test added: `test_summary_000565_a_rr_shell_rounded_2_dp_closes_roof_
w_per_k_per_rdsap_10_section_15` pins the cascade roof_w_per_k = 51.3795
exactly (Δ ≤ 1e-4 vs worksheet (30) Σ).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 20:18:53 +00:00
Khalim Conn-Kowlessar
d0268a5b5c Slice S0380.115: fixture pin ECF 5.3866 → 5.3868 per worksheet (PDF line 593)
The cert 000565 ECF pin was a transcription typo. U985-0001-000565.pdf
line 593 (Block 1, 11a SAP rating individual heating systems) reads:

  Energy cost factor (ECF)  [(255) x (256)] / [(4) + 45.0] =  5.3868 (257)

The pin captured 5.3866 — likely a mis-copy from line 871 / 873 (Nov
MIT (92)m = 15.3866). The cascade output 5.386823 matches the worksheet
PDF at 4 d.p.; the pin was always 0.0002 wrong against the source.

Per [[feedback-verify-handover-claims]], handover narratives are verified
against the source PDF; the cascade is correct and the pin was wrong.

Test movement: `test_sap_result_pin[000565-ecf]` now passes (diff
0.000023 against the corrected pin 5.3868, within abs=1e-4). Four
expected fails remain (cost / CO2 / SH / main_fuel) — closed in the
next slice (A_RR_shell rounding per RdSAP 10 §15).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 20:13:35 +00:00
Khalim Conn-Kowlessar
3998ef586c feat(geospatial): GeospatialRepo — OS Open-UPRN coordinate lookup (#1131)
Add Coordinates value object + GeospatialRepository port + GeospatialS3Repository
adapter. Resolves a Property's lon/lat from the partitioned Ordnance Survey
Open-UPRN parquet (filename_meta -> partition -> UPRN row). A Repo, not a
Fetcher (ADR-0011): no live OS API call. The parquet reader is injected, so it's
unit-tested against fixture parquets with no S3/network; returns None when the
UPRN is uncovered or absent. pyright strict clean.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 19:55:46 +00:00
Khalim Conn-Kowlessar
2fe84fcc7e docs: handover + next-agent prompt post S0380.110..114 (cert 000565 SAP exact at 1e-4)
Five spec-cited slices closed cert 000565 from continuous SAP
Δ = -0.0059 → +0.000042 (within user 1e-4 tolerance):

- S0380.110: per-rooflight g_L via Appendix L §L2a
- S0380.111: roof-window inclination adj via Table 6e Note 2
- S0380.112: per-BP rooflight deduction via RdSAP §3.7
- S0380.113: H=0 gable retention via RdSAP §3.9.2 step (b)
- S0380.114: pump GAIN for HP+boiler via Table 5a Note a)

Handover documents the two parallel workstreams the next agent
should tackle:
1. Final sweep for TRULY exact continuous SAP on cert 000565
   (close the remaining sub-1e-4 cost/CO2/SH/fuel/ECF residuals)
2. Tighten golden test residuals across the corpus per
   [[feedback-golden-residuals-near-zero]]

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 19:53:45 +00:00
Khalim Conn-Kowlessar
cc70e55917 Slice S0380.114: pump gain via Table 5a Note a) (SAP 10.2 p.177)
SAP 10.2 Table 5a (PDF p.177) verbatim:

  "Central heating pump in heated space, 2013 or later: 3 W"

  Note a): "Where there are two main heating systems serving
  different parts of the dwelling, assume each has its own
  circulation pump and therefore include two figures from this
  table. ... Set to zero in summer months. **Not applicable for
  electric heat pumps from database.** Where two main systems serve
  the same space a single pump is assumed."

The Note a) "not applicable for electric heat pumps" rule zeros the
pump GAIN only for HP-category systems themselves. Where a cert
lodges a non-HP main system alongside an HP, the non-HP system's
circulation pump still operates and dissipates 3/7/10 W into the
dwelling as an internal gain.

Pre-slice the cascade conflated TWO different spec rules:

  Table 4f (ELECTRICITY)  — HP pump electricity is in the COP, so
                             worksheet line 230b = 0 for HP certs.
  Table 5a (GAIN)         — HP-from-database pump gain is omitted
                             ONLY for that HP system, not for any
                             non-HP system in the same cert.

`_main_heating_category_from_cert(epc)` returned `details[0].
main_heating_category` and the caller zeroed pump_w whenever that
was category 4. This dropped the 3 W gain for any cert whose first
main system was an HP — even when system 2 was a non-HP boiler with
its own pump.

Cert 000565 lodges TWO main systems:
  [0] HP        (category 4)  pump_age "2013 or later"
  [1] Gas boiler (category 2)  pump_age None

Per spec the system [1] gas boiler's pump contributes 3 W (post-2013
date from [0]'s lodgement). Worksheet (70) confirms:

  Pumps, fans  3.0 3.0 3.0 3.0 3.0 0.0 0.0 0.0 0.0 3.0 3.0 3.0  (70)

Pre-slice cascade returned 0 every month, missing 24 W·months of
winter internal gains. Downstream: +10 kWh space heating, +£0.71
fuel cost, +0.90 kg CO2, -0.008 continuous SAP.

Cert 0380 (cohort-1 ASHP, HP-only):
  [0] HP (category 4)  pump_age unknown
  (no [1])

Worksheet (70) = 0 every month. Cascade post-slice: every main
system is HP → pump_w = 0 ✓ unchanged.

Fix:

`domain/sap10_calculator/worksheet/internal_gains.py`:
- Replace `_main_heating_category_from_cert` + the {4} set-membership
  check with `_all_main_systems_are_heat_pumps(epc)`. Returns True
  iff every lodged `main_heating_details[i].main_heating_category`
  equals 4. Pump gain is zeroed only in that case.
- Existing `_pump_date_category_from_cert` (reads [0]'s pump_age)
  unchanged — Elmhurst lodges the dwelling's pump_age on detail[0]
  regardless of which system the pump serves.

Cohort safety: all 6 cohort certs have a single main system (gas
boiler, category 2) → `all_main_systems_are_heat_pumps` returns
False → pump_w applies, same as the prior `else` branch. Cert 0380
(ASHP) has a single HP main → True → pump_w = 0, unchanged.

Cert 000565 cascade snapshot (HEAD 59de805e → this):
  (70)m pumps_fans gain   [0]*12  → [3,3,3,3,3,0,0,0,0,3,3,3] ✓ EXACT
  sap_score (int)             29 ✓ EXACT (preserved)
  sap_score_continuous   28.5007 → 28.508742  (Δ -0.0080 → +0.000042)
                                  **← essentially exact at 4.2e-5**
  ecf                     5.3876 →  5.386823  (Δ +0.0010 → +0.0002)
  total_fuel_cost_gbp    4680.97 → 4680.2515  (Δ +0.71 → -0.008)
  co2_kg_per_yr          6448.53 → 6447.6161  (Δ +0.90 → -0.010)
  space_heating_kwh     59018.52 → 59008.2363 (Δ +10.17 → -0.114)
  main_heating_fuel     34716.78 → 34710.7272 (Δ +5.98 → -0.067)

**Cert 000565 continuous SAP now exact at 1e-4 tolerance.** Every
intermediate (66-73, 83-84, 93-98, fuel/cost/CO2) closes the
worksheet at ≤1e-3 relative error.

Pyright net-zero (17 → 17 errors across touched files).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 19:46:46 +00:00
Khalim Conn-Kowlessar
92de07efba feat(property): Property aggregate + PropertyRepository (#1132)
Add the Ara modelling aggregate root (ADR-0002): domain/property/ with
PropertyIdentity, SiteNotes, Property, Properties. Property.source_path
implements the two disjoint source paths + Recency Tie-Break (ADR-0001;
survey wins on an equal date); effective_epc resolves to the surveyed data
(Site Notes path) or the public EPC (epc_with_overlay path — Landlord
Overrides overlay is a later slice). Pure dataclasses, no infrastructure imports.

PropertyRepository port + PropertyPostgresRepository hydrate the aggregate
whole from a defensive view of the FE-owned 'property' table (identity columns)
plus the EPC slice via EpcRepository.get_for_property. Reads only from repos
(ADR-0003). 8 domain + 1 hydration test; pyright strict clean.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-05-30 19:39:54 +00:00
Khalim Conn-Kowlessar
59de805e63 Slice S0380.113: H=0 gable lodgement deducts per RdSAP 10 §3.9.2 step (b)
RdSAP 10 §3.9.2 step (b) (PDF p.23) verbatim:

  "Software calculates the area of each gable or adjacent wall by
  using the equation:
         A_RR_gable = L_gable × (0.25 + H_gable) − [(H_gable − H_common_1)² / 2
                                                   + (H_gable − H_common_2)² / 2]"

Step (d):
  A_RR_final = A_RR_wall − (Σ A_common + Σ A_gable + Σ A_party
                            + Σ A_sheltered + Σ A_connected)

The spec equation is signed and applies for all L > 0 — including
H_gable = 0. When the gable is shorter than the common walls the
correction term `(H_gable − H_common)² / 2` exceeds the
L × (0.25 + H_gable) term, producing a negative A_RR_gable.
Elmhurst's worksheet evaluates the equation literally; the negative
value adjusts A_RR_final upward via step (d) without billing a
physical wall area.

Cert 000565 §8.1 lodges Ext3's RR (Simplified Type 2) with an
absent Gable Wall 2:

  Gable Wall 1   L=9.00  H=7.00   Exposed     U=0.45
  Gable Wall 2   L=4.00  H=0.00               U=0.00   ← lodged but H=0
  Common Wall 1  L=5.00  H=1.50               U=0.45
  Common Wall 2  L=7.50  H=0.30               U=0.45

Spec equation for Gable Wall 2:
  A_gable_2 = 4 × (0.25 + 0) − (0 − 1.5)²/2 − (0 − 0.30)²/2
            = 1.0 − 1.125 − 0.045 = −0.17 m²

Worksheet (30) Ext3 residual = 17.35 m² back-solves exactly:
  A_RR_shell = 12.5 × √(32.0 / 1.5)                = 57.7350
  Σ walls (incl. -0.17 absent gable)               = 40.3850
  residual = shell − walls                         = 17.3500  ✓ 4 d.p.

Pre-slice the mapper had two clamps that together dropped the
spec-computed −0.17 m² adjustment:

  mapper.py:3350  `if length_m <= 0 or height_m <= 0: return None`
                  → filtered out any H=0 surface
  mapper.py:3443  `area_m2 = max(0.0, length_m * (0.25 + H) − correction)`
                  → clamped negative gable areas at 0

Combined the cascade computed residual = 17.18 m² (cascade UNDER
by 0.17). Plus a related secondary `if height_m > h` filter on the
correction sum that masked the all-common-walls-taller case.

3-layer fix:

1. `datatypes/epc/domain/mapper.py` `_map_elmhurst_rir_surface`:
   - Split the early-return filter: drop only when L<=0 (no wall),
     OR when H<=0 AND not (Simplified Type 2 with common walls).
   - Apply the spec gable-area formula to BOTH `gable_wall` (party
     default) and `gable_wall_external` kinds in Simplified Type 2
     (the U-value routing differs by kind, but the area equation
     is the same).
   - Remove `max(0.0, ...)` clamp so the signed result reaches the
     cascade.
   - Remove `if height_m > h` correction-sum filter (spec applies
     the full square unconditionally).

2. `domain/sap10_calculator/worksheet/heat_transmission.py` per-
   surface loop:
   - `gable_wall` branch: skip `party += 0.25 × area` when area < 0
     (wall doesn't exist physically) but still add the signed area
     to `rr_walls_in_a_rr_area` so the residual deduction in step (d)
     grows by |area|.
   - `gable_wall_external` branch: same skip pattern for `walls +=
     u × area` and `rr_detailed_area += area`.

Cohort safety: only cert 000565 Ext3 hits this in the corpus. All
other cohort certs are Type 1 RR (no common walls, formula gives
the same answer) or have all gables H > 0. The cascade's per-element
test pins (Ext1's Connected gable + Exposed gable, Ext4's Detailed
RR) unchanged.

Cert 000565 cascade snapshot (HEAD a461b70d → this):
  roof_w_per_k         51.3185 → 51.3768  ✓ EXACT (Δ -0.06 → -0.003)
  total_external_area 857.46  → 857.6323  ✓ EXACT (Δ -0.18 → -0.008)
  thermal_bridging    128.62  → 128.6448  ✓ EXACT (Δ -0.03 → -0.005)
  total_w_per_k       936.97  → 937.0563  ✓ EXACT (Δ -0.09 → -0.004)

  sap_score (int)         29 ✓ EXACT (preserved)
  sap_score_continuous 28.5027 → 28.5007 (Δ -0.0060 → -0.0080)
  ecf                   5.3877 →  5.3876
  total_fuel_cost_gbp  4681.01 → 4680.97
  co2_kg_per_yr        6448.59 → 6448.53
  space_heating_kwh   59019.21 → 59018.52
  main_heating_fuel   34715.31 → 34716.78

**Cert 000565 fabric cascade now essentially exact** (HTC −0.004 W/K
total residual across all 8 fabric components). The remaining
continuous SAP -0.0080 / cost +£0.71 / SH +10 kWh residuals come
from non-fabric upstream (likely ventilation or appliances) —
candidates for a future audit.

Pyright net-zero (57 → 57 errors across touched files).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 19:23:12 +00:00
Khalim Conn-Kowlessar
a461b70d19 Slice S0380.112: per-BP rooflight allocation (RdSAP 10 §3.7 p.19)
RdSAP 10 §3.7 (PDF p.19) verbatim:

  "for each building part, software will deduct window/door areas
  contained in the relevant wall areas"

The same per-BP deduction applies to roof windows / rooflights
piercing each BP's roof. Pre-slice the cascade lumped every
rooflight's area onto BP[0] Main's `rw_area_part` (S0380.106-era
convention), leaving the actual host BP's gross roof un-deducted.

Cert 000565 §11 Openings lodges:
  Roof Windows 1(Ext2)  External roof Ext2, 1.20 m²
  Roof Windows 2(Ext4)  External roof Ext4, 0.50 m²

Worksheet (30) ground truth — each rooflight deducts from its
host BP's gross roof:
  Ext2: 25.00 − 1.20 = 23.80 net × 0.30 = 7.1400 W/K
  Ext4:  3.00 − 0.50 =  2.50 net × 0.00 = 0.0000 W/K

Pre-slice cascade:
  Ext2: 25.00 (un-deducted) × 0.30 = 7.5000 (+0.36 W/K over)
  Plus 1.70 m² of RW area lumped onto Main's external aggregate
  → +1.20 m² double-count (Ext2 gross + Main rw_area_part)

3-layer fix:
1. `datatypes/epc/domain/epc_property_data.py`: add `window_location:
   Union[int, str] = 0` to SapRoofWindow (mirror of
   `SapWindow.window_location` shape).
2. `datatypes/epc/domain/mapper.py` `_map_elmhurst_roof_window`:
   thread `w.building_part` through (mirror of
   `_map_elmhurst_window`'s pass-through).
3. `domain/sap10_calculator/worksheet/heat_transmission.py`: pre-loop
   compute `rw_area_by_bp[i]` from each `SapRoofWindow.window_location`
   via the existing `_window_bp_index` resolver; per-BP loop reads
   `rw_area_by_bp[i]` instead of allocating everything to BP[0].

Cohort safety: cert 000516's lone rooflight is on the Main BP
(Summary §11 row "Main, External wall"), so the per-BP allocation
returns Main = 0 = same as the prior lump-on-Main convention. The
000516 hand-built fixture's SapRoofWindow now sets
`window_location="Main"` to mirror the Elmhurst mapper string-form.

Cert 000565 cascade snapshot (HEAD 794ef7ed → this):
  roof_w_per_k          51.6773 → 51.3185 (Δ +0.30 → -0.06)
  total_external_area  858.66  → 857.46  (Δ +1.02 → -0.18)
  thermal_bridging_w/k 128.80  → 128.62  (Δ +0.15 → -0.03)
  sap_score (int)          28 → 29 ✓ EXACT (recovered)
  sap_score_continuous 28.4903 → 28.5027  (Δ -0.0184 → -0.0060)
  ecf                   5.3887 →  5.3877
  total_fuel_cost_gbp  4681.89 → 4681.01
  co2_kg_per_yr        6449.73 → 6448.59
  space_heating_kwh   59031.86 → 59019.21
  main_heating_fuel   34724.63 → 34715.31

Closes the +1.20 m² Ext2 rooflight double-count. Remaining
residuals (Ext3 -0.17 m² + -0.06 W/K) closed by S0380.113 (H=0
gable retention).

Pyright net-zero (58 → 58 errors across touched files).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 19:15:16 +00:00
Khalim Conn-Kowlessar
9461e657a5 Slice S0380.110: per-rooflight g_L in Appendix L L2a (SAP 10.2 p.88)
SAP 10.2 Appendix L §L2a (PDF p.88) verbatim:

    GL = 0.9 × Σ (Aw × gL × FF × ZL) / TFA                  (L2a)

    where
      FF is the frame factor (fraction of window that is glazed) for
          the actual window or from Table 6c
      Aw is the area of a window, m²
      gL is the light transmittance factor from Table 6b
      ZL is the light access factor from Table 6d

Table 6b gL (PDF p.178) — light transmittance column:
  Single glazed                     0.90
  Double glazed (any variant)       0.80
  Triple glazed (any variant)       0.70

Table 6d note 2 (PDF p.178): "A solar access factor of 1.0 and a light
access factor of 1.0 should be used for roof windows/rooflights."

Pre-slice `_daylight_factor_from_cert` collapsed every rooflight into
a single `rooflight_total_area_m2 × _G_LIGHT_DEFAULT (0.80) ×
_FRAME_FACTOR_DEFAULT (0.70)` product, overcounting any Triple-glazed
rooflight (gL=0.70) or any non-default frame factor.

Cert 000565 §11 lodges 2 rooflights (per S0380.107 routing):
  Item 2 (Ext2 NR rooflight): 1.2 m², "Triple between 2002 and 2021",
    PVC FF=0.70 → gL=0.70 (Table 6b Triple). Correct numerator
    contribution 1.2 × 0.70 × 0.70 = 0.588; pre-slice cascade used
    1.2 × 0.80 × 0.70 = 0.672 (+0.084 over).
  Item 5 (Ext4 A rooflight): 0.5 m², "Double between 2002 and 2021",
    Wood FF=0.70 → gL=0.80 (Table 6b Double). Already matched.

The +0.084 numerator delta lowered GL → lowered C_daylight → lowered
worksheet (232) by 2.17 kWh/yr.

3-layer fix:
1. `datatypes/epc/domain/epc_property_data.py`: add `glazing_type:
   int = 3` to SapRoofWindow (default = Double 2002-2021, the cohort
   modal).
2. `datatypes/epc/domain/mapper.py` `_map_elmhurst_roof_window`:
   populate `glazing_type` via `_elmhurst_glazing_type_code(w.
   glazing_type)` — mirror of `_map_elmhurst_window`.
3. `domain/sap10_calculator/worksheet/internal_gains.py`
   `_daylight_factor_from_cert`: iterate `epc.sap_roof_windows` for
   the rooflight g_L numerator, dispatching via existing
   `_G_LIGHT_BY_GLAZING_CODE` + `rw.frame_factor`. Z_L = 1.0 per
   Table 6d note 2.

Test coverage:
- AAA test `test_summary_000565_rooflight_per_window_g_l_routes_via_
  glazing_type_per_sap_10_2_appendix_l_l2a` pins both per-rooflight
  glazing codes (9 Triple / 3 Double) AND `inputs.lighting_kwh_per_
  yr` at 1384.8353 ±1e-4.
- 000516 hand-built fixture updated to explicitly set glazing_type=2
  ("Double pre 2002") matching the lodged label.

Cert 000565 cascade snapshot (HEAD 98a4b5b9 → this):
  sap_score (int)             29       ✓ EXACT (preserved)
  lighting_kwh_per_yr     1382.6657 → 1384.8353  ✓ EXACT (-2.17 → 0)
  sap_score_continuous     28.5028  →  28.5002   (Δ -0.0059 → -0.0085)
  ecf                       5.3874  →   5.3877   (Δ +0.0008 → +0.0011)
  total_fuel_cost_gbp    4680.78    → 4681.01    (+0.52 → +0.75)
  co2_kg_per_yr          6448.34    → 6448.59    (+0.72 → +0.96)
  space_heating_kwh     59020.02    → 59019.18   (+11.67 → +10.83)
  main_heating_fuel     34717.66    → 34717.16   (+6.87  → +6.37)

Lighting closure exposes a previously-cancelling residual elsewhere —
continuous SAP magnitude widens slightly (-0.0059 → -0.0085) but the
spec-correct path is now in place, per [[feedback-spec-floor-
skepticism]]. SH + main_heating_fuel improve (added lighting energy
contributes internal gains, reducing SH demand). Integer SAP 29 ✓
EXACT preserved.

Cohort safety: 6 cohort certs have at most 1 rooflight each
(000516 W6 only, lodged "Double pre 2002" → code 2). Their gL still
resolves to 0.80 via the existing `_G_LIGHT_BY_GLAZING_CODE` table,
so the per-rooflight dispatch produces the same numerator as the
old default branch.

Pyright net-zero (50 → 50 errors across touched files).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 18:31:35 +00:00
Khalim Conn-Kowlessar
98a4b5b9e6 docs: handover + next-agent prompt post S0380.105..109 (MEV trifecta + window routing + Connected gable + §5.7/5.8 brick formula)
Captures the 5-slice session that took cert 000565 continuous SAP
from +0.0182 → -0.0059 (magnitude 67% smaller) via spec-cited
intermediate-value closures.

  HANDOVER_POST_S0380_109.md     full state + per-slice movement
                                 + per-pin journey + lessons learned
  NEXT_AGENT_PROMPT_POST_S0380_109.md   focused briefing pointing
                                 at S0380.110 (Lighting g×FF closure
                                 — leading remaining residual at
                                 -2.17 kWh) and S0380.111 (roof
                                 window U formula refinement).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 18:16:16 +00:00
Khalim Conn-Kowlessar
efb203f7ad Slice S0380.109: Solid brick + insulation via §5.7 Table 13 + §5.8 Table 14 (RdSAP 10)
Closes the remaining cert 000565 BP[0] Main wall residual (-1.54 W/K
under ws) by routing solid-brick walls with documentary wall
thickness + lodged insulation through the RdSAP 10 §5.7 + §5.8
formula chain. Adds a Table-6 footnote (a) cap on the §5.6 stone
formula to handle thin uninsulated stone walls (Ext1 BP[1] Granite
W=50 mm).

RdSAP 10 §5.7 Table 13 (PDF p.41) verbatim:

  "Default U-values of brick walls
   Wall thickness, mm   U-value, W/m²K
   Up to 200 mm         2.5
   200 to 280 mm        1.7
   280 to 420 mm        1.4    ← cert 000565 Main W = 300 mm
   More than 420 mm     1.1"

RdSAP 10 §5.8 step 2 (PDF p.41-42) verbatim:

  "The U-value of the insulated wall is U = 1 / (1/U₀ + R_insulation)
   ...
   Where R_insulation comes from Table 14: Insulation thickness and
   corresponding resistance.
   ...
   R = 0.025 × T + 0.25 when λ = 0.04 W/m·K
   R = 0.0333 × T + 0.248 when λ = 0.03 W/m·K
   R = 0.040 × T + 0.25 when λ = 0.025 W/m·K
   Where T is thickness of insulation in mm"

Cert 000565 Main lodgement (Summary §7.0):
  Type SO Solid Brick (wall_construction = 3)
  Insulation E External (wall_insulation_type = 1)
  Insulation Thickness 75 mm
  Wall Thickness 300 mm (measured)
  Conductivity Known No  → λ defaults to 0.04 (§5.8 final note)
  Age band A

Formula chain:
  U₀ = 1.4 (§5.7 Table 13 row "280 to 420 mm")
  R  = 0.025 × 75 + 0.25 = 2.125 m²K/W
  U  = 1 / (1/1.4 + 2.125) = 1 / 2.8393 = 0.3522 → 0.35 (2 d.p.)

Pre-slice the cascade bucketed 75 mm into the Table-6 "100 mm
external/internal insulation" row → 0.32 for age A. The -0.03 U
delta on Main's 51.72 m² external wall is the entire -1.54 W/K
under-count driving the cohort's remaining fabric residual.

RdSAP 10 Table 6 footnote (a) (PDF p.34) verbatim:

  "Or from equations in 5.6 if the calculated U-value is less than
   1.7."

Applies only to the AS-BUILT (no insulation, no dry-line) Table 6
row. For thin walls where §5.6 gives U ≥ 1.7 the Table 6 row
default of 1.7 caps the result. Verified empirically against cert
000565 Main alt_wall_1 (granite W=120 mm dry-lined): raw §5.6 →
3.879 + dry-line → 2.34 matches worksheet, NOT capped 1.7 + dry-
line → 1.32. The cap therefore only fires when neither dry-lining
nor insulation is present (cert 000565 BP[1] Ext1: granite W=50 mm
"Insulation Unknown" → §5.6 = 6.09 → capped to 1.7, matches ws).

3-layer fix:
1. `domain/sap10_ml/rdsap_uvalues.py`:
   - Add `_u_brick_thin_wall_age_a_to_e(W_mm)` per §5.7 Table 13
   - Add `_r_insulation_table_14(T_mm, λ)` per §5.8 Table 14
     interpolation rule (handles all 3 λ columns)
   - Wire §5.7+§5.8 chain into `u_wall` for WALL_SOLID_BRICK + age
     A-E + lodged thickness + (External | Internal) insulation +
     thickness > 0
   - Add Table 6 footnote (a) cap to `_u_stone_thin_wall_age_a_to_e`
     (cap at 1.7 only when not dry-lined)
   - Round dry-lined §5.6 result to 2 d.p. (worksheet A×U precision)
2. `domain/sap10_calculator/worksheet/heat_transmission.py` passes
   `wall_thickness_mm=part.wall_thickness_mm` through to `u_wall`
   for the per-BP main wall U (previously passed only for alt walls).
3. AAA test pins cert 000565 walls_w_per_k = 604.07 within 1e-4.

Movement at HEAD `9159e91f` → post-slice (cert 000565):

Fabric (cascade vs ws):
  walls         602.53 → 604.08 (Δ -1.54 → +0.01 W/K — sub-spec
                                  alt-wall float rounding artifact)
  total W/K     935.54 → 937.09 (Δ -1.52 → +0.03 W/K — essentially
                                  zero net fabric HTC residual)

End-result pins:
  sap_score (int)    29 ✓ EXACT  (unchanged)
  sap_score_continuous 28.5380 → 28.5028  (Δ +0.0293 → -0.0059;
                                          80% magnitude reduction)
  ecf              5.3838 →  5.3874 (Δ -0.0028 → +0.0008)
  total_fuel_cost_gbp 4677.64 → 4680.78 (Δ -2.62 → +0.52)
  co2_kg_per_yr   6444.27  → 6448.34 (Δ -3.35 → +0.72)
  space_heating  58974.84  → 59020.02 (Δ -33.5 → +11.7)
  main_heating_fuel 34691.09 → 34717.66 (Δ -19.7 → +6.87)
  lighting_kwh    1382.67 (unchanged)
  pumps_fans_kwh ✓ EXACT (unchanged)

Continuous SAP magnitude improved 80% (0.0293 → 0.0059). All
SH-driven downstream residuals (cost, co2, SH kwh, main_heating
fuel) magnitude-reduced 65-80%. Integer SAP stays exact at 29.

Cohort safety verified: 6 cohort certs (000474-000516) lodge wc=4
(cavity) + wit=4 (as-built) — neither precondition for the new
§5.7+§5.8 path. §5.6 cap only fires when not dry-lined (cohort
certs don't trigger). All 11 cert→inputs and 6 sap_result_pin
cohort tests pass unchanged.

Golden cert 6035-7729-2309-0879-2296 (mid-terrace age A solid
brick) sees the §5.7+§5.8 chain fire on its Main wall:
  PE  +46.7562 → +46.0936 kWh/m² (cascade closer to actual EPC)
  CO2 +1.0652  → +1.0495 tonnes/yr (cascade closer to actual EPC)
Per [[feedback-golden-residuals-near-zero]] the expected pin is
updated to track the improvement (target → ~0 as mapper closes).

Test count: 608 pass + 7 expected 000565 fails → **608 pass + 7
expected 000565 fails** (new §5.7+§5.8 formula test green; golden
cert 6035 pin re-pinned; integer SAP stays at 29). Pyright net-zero
per touched file (27 baseline → 27 post-change).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 18:10:33 +00:00
Khalim Conn-Kowlessar
9159e91fbc Slice S0380.108: Connected-to-heated-space RR gables deduct from A_RR (RdSAP 10 §3.9.2 + Table 4 row 4)
Closes the largest single localised fabric residual on cert 000565
(roof +1.59 W/K over, area +4.70 m² over) by routing
Connected-gable surfaces through a new `connected_wall` kind that
deducts area from the residual A_RR per the spec but contributes
0 W/K per RdSAP 10 Table 4 row 4.

RdSAP 10 §3.9.2 step (d) (PDF p.23) verbatim:

  "The areas of gable walls are deducted from the calculated total
   RR area, and the remaining area of RR, ARR_final is then
   calculated. This area is treated as roof structure.
       ARR_final = ARR_wall − (ΣARR_common_wall + ΣARR_gable +
                               ΣARR_party + ΣARR_sheltered +
                               ΣARR_connected)"

RdSAP 10 Table 4 row 4 (PDF p.22):

  "ARR_connected — Adjacent to heated space — U-value = 0"

The U=0 means no heat-loss contribution, but the area STILL appears
in the deduction equation as ΣARR_connected. Pre-slice the mapper's
`_map_elmhurst_rir_surface` returned None for Connected gables,
dropping them entirely from `detailed_surfaces` so the cascade
neither billed them nor deducted them. The residual A_RR was
therefore over by their lodged area.

Cert 000565 Ext1 §8.1 lodges (Simplified Type 2):
  Gable Wall 1   L=4.00  H=6.00  Connected  U=0
  Gable Wall 2   L=8.00  H=9.00  Exposed    U=1.70
  Common Wall 1  L=9.00  H=1.00  U=1.70
  Common Wall 2  L=5.00  H=1.80  U=1.70

Gable Wall 1 area via §3.9.2 quadratic:
  A_gable_1 = 4 × (0.25 + 6)
              − (6 − 1)²/2   ← subtract triangle above Common Wall 1
              − (6 − 1.8)²/2 ← subtract triangle above Common Wall 2
            = 25.0 − 12.5 − 8.82
            = 3.68 m²

Pre-slice:
  A_RR shell = 12.5 × √(34 / 1.5) = 59.51 m²
  Σ wall areas = 11.25 + 10.25 + 16.08 = 37.58 m²
  Residual    = 21.93 m² (worksheet: 18.25; over by +3.68)
  Roof W/K = 21.93 × 0.35 = 7.68 (worksheet: 6.39; over by +1.29)

3-layer fix:
1. Mapper `_map_elmhurst_rir_surface` (datatypes/epc/domain/mapper.py)
   now routes "Connected" gable_type to kind="connected_wall" with
   u_value=0 and area via the Simplified Type 2 quadratic correction.
2. Heat transmission `heat_transmission_from_cert` (domain/sap10_
   calculator/worksheet/heat_transmission.py) adds a connected_wall
   branch that deducts area from rr_walls_in_a_rr_area but skips
   walls/party W/K contribution.
3. AAA test pins Ext1 Connected gable area at 3.68 m² and U=0.

Movement at HEAD `b7fa5f74` → post-slice (cert 000565):

Fabric (cascade vs ws):
  walls           602.53 → 602.53 (Δ -1.54 W/K; unchanged)
  roof             52.97 →  51.68 (Δ +1.59 → +0.30 W/K; closes 81%)
  TB              129.35 → 128.80 (Δ +0.70 → +0.15 W/K; closes 79%)
  total area      862.34 → 858.66 (Δ +4.70 → +1.02 m²; closes 78%)
  total W/K       937.40 → 935.54 (Δ +0.33 → -1.52 W/K; sign flips)

End-result pins:
  **sap_score (int)   28 → 29 ✓ EXACT vs ws 29**  (RECOVERED from
                                                   S0380.107 transient
                                                   rounding flip)
  sap_score_continuous 28.4959 → 28.5380 (Δ -0.0128 → +0.0293)
  ecf                   5.3881 →  5.3838 (Δ +0.0015 → -0.0028)
  total_fuel_cost_gbp 4681.39  → 4677.64 (Δ +1.13 → -2.62)
  co2_kg_per_yr      6449.13  → 6444.27 (Δ +1.51 → -3.35)
  space_heating_kwh 59028.80  → 58974.84 (Δ +20.5 → -33.5)
  main_heating_fuel 34722.83  → 34691.09 (Δ +12.0 → -19.7)
  lighting_kwh       1382.67  → 1382.67 (unchanged)
  pumps_fans_kwh ✓ EXACT (unchanged)

Continuous SAP and downstream pins SIGN-FLIPPED again
(cascade was over post-.107, now under post-.108). Per user
direction: transient drift acceptable while closing a true
intermediate-value bug. The remaining net HTC -1.52 W/K is
mostly walls (-1.54 W/K) — closing the Detailed-RR walls
residual is the next leverage front.

Cohort safety: none of the 6 cohort certs lodge a Connected
gable (grep audit across all Summary fixtures). The new
`connected_wall` branch only fires for the cert 000565 Ext1 BP.

Test count: 606 pass + 8 expected 000565 fails → **608 pass +
7 expected 000565 fails** (sap_score back to exact + new
Connected-gable test green). Pyright net-zero per touched
file (57 baseline → 57 post-change).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 17:40:42 +00:00
Khalim Conn-Kowlessar
8effa2d00d Slice S0380.106: MEV fans PE split via Table 12a Grid 2 + Table 12e (SAP 10.2 §10a / §10c)
PE-side mirror of S0380.103 (cost) + S0380.105 (CO2). Completes the
MEV cascade trifecta for off-peak tariff certs. Cert 000565
worksheet line (281):

  Pumps, fans and electric keep-hot  252.5159  1.5239  383.3796 (281)

The displayed factor (1.5239) is the ALL_OTHER_USES Table 12e Σ
days-weighted blend; the displayed product (383.3796) is the kWh-
weighted blend across the two Grid 2 categories:

  F_FANS  = 0.58 × F_code34 + 0.42 × F_code33 = 1.51268 kWh/kWh
  F_OTHER = 0.80 × F_code34 + 0.20 × F_code33 = 1.52391 kWh/kWh
  F_eff   = (127.5159 × 1.51268 + 125.0 × 1.52391) / 252.5159
          = 1.51824 kWh/kWh
  PE      = 252.5159 × 1.51824 = 383.3796 kWh/yr ✓

Pre-slice the cascade applied 1.52391 to ALL 252.5159 kWh →
384.81 → +1.43 over ws.

SAP 10.2 Table 12a Grid 2 (PDF p.191) — same dispatch as Slice
S0380.105 — splits the off-peak high-rate fraction by end-use
between `FANS_FOR_MECH_VENT` and `ALL_OTHER_USES`.

SAP 10.2 Table 12e (PDF p.195) verbatim header:

  "Where electricity is the fuel used, the relevant set of factors
   in the table below should be used to calculate the monthly
   primary energy instead the annual average factor given in
   Table 12."

The Grid 2 high-rate fraction blends Table 12e high-rate × low-
rate codes per `F_blended = high_frac × F_high + (1 − high_frac)
× F_low`. MEV fans bill at the lower 0.58 high_frac → lower PE
factor on the higher-PE high-rate code 34. Identical structural
fix as the .105 CO2 slice; the only delta is the underlying Table
12 column.

2-layer fix:
1. New helper `_pumps_fans_primary_factor` in cert_to_inputs.py
   — mirror of `_pumps_fans_co2_factor_kg_per_kwh`. Returns kWh-
   weighted blend of FANS_FOR_MECH_VENT + ALL_OTHER_USES factors.
   Falls back to ALL_OTHER_USES rate on STANDARD / no-MEV certs.
2. Call site at line 4640 wires `mev_kwh_for_cost_split` +
   `pumps_fans_kwh` through the helper.

Movement at HEAD `8a3aaf7a` → post-slice (cert 000565):

| Pin                            | Pre        | Post       |
|--------------------------------|-----------:|-----------:|
| pumps_fans_primary_factor       |    1.52391 |    1.51824 |
| pumps_fans_pe_kwh_per_yr        |   384.8122 |   383.3797 |  ✓ EXACT vs ws (281)
| primary_energy_kwh_per_yr       | 62228.4896 | 62227.0570 |
| primary_energy_kwh_per_m2       |   194.5187 |   194.5143 |

No effect on sap_score_continuous (ECF is cost-based, not PE-based),
ecf, or any of the 7 currently-failing 000565 pins. The total PE
residual remains dominated by an unrelated SH cascade PE factor
gap (cascade 170 kWh/m² vs ws 135.6 — separate slice).

Cohort safety: STANDARD-tariff and no-MEV certs return the existing
ALL_OTHER_USES rate (helper falls through). No-MEV certs return
the same rate (mev_kwh_per_yr=0 short-circuit). Pyright net-zero
per touched file (45 baseline → 45 post-change).

Test count: 605 pass + 7 expected 000565 fails → **606 pass + 7
expected 000565 fails** (new
test_summary_000565_mev_fans_pe_factor_uses_table_12a_grid_2_
fans_for_mech_vent_split GREEN; 7 known 000565 fails set unchanged).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 16:59:56 +00:00
Khalim Conn-Kowlessar
8a3aaf7ae6 Slice S0380.105: MEV fans CO2 split via Table 12a Grid 2 + Table 12d (SAP 10.2 §10a / §10b)
Mirror of S0380.103 for the CO2 cascade. Cert 000565 worksheet line
(267):

  Pumps, fans and electric keep-hot  252.5159  0.1412  35.3349 (267)

The displayed factor (0.1412) is the ALL_OTHER_USES Table 12d Σ
days-weighted blend; the displayed product (35.3349) is the kWh-
weighted blend across the two Grid 2 categories:

  F_FANS  = 0.58 × F_code34 + 0.42 × F_code33 = 0.13872 kg/kWh
  F_OTHER = 0.80 × F_code34 + 0.20 × F_code33 = 0.14116 kg/kWh
  F_eff   = (127.5159 × 0.13872 + 125.0 × 0.14116) / 252.5159
          = 0.13993 kg/kWh
  CO2     = 252.5159 × 0.13993 = 35.3349 kg/yr ✓

Pre-slice the cascade applied 0.14116 to ALL 252.5159 kWh →
35.6457 → +0.31 over ws.

SAP 10.2 Table 12a Grid 2 (PDF p.191) verbatim header:

  "Fractions of electricity used at the higher rate, for use in
   off-peak tariff calculations
   ...
   Fans for mechanical ventilation systems   10-hour: 0.58
   All other uses, and locally generated     10-hour: 0.80
     electricity"

SAP 10.2 Table 12d (PDF p.194) verbatim header:

  "Where electricity is the fuel used, the relevant set of factors
   in the table below should be used to calculate the monthly CO2
   emissions INSTEAD of the annual average factor given in Table
   12."

The Grid 2 high-rate fraction blends Table 12d high-rate × low-
rate codes per `F_blended = high_frac × F_high + (1 − high_frac)
× F_low`. MEV fans bill at the lower 0.58 high_frac → lower CO2
factor on the higher-carbon high-rate code 34. Cost-side S0380.103
landed the same split for tariff prices; this slice mirrors it
for the CO2 factor.

3-layer fix:
1. New helper `_pumps_fans_co2_factor_kg_per_kwh` returns the
   kWh-weighted blend across `FANS_FOR_MECH_VENT` + `ALL_OTHER_USES`
   factors. Falls back to the existing `ALL_OTHER_USES` rate on
   STANDARD tariff and no-MEV certs (cohort-safe).
2. cert_to_inputs.py wires `mev_kwh_for_cost_split` +
   `pumps_fans_kwh` through to the new helper.
3. Field `CalculatorInputs.pumps_fans_co2_factor_kg_per_kwh`
   already exists from S0380.65; calculator legacy path unchanged.

Movement at HEAD `7df3fef8` → post-slice (cert 000565):

| Pin                          | Pre        | Post       | Δ vs ws  |
|------------------------------|-----------:|-----------:|---------:|
| pumps_fans_co2_kg_per_yr     |    35.6457 |    35.3349 |   ✓ 0    |
| co2_kg_per_yr (TOTAL)        |  6445.8198 |  6445.5090 |  −2.1173 |

The total CO2 residual moves -1.81 → -2.12 (sign-flip pattern of
S0380.103): the previously-cancelling pumps_fans CO2 over-count
masked the main-heating-fuel CO2 under-count (downstream of the
§3-§8 SH cascade -16 kWh fuel residual). Per user direction
(NEXT_AGENT_PROMPT) transient continuous-SAP / TOTAL drift is OK
while closing a true spec-correct intermediate-value bug; the SH
cascade closure is a separate slice.

Cohort safety: STANDARD-tariff certs return the existing
ALL_OTHER_USES rate (helper falls through). No-MEV certs return
the same rate (mev_kwh_per_yr=0 short-circuit).

Test count: 604 pass + 7 expected 000565 fails → **605 pass + 7
expected 000565 fails** (new
test_summary_000565_mev_fans_co2_factor_uses_table_12a_grid_2_
fans_for_mech_vent_split GREEN). Pyright net-zero per touched
file (45 baseline → 45 post-change).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 16:48:53 +00:00
Khalim Conn-Kowlessar
7df3fef8bb docs: handover + next-agent prompt post S0380.96..103 (RIR Unknown + §9 floor + MEV PCDB arc + HP-on-E7 cost split)
8 slices shipped this session:
  S0380.96  RIR Unknown insulation       (RdSAP 10 §3.10.1)
  S0380.97  Floor §9 insulation thickness (RdSAP 10 §5.13 Table 20)
  S0380.98  PCDB Table 322 ETL+parser    (PCDF Spec §A.19)
  S0380.99  PCDB Table 329 ETL+parser    (PCDF Spec §A.20)
  S0380.100 MEV SFPav + (230a) helpers   (SAP 10.2 §2.6.4)
  S0380.101 HP SAP code → cat=4 mapper   (SAP 10.2 Table 4a)
  S0380.102 Wire MEV into pumps_fans     (SAP 10.2 Table 4f 230a)
  S0380.103 MEV-fan cost split           (SAP 10.2 Table 12a Grid 2)

Cert 000565 at HEAD `e3abe9b2`:
  sap_score (int)              ✓ EXACT
  pumps_fans_kwh_per_yr        ✓ EXACT (was +2.48 over)
  hot_water_kwh_per_yr         ✓ 0 EXACT
  sap_score_continuous         Δ +0.0182 (SH cascade-driven)
  7 expected fails (was 9)

Next slice candidate: S0380.104 investigate §3-§8 space-heating
cascade -27 kWh under-count (cert-000565-specific; cohort certs
pass at 1e-4). Alternative: S0380.105 CO2 MEV split (mirror of
.103 for Table 12d monthly factors).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 16:13:33 +00:00
Khalim Conn-Kowlessar
e3abe9b2b5 Slice S0380.103: MEV fans cost split via Table 12a Grid 2 FANS_FOR_MECH_VENT rate (SAP 10.2 Table 12a)
SAP 10.2 Table 12a Grid 2 (PDF p.191) splits off-peak electricity
costs into two categories:

  Other electricity uses                       Tariff    Fraction at
                                                          high rate
  Fans for mechanical ventilation systems      7-hour    0.71
                                              10-hour    0.58
  All other uses, and locally generated        7-hour    0.90
  electricity                                 10-hour    0.80

Cert 000565 (Dual meter, 10-hour off-peak, MEV decentralised) lodges
127.5159 kWh of MEV-fan electricity (line 230a) that bills at the
`FANS_FOR_MECH_VENT` blend (0.58 × 14.68 + 0.42 × 7.50 = 11.6644
p/kWh), distinct from the 125 kWh of other pumps_fans (45 kWh gas-
boiler flue fan + 80 kWh solar HW pump) which bills at the
`ALL_OTHER_USES` blend (0.80 × 14.68 + 0.20 × 7.50 = 13.2440 p/kWh).

Pre-slice the cascade applied `ALL_OTHER_USES` to ALL 252.5159 kWh,
over-counting MEV cost by 127.5159 × (0.13244 - 0.11664) = +£2.01/yr.

Worksheet pin verification (line (249)):
  "Pumps, fans and electric keep-hot ... 172.5159  13.2440  20.8338"
  127.5159 × 0.11664 + 45 × 0.13244 = £14.8753 + £5.9598 = £20.8351
  ≈ ws £20.8338 ✓
  Pump for solar water heating 80.0 × 0.13244 = £10.5952 ✓

Implementation (3-layer):
1. `calculator.py:CalculatorInputs` — new optional
   `pumps_fans_fuel_cost_gbp_per_kwh: Optional[float] = None`.
2. `calculator.py` legacy cost path — `pumps_fans_cost` resolves
   via the new field with fallback to `other_fuel_cost_gbp_per_kwh`.
3. `cert_to_inputs.py:_pumps_fans_fuel_cost_gbp_per_kwh` — computes
   the kWh-weighted blended rate when off-peak + MEV is lodged.
   Reuses `_mev_decentralised_kwh_per_yr_from_cert` (S0380.102) to
   recover the MEV portion.

Cohort safety: STANDARD-tariff certs (the entire cohort except cert
000565) get None back → existing `other_fuel_cost_gbp_per_kwh`
fallback unchanged. Certs without MEV (zero MEV kWh) also get None
→ no behavioural change.

Movement at HEAD (cert 000565):
- pumps_fans_kwh_per_yr ✓ EXACT (unchanged)
- total_fuel_cost_gbp: 4680.6514 → 4678.6372  (Δ +£0.39 → -£1.62)
- ecf: 5.3873 → 5.3850 (Δ +0.0007 → -0.0016)
- sap_score_continuous: 28.5043 → 28.5269 (Δ -0.0044 → +0.0182)

Continuous-SAP residual drifted from -0.0044 to +0.0182 in absolute
value: closing the MEV cost over-count exposes a pre-existing
space-heating cascade under-count (main_heating_fuel_kwh is -16 kWh
under ws). Per user direction [[feedback-spec-floor-skepticism]]:
shipping spec-correct intermediate-value fixes even when they
transiently drift continuous SAP. The remaining residual is now
SH-cascade driven; a separate slice.

Test count: 597 pass + 7 expected 000565 fails unchanged.

Pyright net-zero per touched file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 16:07:55 +00:00
Khalim Conn-Kowlessar
a0413155ae Slice S0380.102: Wire MEV decentralised cascade into pumps_fans (SAP 10.2 §2.6.4 + Table 4f line 230a)
SAP 10.2 Table 4f line (230a) annual electricity for mechanical
ventilation fans, decentralised MEV branch:

    E_fans_kwh = SFPav × 1.22 × V

where SFPav is the §2.6.4 equation (1) flow-weighted average SFP
across every fan in the installation, with PCDB Table 322 supplying
per-configuration (flow, SFP) and PCDB Table 329 supplying the
ducting-type IUF.

This slice composes the foundation slices S0380.98 (Table 322),
S0380.99 (Table 329), S0380.100 (SFPav helper) into a cert-driven
cascade — `_mev_decentralised_kwh_per_yr_from_cert(epc)` reads:

    MV PCDF Reference Number  → PCDB Table 322 record (per-config SFP)
    Duct Type (Flexible/Rigid) → PCDB Table 329 in-use factor
    Wet Rooms count           → per-fan-type count distribution

Three coupled changes:

1. Elmhurst extractor + schema — `_extract_ventilation` parses §12.1
   "MV PCDF Reference Number", "Wet Rooms", "Duct Type", "Approved
   Installation". New fields on `VentilationAndCooling`.
2. Mapper — plumbs the lodgements through to
   `EpcPropertyData.mechanical_ventilation_index_number`,
   `.wet_rooms_count`, `.mechanical_vent_duct_type`. New
   `_elmhurst_mv_duct_type_int` helper (Flexible→1, Rigid→2 per PCDF
   Spec §A.20 field 12 convention) with strict-raise on unknown
   labels per [[unmapped-elmhurst-label]].
3. Cascade — `_table_4f_additive_components` calls the new
   `_mev_decentralised_kwh_per_yr_from_cert(epc)` to add the (230a)
   contribution alongside the existing flue-fan + solar-HW pump
   additions.

Per-fan count convention (reverse-engineered from cert 000565):
- Each PCDB-defined configuration (1..6) contributes 1 baseline fan.
- Through-wall configurations scale with wet-rooms count:
    through-wall kitchen (5):   wet_rooms_count fans
    through-wall other wet (6): wet_rooms_count + 1 fans
- Configurations with blank SFP (e.g. record 500755 in-duct codes 3,
  4) contribute 0 to the numerator but their flow rate to the
  denominator per SAP §2.6.4 "summation is over all the fans".

For cert 000565 (wet_rooms=2) this yields the worksheet's observed
fan distribution (1, 1, 1, 1, 2, 3) → SFPav = 11.7205 / 92.0 =
0.12740 W/(l/s), and (230a) = 0.12740 × 1.22 × 820.4385 = 127.5159
kWh/year ✓ matches worksheet line (230a) at 1e-4.

TODO: validate the count convention against a second MEV
decentralised fixture; the rule above fits cert 000565 alone.

Cert 000565 closure state at HEAD:
- pumps_fans_kwh_per_yr: 125.0 → 252.5159 ✓ EXACT (was 255.0 pre-arc;
  the MEV +127.5 contribution closes the residual)
- sap_score (int): 29 ✓ EXACT preserved
- sap_score_continuous: 28.69 (S0380.101 transient) → 28.5043 vs
  ws 28.5087 (Δ -0.0044). Was -0.0001 pre-arc — the MEV fix revealed
  a pre-existing residual elsewhere in the cost cascade (likely
  Table 12a HP-on-E7 high-rate split per the original TODO at
  mapper.py:4039-4040; deferred to a separate slice).

Test count: 603 pass + 7 expected 000565 fails (was 8 —
pumps_fans_kwh_per_yr flipped FAIL→PASS, removed from work queue).

Cohort safety: only cert 000565 lodges a non-None MV PCDF Reference
Number across the Summary fixture set; cohort certs return 0 from
`_mev_decentralised_kwh_per_yr_from_cert` (no MEV system).

Pyright net-zero per touched file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 15:45:55 +00:00
Khalim Conn-Kowlessar
44fb8c0724 Slice S0380.100: MEV SFPav + (230a) cascade helpers (SAP 10.2 §2.6.4 + Table 4f)
SAP 10.2 specification (14-03-2025) §2.6.4 (PDF p.16):

  "In the case of decentralised MEV the specific fan power is provided
   for each fan and an average value is calculated for the purposes of
   the SAP calculations. There are two types of fan, one for kitchens
   and one for other wet rooms, and three types of fan location (in
   room with ducting, in duct, or through wall with no duct). [...]
   The average SFP, including adjustments for the in-use factors, is
   given by:

       SFPav = Σ(SFP_j × FR_j × IUF_j) / Σ(FR_j)             (1)

   where the summation is over all the fans, j represents each
   individual fan, FR is the flow rate which is 13 l/s for kitchens
   and 8 l/s for all other wet rooms, and IUF is the applicable
   in-use factor."

And SAP 10.2 §5 Table 4f line (230a):

  "Annual electricity for mechanical ventilation fans (kWh/year) =
   IUF × SFP × 1.22 × V"

This slice lands the two pure-function cascade primitives:

  mev_sfp_av(fan_entries) -> float        # equation (1)
  mev_decentralised_kwh_per_yr(*, sfp_av, V) -> float   # (230a)

`MevFanEntry` carries the per-fan resolved (SFP_w_per_l_per_s, flow_l_
per_s, IUF) triple. Callers (PCDB Table 322 + Table 329 + cert
lodgement of duct type) compose the entries upstream; the cascade
helper does no PCDB resolution itself.

Cert 000565 worksheet line (230a) pinned at 1e-4:
  Σ FR = 92.0 l/s  (matches worksheet "total flow")
  Σ SFP×FR×IUF = 11.7205 W  (matches worksheet "total watage")
  SFPav = 11.7205 / 92.0 = 0.1274 W/(l/s) ✓ vs ws 0.1274
  (230a) = 0.1274 × 1.22 × 820.4385 = 127.5159 ✓ vs ws 127.5159

Pure-function helpers; no cascade integration yet. Next slice
S0380.101 wires HP category mapper; S0380.102 wires cert→inputs
to invoke the cascade. Pyright net-zero per touched file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 15:28:59 +00:00
Khalim Conn-Kowlessar
433f4a49ce Slice S0380.99: PCDB Table 329 (MV In-Use Factors) ETL + parser + lookup (PCDF Spec §A.20)
PCDF Spec Rev 6b §A.20 (May 2021) Format 430 — Mechanical Ventilation
In-Use Factors Table. Pcdb10.dat carries Format 432 (header
`$329,432,4,2021,11,25,2`), an extended-field version where Format
430 fields 1-4 (system_type + 3 SFP factors for the "no approved
scheme" variant) align at positions 0..3. The remainder of Format
432 carries MVHR adjustments + "with approved scheme" variants +
additional Format 432 columns, preserved verbatim in `raw` for
follow-up slices.

Per PCDF Spec §A.20 field 1 — system types:
  1  = centralised MEV
  2  = decentralised MEV
  3  = balanced whole-house MV (with or without heat recovery)
  5  = positive input ventilation (PIV)
  10 = default data (used with SAP Table 4g defaults)

Decentralised MEV (system_type=2) IUFs:
  SFP × ducting type:
    flexible:   1.45 (field 2)
    rigid:      1.30 (field 3)
    no-duct:    1.15 (field 4 — through-wall fans)

Per spec Note: "If there is no applicable approved installation
scheme the values for with and without scheme are the same." Cert
000565 lodges "Approved Installation: No" → use the "no scheme"
IUFs.

Validation for cert 000565 against worksheet line (230a):
  Σ(SFP_j × FR_j × IUF_j) for the 4 lodged fans:
    in-room kitchen:        1×0.15×13×1.45 = 2.8275
    in-room other wet:      1×0.15× 8×1.45 = 1.7400
    through-wall kitchen:   2×0.11×13×1.15 = 3.2890
    through-wall other wet: 3×0.14× 8×1.15 = 3.8640
  Σ = 11.7205 W (matches worksheet "total watage = 11.7205")
  Σ(FR_j) = 92.0 l/s (matches worksheet "total flow = 92.0000")
  SFPav = 11.7205 / 92.0 = 0.1274 W/(l/s) ✓ matches worksheet

Foundation only this slice — typed parser + ETL + runtime lookup
`mv_in_use_factors_record(system_type)`. No cascade integration; no
behavioural change on any cert. Next slice S0380.100 wires the
SFPav formula.

5 Table 329 records ingested. Pyright net-zero per touched file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 15:20:02 +00:00
Khalim Conn-Kowlessar
b3330821e7 Slice S0380.98: PCDB Table 322 (Decentralised MEV) ETL + parser + lookup (PCDF Spec §A.19)
PCDF Spec Rev 6b §A.19 (May 2021) Format 427 — Decentralised MEV
Systems Table. Pcdb10.dat carries the per-fan-configuration block in
Format 428 (header `$322,428,72,...`), which drops the spec's per-
group "Fan speed setting" string. Each group is a 3-field triplet:
(config_code, flow_l_per_s, sfp_w_per_l_per_s).

Per the spec § field 14, the 6 fan configurations are:
  1 = In-room fan, kitchen
  2 = In-room fan, other wet room
  3 = In-duct fan, kitchen
  4 = In-duct fan, other wet room
  5 = Through-wall fan, kitchen
  6 = Through-wall fan, other wet room

Some configurations may be blank per spec Note 1 — these are not
valid SAP selections and are excluded from the SFPav summation
downstream.

This slice lands the foundation only — typed parser, ETL promotion
to typed write, and a runtime lookup `decentralised_mev_record(pcdb_
id)`. No cascade integration yet → no behavioural change on any
cert; full test suite + cert 000565 expected fails unchanged.

Subsequent slices in the arc:
- S0380.99: PCDB Table 329 (In-Use Factors) ETL + lookup
- S0380.100: SAP 10.2 §2.6.4 SFPav cascade helper
- S0380.101: HP SAP code 211-227 / 521-527 → main_heating_category=4
- S0380.102: wire MEV cascade into pumps_fans

Cert 000565 lodges `MV PCDF Reference Number = 500755` (Titon
Ultimate dMEV), resolving via this lookup to:
  config 1 (in-room kitchen):     flow=13.0, SFP=0.15 W/(l/s)
  config 2 (in-room other wet):   flow=8.0,  SFP=0.15
  config 3 (in-duct kitchen):     not tested
  config 4 (in-duct other wet):   not tested
  config 5 (thru-wall kitchen):   flow=13.0, SFP=0.11
  config 6 (thru-wall other wet): flow=8.0,  SFP=0.14

48 Table 322 records ingested. Pyright net-zero per touched file.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 15:12:55 +00:00
Khalim Conn-Kowlessar
25f3af9eba docs: handover + next-agent prompt post S0380.91..95 (party-wall + AP4/MEV + §5.14 floor + RIR insulation + Detailed-RR residual) 2026-05-30 14:26:49 +00:00
Khalim Conn-Kowlessar
fa6974bdd9 Slice S0380.95: Detailed-RR residual area cascade per RdSAP 10 §3.10.1
RdSAP 10 §3.10.1 (PDF p.24) "Default U-values of the roof rooms":

> "The residual area (area of roof less the floor area of room(s)-in-
>  roof) has a U-value from Table 16 : Roof U-values when loft
>  insulation thickness is known according to its insulation thickness
>  if at least half the area concerned is accessible, otherwise it is
>  the default for the age band of the original property or extension."

Plus RdSAP 10 §3.9.1 step (d-e) (PDF p.21-22) — the Simplified A_RR
formula `12.5 × √(A_RR_floor / 1.5)` is the empirical estimator for
the total RR exposed shell; residual = A_RR − Σ lodged walls. The
worksheet applies this same formula to Detailed mode when the lodged
surface set has no roof-going entries (cert 000565 BP[0]:
12.5 × √(45/1.5) − (9.8 + 14.7) = 43.96 ≈ ws 43.97).

Pre-slice the cascade computed residual area ONLY in the Simplified
RR branch (via `_part_geometry`'s `rr_simplified_a_rr_m2` − rr_common
− rr_gable subtractions). The Detailed-RR branch in
`heat_transmission` iterated `rir.detailed_surfaces` and missed the
residual entirely. Cert 000565 routes all 5 BPs through Detailed mode
(the Elmhurst mapper translates Summary "Simplified" lodgements to
`SapRoomInRoofSurface` records when per-surface L×H is present), so
cascade total_external_element_area_m2 was 779.27 m² vs worksheet
(31) = 857.64 m² (Δ −78.37 m² → thermal_bridging cascade −11.76 W/K
under).

Slice span (1 file):
- `heat_transmission.py`: Detailed-RR branch adds residual area via
  the §3.9.1 A_RR formula minus wall-going lodgements (gable_wall,
  gable_wall_external, common_wall). Residual area contributes to
  `rr_detailed_area` (→ part_external_area → (31) → thermal_bridging
  multiplier) and to `roof` at `u_rr_default_all_elements`.
- Discriminator: residual fires only when no roof-going surface kinds
  (slope, flat_ceiling, stud_wall) are lodged — true Detailed-mode
  lodgements (cohort fixture 000516) lodge the entire roof shell
  explicitly and have no residual.

Cert 000565 movement (HEAD `78c57c0d` → this slice):
  - thermal_bridging_w_per_k:    116.89 → 129.35 ✓ vs ws 128.65 (Δ +0.70)
  - total_external_area_m2:      779.27 → 862.34 ✓ vs ws 857.64 (Δ +4.70)
  - roof_w_per_k:                34.64  → 63.72 (Δ −16.74 → +12.34)
  - sap_score_continuous:        29.02  → 28.07 (Δ +0.51 → −0.44)
  - sap_score (integer):         29 → 28        (temp regression
                                                  past 28.5 threshold)
  - space_heating_kwh:           −685   → +533
  - main_heating_fuel:           −403   → +321
  - hot_water_kwh:               ✓ 0 EXACT unchanged

Per user direction temporary continuous-SAP drift is acceptable when
fixing real spec-correct sub-component bugs; the absolute continuous-
SAP residual is now −0.44 (was +0.51) — slightly closer to zero
overall. The roof overshoot localises to:
  - BP[4] Flat Ceiling 1 "Unknown PUR or PIR" lodgement (cascade 2.30
    vs ws 0.15, over by +10.75 W/K) — Elmhurst-specific "Unknown +
    known material" convention not yet wired
  - BP[1] residual formula gives +3.68 m² over worksheet (Δ +1.29 W/K)
    — Detailed-mode residual is spec-ambiguous for extensions with
    non-2.45 m RR height; future slice may add a height-aware formula

Cohort safety: discriminator `has_roof_lodgement` filters out true
Detailed-mode lodgements (cohort fixtures 000474/000477/000480/
000487/000490/000516 all lodge slope/flat_ceiling/stud_wall surfaces).
Initial implementation broke 41 cohort pins; the discriminator
restores cohort behaviour exactly. Test baseline: 585 pass + 9
expected `000565` fails (was 585 + 8 — sap_score moved from passing
to failing during the slice's transient overshoot; expected per
user direction).

Pyright net-zero per touched file (test_summary_pdf_mapper_chain.py
13 → 13 preserved; heat_transmission.py 13 → 12 improved by −1).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 14:21:59 +00:00
Khalim Conn-Kowlessar
78c57c0dc7 Slice S0380.94: RIR insulation "400+ mm PUR or PIR" extractor + mapper + cascade (RdSAP 10 Table 17 col 3b)
RdSAP 10 §5.11.3 + Table 17 (PDF p.42-43) "Roof room U-values when
insulation thickness is known". Column (3b) "Stud wall — PUR or PIR
optional" 400 mm row → 0.10 W/m²K. Cert 000565 Summary §8.1 BP[2] Ext2
(Detailed) lodges:

  Stud Wall 2  2.00 × 2.00   400+ mm   PUR or PIR   Default U=0.10

Pre-slice three coupled bugs silently dropped the lodgement, routing
the cascade through the uninsulated Table 17 row 0 (U=2.30) — over-
counting Stud Wall 2 by (2.30 − 0.10) × 4 m² = +8.80 W/K on roof:

1. **Extractor regex** `_RIR_INSULATION_THICKNESS_RE = ^\d+\s*mm$`
   failed to match the "400+ mm" bucket-cap form (Table 17's largest
   tabulated row is annotated with a trailing "+" in the Summary).
2. **Extractor insulation_type allow-list** `("Mineral or EPS",
   "PUR", "PIR")` failed to match the disjunction "PUR or PIR" — the
   actual Summary form when the assessor doesn't distinguish PUR from
   PIR. (Both columns Table 17 column (b) anyway.)
3. **Mapper thickness parser** `_elmhurst_rir_insulation_thickness_mm`
   used the same `^\d+\s*mm$` regex — also failed on "400+ mm".

Plus a fourth coupled fix: the cascade's `_is_rigid_foam` checked a
frozenset `{"pur", "pir", "rigid"}` that didn't include the canonical
mapper-side code "rigid_foam" — even if the mapper translated "PUR or
PIR" → "rigid_foam", the cascade would route to column (a) mineral-
wool instead of column (b) rigid-foam.

Slice span (4 layers):
1. **Extractor regex** — `^\d+\+?\s*mm$` matches both "100 mm" and
   "400+ mm".
2. **Extractor allow-list** — add "PUR or PIR" alongside individual
   "PUR" / "PIR" + "Mineral or EPS".
3. **Mapper** — `_RIR_INSULATION_TYPE_TO_SAP10` canonicalises all
   rigid-foam strings to "rigid_foam"; thickness parser regex matches
   "400+ mm" → 400 mm int.
4. **Cascade** — `_RR_RIGID_FOAM_INSULATION_TYPES` adds "rigid_foam"
   alongside the legacy "pur"/"pir"/"rigid" aliases.

Cert 000565 movement (HEAD `23aaa4fa` → this slice):
  - cascade BP[2] Ext2 Stud Wall 2 U:  2.30 → 0.10 ✓ EXACT vs ws 0.10
  - cascade roof_w_per_k:              43.44 → 34.64 (Δ−7.94 → Δ−16.74)
  - sap_score:                         29 ✓ EXACT unchanged
  - sap_score_continuous:              28.81 → 29.02 (Δ+0.26 → Δ+0.51)
  - space_heating_kwh:                 −427 → −685
  - main_heating_fuel:                 −251 → −403
  - hot_water_kwh:                     ✓ 0 EXACT unchanged

Closing one spec-correct sub-component while others remain non-spec-
correct drifts continuous SAP further; per user direction temporary
drift is acceptable as long as we're fixing true intermediate-value
problems — once every sub-component is spec-correct, the continuous
SAP error closes to zero by construction. The remaining −16.74 W/K
roof gap localises to:
  - BP[0/1/3] missing RR residual area for Detailed-RR mode (§3.10.1
    spec — cascade only handles Simplified mode today); +27.85 W/K
    closure when wired.
  - BP[4] Flat Ceiling 1 lodges "Unknown thickness, PUR or PIR" → ws
    U=0.15; cascade over-counts at 2.30 (uninsulated). Elmhurst's
    "Unknown PUR or PIR" → 200 mm convention is non-spec; the spec-
    correct path falls back to Table 18 col 4 default (`u_rr_default
    _all_elements`). Separate diagnostic slice.

Cohort safety: 21 other Elmhurst Summary fixtures lodge no RIR detailed
surfaces with "400+ mm" or "PUR or PIR" (modal cohort uses As Built /
None / no detailed surfaces). Existing "Mineral or EPS" tests at
`test_u_rr_stud_wall_table17_col3a_mineral_wool_100mm_returns_0_36`
remain green — the new aliases extend rather than replace.

Test baseline: 585 pass + 8 expected `000565` fails (was 583 + 8; +2
new tests). Pyright net-zero per touched file (0/32/1/65/13 preserved).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-30 14:08:05 +00:00