# Controller A HPT2 observed-case classifier correction

Status: partial-pass; append-only classification correction deployed and Controller A S0-S3 matrix in progress
Type: evidence
Updated: 2026-08-05
Next Action: continue Controller A until the strict observed-boundary S1-S3 minimums pass, then implement and execute the distinct S4-S6 evidence paths; keep the production deadline unset
Campaign Reason: Historical record from campaign 009-complete-clean-contract-bound-a-b-qualification; retained independently after campaign closure and requires no separate owner-queue execution.
Campaign: standalone
Parent: work/checklists/checklist-hpt2-bounded-stop-recovery-and-regression-measurement.md

## Result

The Pi coordinator formerly accepted the planned case label for every non-S0
bounded-stop pass even when the immutable pre-Stop status capture proved a
different boundary. Five runs planned as S3 actually captured three S1 and two
S2 boundaries. The original evidence remains immutable; supplemental Evidence
`273`-`277` now supersedes only the erroneous case classifications.

Pi commit `3fdd4c929f21eb05b90f0e2da206e763985a5699` derives case credit solely
from the exact pre-Stop and terminal status. It accepts S1 only when attempted
exceeds committed by one, S2 only when committed exceeds verified by one, and
S3 only when all three counters are equal. S0 still requires the zero boundary
and also contributes S3. S4-S6 remain uncredited until their distinct evidence
is implemented and observed.

The exact image passed `72/72` focused and `194/194` full tests. Release
`hpt2-observed-case-classifier-3fdd4c9`, image
`sha256:c03e252157fc2df4b71f207e7f1bf4f637008fb06387fec7d55b3655d8486dd0`,
was deployed healthy after database backup/restore and storage preflight. The
release-package manifest SHA-256 is
`17e77a32267a2e49eb64e09b2bde40f6b46aa27da5c13e120d92f756acb894ee`;
every packaged checksum passed. The change is pushed to draft Pi PR `#32`.

## Append-only corrections

| Run | Prior evidence | Supplemental evidence | Correct contribution |
| --- | ---: | ---: | --- |
| `3a687315-62b4-49fc-8900-38b17d3b6bed` | 216 | 273 | S2 |
| `dcb77d7b-839f-413d-a0e0-482d5d2565d0` | 230 | 274 | S1 |
| `15264069-d612-435c-aae1-927f7b49e42d` | 244 | 275 | S1 |
| `b864850f-5de7-4e95-a182-aee81393939b` | 258 | 276 | S1 |
| `aedf7d2b-91bb-424a-ba77-26f3578a459b` | 272 | 277 | S2 |

The supplemental SHA-256 values are, in row order,
`149d4fbf61e0124f80cb1f4dc351e206f2cef5867c139e78423a533ac7a073ea`,
`8ba7eb8cce07caff8de462eb55fde089268984f2979963058b02d2f156a362b1`,
`64419a061fd17273a2310a510b38030bed1576c1ba5f72e52a500e91ed75c973`,
`edd445f5e1f78e057c76538191cea8065e0f40fa45cc23cb7ec8d0c5d229c297`,
and `aa970bf8cb640e0d0869c5bd7574d61fd29842c1e5de08603cc46e9270d5edbc`.

## Strict-classifier continuation

Four subsequent runs used one immutable Start and Stop each and two stable
terminal observations:

| Run | Planned / observed | Result / adjudication evidence | Result |
| --- | --- | --- | --- |
| `b9e7c349-62f3-4e3e-8623-46be037552c2` | S1 / S3 | 290 / 291 | bounded Stop pass; planned case rejected; S3 credited |
| `5704d10a-6367-42fb-8d15-2aa160c5b38b` | S1 / S3 | 304 / 305 | bounded Stop pass; planned case rejected; S3 credited |
| `fbc8a14a-eceb-43d2-9149-b804b1bd78e2` | S1 / S1 | 318 / 319 | `CASE_PASS`; S1 credited |
| `4ef5ae85-b7ba-44c0-bc2a-28d6ad8ddb2f` | S2 / S2 | 332 / 333 | `CASE_PASS`; S2 credited |

Run `4ef5ae85...ddb2f` returned an ambiguous Start result because status changed
inside a seqlock capture. Operation `e87885c0-4c86-4b85-a528-2f242a1571c0`
was not replayed; a distinct read-only reconciliation proved the existing Start
acknowledged before Stop was prepared.

Current strict Controller A totals are S0 `3/3`, S1 `4/10`, S2 `3/10`, and S3
`5/10`; S4-S6 are `0` because their case-specific evidence paths do not yet
exist. This supersedes the current-count interpretation in
`controller-a-hpt2-s0-matrix-pass-20260805.md` without changing that artifact's
immutable S0 run evidence.

## Identity and cleanup

- Protocol/card status: `DETECTION_READY; RAW_HPT; DRIVER_OK`.
- CID-valid status: true.
- Representative-sector-read status: true.
- Manufacturer/MID: unknown CID manufacturer, retail brand KEXIN; `0x05`.
- OEM/application ID: `0x000C`.
- Product/revision: `asdfg`, `2.2`.
- Serial/manufacturing date: `7305` (`0x00001C89`), 2026-03.
- Complete raw 128-bit CID: `05000C61736466672200001C8901A34F`.
- Boot-session witness: `DEE10A12EC443248`.

No card movement, power manipulation, or Controller B access occurred. After
every one-shot operation the default firewall again dropped non-loopback access
to ports `19120` and `19121`, and no HPT2 adapter tool container remained.
Production `stop_deadline_ms` remains `null`.
