Jun-te Kim b9f1f428b9 test(accuracy): corpus-1000 campaign ledger + C001 4510053280 pinned 75 (lodged-software PSR gap) ... Setup for the RdSAP-21.0.1 corpus gauge campaign (74.2% within-0.5, SAP MAE 0.721 at HEAD, 1000/1000 computed): - scripts/corpus_1000/build_worklist.py — runs all 1000 corpus certs through the gauge's own path (from_api_response -> Sap10Calculator), ranks |engine - lodged| descending, clusters by dwelling signature, and (re)writes scripts/corpus_1000/worklist.md preserving per-cert statuses and notes. 258 certs outside 0.5 in 249 clusters. - C001 (worst cert, Δ +23.9): uprn 4510053280, ground-floor flat 47 m² on ASHP PCDB 100053 (Mitsubishi Ecodan 5 kW, PSR table 0.2-2.0). Dwelling PSR 2.031 -> SAP 10.2 N2 footnotes 44/45 heat-pump extension (reciprocal interpolation toward 100% at 2x largest PSR) = 305% space efficiency, which accredited Elmhurst also applies (golden case 56, record 100061). The LODGED software instead treated the out-of-range record as invalid and billed 100% direct electric + standard schedule (reproduces lodged CO2 to 1%). Lodged-software methodology gap, worklist ⚠, engine untouched; observed engine 75 pinned in test_real_cert_sap_accuracy. Gauge floors unchanged (no engine change). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-02 18:28:20 +00:00
..
json_samples	test(accuracy): corpus-1000 campaign ledger + C001 4510053280 pinned 75 (lodged-software PSR gap)	2026-07-02 18:28:20 +00:00
api_spec.md	adding hacky handling for matching on lmk key or uprn	2026-04-09 14:47:54 +01:00