junte/Model
1
0
Fork 0
mirror of https://github.com/Hestia-Homes/Model.git synced 2026-07-27 23:35:01 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

PasHub SAP accuracy: refresh 5 Paxton fixture to the current V5 (MEV) re-survey 🟩

Browse source 
5 Paxton Place (deal 507639151845, uprn 10070864419) had a STALE fixture.
The same PAS Hub survey (report B74AA5A4-…, inspected 29 Jun 2026) has two
accredited revisions in S3: V2 (uploaded 6 Jul, ventilation "Natural",
SAP 80) and V5 (uploaded 14–15 Jul, ventilation "Mechanical Extract -
Centralised", SAP 76 — the current version). Our committed fixture was the
superseded V2; the portfolio-838 oracle tracks the latest V5 (76). Our
engine faithfully reproduces BOTH (V2 → 80.4, V5 → 75.6) — the +4.38 miss
vs the DB oracle was a fixture-version mismatch, NOT an engine over-rate
(a parallel over-credit sweep found no spec-correct from_site_notes lever;
every channel is faithful).

Refreshed the fixture to the V5 PDF (image-stripped, text layer preserved,
6.7MB→0.27MB, per scripts/build_pashub_accuracy_fixtures.py) and set the
manifest to C76. 5 Paxton flips from the cohort's largest miss to a
within-0.5 hit: DB-oracle gauge 86.9%→87.4% within-0.5, MAE 0.348→0.327.
Pinned via test_paxton_fixture_is_v5_resurvey_sap_76 (asserts a literal 76
against the V5 fixture) — a canary, because hubspot_deal_data.pre_sap is
still stale at C80 and a fixture-builder rerun would revert the manifest.

Confirmed against pashub: the current survey is SAP 76 (Khalim).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Khalim Conn-Kowlessar 2026-07-15 22:29:14 +00:00
parent d3f36d78ac
commit 6c4f73cc91
3 changed files with 24 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
backend/documents_parser/tests/fixtures/pashub_accuracy/507639151845.pdf vendored
View file

Binary file not shown.

4
backend/documents_parser/tests/fixtures/pashub_accuracy/manifest.json vendored
View file

@ -1091,8 +1091,8 @@
{
"deal_id": "507639151845",
"uprn": null,
"pre_sap_raw": "C80",
"pre_sap_score": 80,
"pre_sap_raw": "C76",
"pre_sap_score": 76,
"pdf": "507639151845.pdf"
},
{

22
backend/documents_parser/tests/test_pashub_sap_accuracy.py
View file

@ -344,3 +344,25 @@ def test_walsden_pins_to_pashub_resurvey_sap_64() -> None:
f"13 Walsden SAP {outcome.sap_continuous:.2f} diverged from the PAS Hub "
"re-survey's own accredited 64 (NOT the colliding 24-Jun cert's 68)"
)
@pytest.mark.skipif(not _FIXTURES, reason="no pashub_accuracy fixtures/manifest")
def test_paxton_fixture_is_v5_resurvey_sap_76() -> None:
"""5 Paxton Place (deal 507639151845, uprn 10070864419) was RE-ISSUED: the
same PAS Hub survey (inspected 29 May/Jun 2026, report B74AA5A4-…) has two
accredited revisions — V2 (ventilation "Natural", SAP 80) and V5 (ventilation
"Mechanical Extract - Centralised", SAP 76, the current version). The
portfolio-838 oracle tracks the latest revision (76), so the fixture is
refreshed to the V5 PDF (2026-07-15e); our engine reproduces its accredited 76
(~75.6). Do NOT revert this fixture/manifest to the V2 SAP-80 version.
CAVEAT: `hubspot_deal_data.pre_sap` for this deal is still stale at "C80", so a
`scripts/build_pashub_accuracy_fixtures.py` rerun would regenerate the manifest
`pre_sap` back to 80 — this pin (asserting a literal 76 against the V5 fixture)
is the canary. Confirmed against pashub: April survey → SAP 76 (Khalim)."""
outcome = _evaluate("507639151845")
assert outcome.sap_continuous is not None
assert abs(outcome.sap_continuous - 76) < 0.5, (
f"5 Paxton SAP {outcome.sap_continuous:.2f} diverged from the current V5 "
"(MEV) re-survey's accredited 76 — has the fixture reverted to the V2 "
"(Natural, SAP 80) PDF?"
)