# Controller A HPT2 S0-S3 observed-boundary matrix pass

Status: pass for Controller A S0-S3 strict observed-boundary matrix; S4-S6, recovery, regression, Controller B, and deadline review remain open
Type: evidence
Updated: 2026-08-05
Next Action: implement and software-qualify distinct S4-S6 evidence paths before any further Controller A target execution; keep Controller B untouched and 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

Controller A completed the strict S0-S3 bounded-stop matrix on the exact
candidate. The durable append-only ledger contains 35 current run
adjudications and 35 measurement results. Supplemental adjudications take
precedence over, but do not alter, the five preserved erroneous planned-S3
classifications identified in the predecessor correction artifact.

Current observed contributions are:

| Case | Required | Observed | Result |
| --- | ---: | ---: | --- |
| S0 | 3 | 3 | pass |
| S1 | 10 | 12 | pass |
| S2 | 10 | 11 | pass |
| S3 | 10 | 12 | pass |
| S4 | distinct checkpoint-region evidence | 0 | not implemented |
| S5 | 10 contention observations | 0 | not implemented |
| S6 | at least 10 including both variants | 0 | not implemented |

Every credited run was classified from the exact pre-Stop status capture and
clean terminal status by Pi commit
`3fdd4c929f21eb05b90f0e2da206e763985a5699`. Planned labels and
qualification-only phase offsets supplied no credit. Runs whose observed
boundary differed were retained as bounded-stop passes with the planned case
rejected, then credited only to the proven boundary.

The largest current Stop-publication-to-terminal-observation upper bound is
`2089 ms`. This is measurement evidence, not a production deadline.
`stop_deadline_ms` remains `null` until the complete A/B matrix, recovery,
representative regression, and firmware-owner review pass.

## Closing observations

The final S1 minimum was closed by run
`4e82b82b-affc-4553-a280-79e150ec973c`, Result/Adjudication Evidence
`556`/`557`. The final S2 minimum was closed by run
`d75d3f8e-4eb0-4e0a-ae4e-d3a67e2d7d7b`, Evidence `640`/`641`; the
immediately following run `80c23eb7-baa2-4512-b578-21377385cb76`, Evidence
`654`/`655`, supplied an additional S2 observation. Their adjudication
SHA-256 values are
`4e9ebc74ae7ec0000a45819ca91e9553ca1ebf7178f156fd2c88cd7fd433bf86`,
`49d90ba05dcd775c593794286497c1ae6e3fbea24658bc5f19f4c3729d6323ce`,
and `17e37e7e8540e228bc413b3cf9e083d8256bd36162addd42d62cf16a472dde42`.

Ambiguous Start outputs caused by concurrent firmware seqlock publication
were never replayed. The harness queried the durable operation state and used
separate read-only reconciliation until the existing command was proven
acknowledged; only then was its Stop prepared.

## Frozen identity

- Campaign: `7f13c433-e904-4320-a0d1-33d503057f69`.
- Controller/sample: A / `F1-A1`; Controller B remained untouched.
- Bundle: `smi-00-05-00-52edddc39e30-054d5386ad9d-release`.
- Bundle manifest SHA-256:
  `e2561cdd82b6e1fc69585b2149d27f3bf3ca2690df5e5a2fc6356dd825c2e638`.
- Complete code-flash SHA-256:
  `862b8122c0c8c9556508130927cc9960e91fc0a2bc4aea5f8d7b457ba4cd7efe`.
- Boot-session witness: `DEE10A12EC443248`.
- Protocol/card status: `DETECTION_READY; RAW_HPT; DRIVER_OK`.
- CID valid / representative-sector read valid: true / 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`.

No card movement, power operation, physical intervention, or Controller B
access occurred. At checkpoint there were zero active runs and zero prepared,
publishing, or reconciliation-required HPT2 operations. The default firewall
dropped non-loopback ports `19120` and `19121`, and no HPT2 tool container
remained.
