# SD qualifier matrix-status projection deployment — 2026-08-07

Status: deployed and verified; Controller A qualification chain uninterrupted
Type: evidence
Updated: 2026-08-07
Next Action: let the persistent Controller A chain continue from exact S4 44640 / AT observation 2 of 3; keep Controller B qualification 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/wp/active/wp-build-standalone-pi-sd-qualification-operator-application.md

## Result

The bounded-stop measurement card now reports the actual matrix adjudication
instead of presenting the base classifier's
`BOUNDED_STOP_PASS_CASE_TRIGGER_NOT_MET` terminal code as the operator-facing
result. Completed S4 observations whose extended evidence is valid are shown as
`CREDITED`; the admitted run is shown as `RUNNING`. Each row identifies the
boundary, observation ordinal, counters, checkpoint, short run ID, and evidence
ID. The card also distinguishes the 32 current-campaign runs from 69 earlier
Engineering attempts.

This corrects a presentation defect, not a qualification failure or repeated
command replay. The extended S4 adjudication had credited the completed runs,
but the status card displayed the lower-level terminal code and mixed historical
runs into its attempt total.

## Source and release identity

- SD Qualifier PR #45, `Clarify credited matrix run status`, merged as
  `24f31db5e0577873aac87bda926b110c60a0c887`.
- SD Qualifier PR #46, `Humanize historical matrix actions`, merged as
  `5b0f4dda6f53f83a0dca411264ec0fbf0da911cd`.
- Deployed exact ARM64 image:
  `sha256:b032bd3b6a6158b213970f5d51d40f20fe1c18dfe2aab54ec65f0854afe71b37`.
- Production web container after deployment:
  `8537ffffbb0992bb180a33e59d8b99bba6631114d427f7c1f5a687f061cd7446`.

The change was delivered through reviewable pull requests. Production received
only a web-service image replacement; no migration, database write, evidence
rewrite, command-worker restart, qualification-service restart, or controller
operation was part of this deployment.

## Verification

- The exact merged image passed all `258/258` tests and the Django system check.
- `/sd-qualifier/healthz` returned `status: ok`; database, storage, clock, and
  worker checks were healthy.
- An authenticated render against the production database returned HTTP 200,
  contained no instance of `BOUNDED_STOP_PASS_CASE_TRIGGER_NOT_MET`, and showed
  four completed observations as `CREDITED` plus the active observation as
  `RUNNING`.
- The five newest rows were S4 44640/AT observation 2 running, S4 44640/AT
  observation 1 credited, and S4 44640/BEFORE observations 3, 2, and 1 credited.
- The rendered scope text was: `Showing the 5 newest of 32 current-campaign
  runs. Earlier Engineering attempt history: 69 runs.`

No connected in-app browser instance was available for screenshot-level visual
inspection. The authenticated production render, template assertions, static
style rules, exact-image tests, and live health checks provide the deployment
verification recorded here.

## Qualification continuity

The command worker retained container ID `4e08d8b81ffc`; the notification worker
retained container ID `b7610271cd99`. The active
`sdq-controller-a-s4-matrix-v3.service` retained PID `1798217` and its original
2026-08-06 start time. After the web deployment, S4 44640/AT observation 2 had
advanced to attempted `39604`, committed `39604`, verified `39603`, checkpoint
`3`, with reason `0`. Controller B remains outside the admitted qualification
chain.
