# Controller A S4 44640 / BEFORE live checkpoint — 2026-08-06

Status: active run healthy at checkpoint; persistent A-only qualification chain continues
Type: evidence
Updated: 2026-08-06
Next Action: let the persistent Controller A chain complete without replay or interruption; keep Controller B disabled and not started
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

## Checkpoint scope

This is a read-only checkpoint captured at `2026-08-07T00:19:18Z`
(`2026-08-06 17:19:18 PDT`). It records the durable run identity, live
measurement progress, service continuity, SD-card identity, Controller B
isolation, and repository coordination state. It did not issue a controller
command, stop a service, change a firewall rule, or manipulate either SD card.

## Active campaign and run

- Campaign: `648ba10c-0bc0-4319-8089-78a0cce287ce`, `RUNNING`, version `6`.
- Campaign name: `KEXIN 8GB HPT S4 exact-boundary Controller A qualification
  2026-08-06`.
- Physical sample/controller: `F1-A1` / Controller A.
- Run: `b58be682-69cd-4982-b3bf-8f78972458a3`, `RUNNING`.
- Measurement: S4, target `44640`, region `BEFORE`, measurement-only.
- Latest read-only status: attempted `13778`, committed `13778`, verified
  `13777`, checkpoint `3`, reason `0`, state `2` at elapsed `5068` seconds.
- Target progress at capture: `13778 / 44640` (`30.9%`).
- Boot-session witness: `26B10B1280443248`.
- Source evidence: Evidence `1542`, SHA-256
  `43b74fe40e2cb2e579d601426b478e089f6bd07fe4c8184b22f15436b6c6a1c0`.

The one-shot START operation
`0bde2c9b-b29e-47f3-ae8e-8047de45d424` is `ACKNOWLEDGED` with machine
authorization `198` and authorization envelope
`3f8f2f98-a2dc-4245-be6f-e0318f6fc0b9`. Automatic START, STOP, and resume
replay remain disabled. No STOP operation exists for this active run because
the target has not yet been reached.

The current run has one logged `transient-status-observation-retry`, at elapsed
`1613` seconds. This is the designed retry of an unstable read-only status
observation; it did not replay START or issue STOP. The latest observation is
stable and the run continues to advance.

## Required CID identity block

- Protocol/card status: `DETECTION_READY; RAW_HPT; DRIVER_OK`.
- CID-valid status: true.
- Representative-sector-read status: true.
- Manufacturer: unknown CID manufacturer; retail brand KEXIN; MID `0x05`.
- OEM/application ID: decoded `??`; raw CID OID bytes `0x000C`.
- Product name: `asdfg`.
- Product revision: `2.2`.
- Serial number: `7305` (`0x00001C89`).
- Manufacturing date: `2026-03`.
- Complete raw 128-bit CID: `05000C61736466672200001C8901A34F`.
- Capture: CardIdentityCapture `115`, reason
  `HPT2_S4_MEASUREMENT_PREFLIGHT`, at `2026-08-06T22:54:38.143685Z`.

CID is identity evidence, not proof of authenticity.

## Continuity and isolation

All four persistent user services reported `active/running`, result `success`,
and main status `0`:

1. `sdq-controller-a-s4-matrix-v3.service`;
2. `sdq-controller-a-after-ordinary.service`;
3. `sdq-controller-a-final-after.service`; and
4. `sdq-controller-a-after-final.service`.

The database contained exactly one active qualification run, the Controller A
run above. Controller B assignment `18`, physical sample `F1-B1`, remains
`INTAKE` / `PENDING` with no active run. A read between polling operations
showed the default non-loopback firewall drop for both TCP `19120` and `19121`
and no temporary accept rule. Controller B was not contacted.

The mutable runner log remains outside version control at
`/home/jong/.local/share/sd-qualifier/controller-a-s4/matrix.log`; this evidence
records only its small checkpoint summary rather than copying generated raw
output into Git.
