# Controller A HPT2 S5 runtime evidence first pass — 2026-08-05

Status: pass; first Controller A S5 observation retained, superseded by the 10/10 matrix pass
Type: evidence
Updated: 2026-08-05
Next Action: none; use work/evidence/controller-a-hpt2-s5-runtime-matrix-pass-20260805.md for current S5 disposition
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
Canonical Truth: docs/hpt2-measurement-matrix-v1.md

## Result

Superseding result: the remaining nine observations passed and Controller A S5
is now `10/10`. See
`work/evidence/controller-a-hpt2-s5-runtime-matrix-pass-20260805.md`.

One separately admitted Controller A/F1-A1 S5 run completed with immutable,
map-bound baseline and terminal runtime snapshots. The extended adjudicator
credited production-queue contention from two queued and two completed normal
log records, with zero queue drops, zero HPT store loss, and an empty queue at
both boundaries. The run reached `STOPPED_CLEAN`, terminal reason `0`, terminal
proof `0x1F`, and a `2023 ms` Stop-to-terminal observation upper bound.

The ordinary counter-boundary adjudicator also recorded the actual S2 boundary
shape and correctly did not infer S5 from the planned label. S5 credit comes
only from the separate controller-runtime adjudication required by the selected
contract.

Live audit after the run reports Controller A S0 `3/3`, S1 `12/10`, S2
`12/10`, S3 `12/10`, S5 `1/10`, and S4/S6 zero. The A-local gate remains false,
Controller B remains disabled and untouched, the matrix remains incomplete,
and `stop_deadline_ms` remains `null`.

## Parser correction and exact deployment

The first baseline attempt stopped before target access because the exact GNU
Release map represents section-owned `gHptQualification` without a redundant
standalone symbol line. Pi commit
`6dc1c3caf69859df2f6a7c9dc3997a369ba61fb4` accepts that valid exact-map form
while still requiring a unique exact `.bss.<symbol>` section, address, size,
and owning object. Duplicate resolution fails closed. The firmware image,
bundle, mapping, profile, controller flash, CID, and boot session did not
change.

- Pi release: `hpt2-runtime-map-6dc1c3c`.
- Image: `sha256:b550a9a5dd9907105a14f364d48ab3f56be4c8f9b36168c1317b1e7e13b52fce`.
- Release manifest SHA-256:
  `9fe871abfcf8f54c7e8615af3e12047a395d84261fce5afcb68430851b38bbd3`.
- Exact-image tests: `212/212` passed in `46.097 s`.
- Backup: `/backups/sd-qualifier-20260805T223251Z.dump`; restore check,
  migration, storage preflight, package hashes, web health, both workers,
  firewall isolation, and residual-tool checks passed.
- Exact firmware bundle:
  `smi-00-05-00-52edddc39e30-054d5386ad9d-release`.
- Exact map SHA-256:
  `ca774f3fd897487ab41161b161bdecd83fffc3146db9347074f815e1620b0dc4`.

## Run identity and no-replay record

- Run: `0703f83e-16a9-4ea2-9022-f337a5937f00`, final database state
  `COMPLETED`.
- Controller A CID: `05000C61736466672200001C8901A34F`.
- Boot-session witness: `DEE10A12EC443248`.
- Start operation: `23750b8a-5a7d-45cd-9974-9db3d5ce6130`.
- Stop operation: `32a225fa-431e-42fe-a02e-534cb6817e7c`.

Each mailbox intent was published once. The Start publication ended with an
unstable seqlock capture after the write; the exact operation then reconciled
read-only to `ACKNOWLEDGED`. It was not replayed. Stop likewise reached
`ACKNOWLEDGED` without a second publication. Two stable stopped-clean snapshots
were captured after Stop.

## Immutable evidence

- Baseline runtime Evidence `658`, SHA-256
  `b78c73658326d5274c0765b6566e9dfc2ba8203dd09c0c1ede4f0bd6cf9b5f67`.
- Terminal status Evidence `667` and `668`, SHA-256
  `e33c0aaec9ac73c8a697e2cd78813a067ebf8ed8adfb80c1ca12bc52cb535fd4`
  and `83ac1d08cf5a8e14b09cc9e25f621c6508a5ec85c79fb90e2d316b7b60255587`.
- Terminal runtime Evidence `669`, SHA-256
  `8612183b5da7891360dce4fc8474b31edb945fc83dd6f434dcef149703e8e382`.
- Bounded-stop result Evidence `670`, SHA-256
  `89531d5c3a841687928e908dc9e672cd93ec3c4bffe585d3d04a1b7080cc8f42`.
- Base boundary adjudication Evidence `671`, SHA-256
  `99c00a8cc19897273494966d496ab21484109980661042cec0c3a6ee9473dd27`.
- S5 extended adjudication Evidence `672`, SHA-256
  `44e4e8eefd79d42021497132d48e301d97f0f5bb624413f591aeb31f1914096b`.

The postflight check found no active run or controller tool container. The
default non-loopback firewall drop for ports `19120` and `19121` is restored.
