# Controller B S0 observation 2 — 2026-08-09

Status: PASS; second Controller B S0 observation credited while Controller A remained healthy
Type: evidence
Updated: 2026-08-09
Next Action: require a new operator continuation before separately admitting Controller B S0 observation 3 of 3
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
Project Map: work/maps/map-smi-firmware-stabilization-and-qualification.md

## Admission and preservation gate

The owner instruction `continue` authorized the next separately gated
Controller B measurement. The traveler and database showed one credited S0
observation, no active B run, no unresolved B operation, and the exact next
case S0 observation 2 of 3. Controller A was `RUNNING` and `HEALTHY`; the
parallelization base gate had no blocker.

Pre-admission database backup
`/home/jong/.local/share/sd-qualifier/backups/sd-qualifier-20260809T235711Z.dump`
is `604860` bytes with SHA-256
`80720701d4bb7547c530290b7c2c9788009e71d62f3a83be0c4cdfc68b9a3378`.
A disposable PostgreSQL 17 restore passed with `105` runs, `1980` evidence
rows, and `209` HPT2 command operations; the disposable container and network
were removed and verified absent.

Read-only admission created run
`e7eb0d5f-4dc7-42fe-b7fe-1c6bca515ba7`. Its source identity evidence is
`1989`, SHA-256
`e2389f19185db7a2c5b5109d60919a7fcc87413d53da10b19d9e59d6b4a65d06`.

Admission CID identity block:

- Protocol card status: `READY; RAW_HPT; DRIVER_OK`.
- CID valid: true.
- Representative-sector read: true.
- Manufacturer: unknown CID manufacturer; retail brand KEXIN; MID `0x05`.
- OEM/application ID: raw `0x000C`.
- Product name: `asdfg`.
- Product revision: `2.2`.
- Serial number: `7298`.
- Manufacturing date: `2026-03`.
- Complete raw 128-bit CID: `05000C61736466672200001C8201A379`.

The boot witness remained `F54F10127F443248`, and bundle manifest remained
`d5da9437a9498b3ca82f6ee418dde82332159db463d51a1ef7a120abf29162fe`.
There was no card replacement, power-off reinsertion, initialization, or reboot
between observations. No powered card removal or insertion occurred. CID is
identity evidence, not proof of authenticity.

## Authorization and execution

The existing reviewed matrix envelope
`5ef65727-8279-4cfa-88ca-979acc5393b2` remained unexpired and exactly bound to
Controller B, F1-B1, the immutable firmware bundle, stable non-heating state,
and later target access. Fresh machine authorization `211` created only Start
operation `4a4c0c7f-17bd-48bc-a61b-1e83ee1ef581`, initially `PREPARED` with
no target access. Generic policy blocked the existing Start while the exact
prepared-operation recheck returned `CONTROLLER_B_EXECUTION_ALLOWED` against
three fresh healthy A snapshots.

The command-scoped B firewall rule then enclosed one same-session S0 sequence:

- Start `4a4c0c7f-17bd-48bc-a61b-1e83ee1ef581`, sequence `3`, publish sequence
  `6`, mailbox SHA-256
  `52c0af1b925625f479bdc51bd3806b6d6934c92804e317d1b72ee821cc37b579`.
- Stop `250f1372-3a99-4ae4-826d-4a66303f8c74`, sequence `4`, publish sequence
  `8`, mailbox SHA-256
  `eaf652c9bcf703c57327035ee1e919079b95cccb9ec75f1f4db83f248db04d6a`.
- Shared request `0a126394-2b8c-44cf-9045-43f8fa34de10`.
- Both operations are `ACKNOWLEDGED`, terminal code
  `MAILBOX_COMMAND_ACKNOWLEDGED`, with automatic replay disabled.
- Same-session evidence `2000`, SHA-256
  `0903a39be118f71a28ac4c4f32a0bfaaabddd3f37ee37809e596d3836c911fc8`,
  recorded `0 ms` from Start acknowledgement to Stop publication.

Stopped-clean observations `2002` and `2003` retained the exact CID/boot
identity, state `5`, terminal reason `0`, and terminal proof `31`. Their hashes
are `9e03a2cb24103efba6dc4ed1c7f4eb190e33f8358b3631d309ef42a0549093f3`
and `c89ac30f319c934d001bf4a95274c6c7f7c9c50792604de4cb985524a52ef3ae`.

Measurement evidence `2004`, SHA-256
`dfe592e345bba48059b3a76039566b1c3ed49c684f3869852a756f20f18e031d`,
classified S0 `CASE_PASS`, bounded-stop pass, with a `2134 ms` Stop-to-terminal
upper bound. Adjudication evidence `2005`, SHA-256
`02851519a8116475a58317395e76cb7d73d09c4d0f352cdc5aa16fb7704498ea`,
credits the planned S0 and observed S3 contribution.

## Final guards

The traveler reports `S0 — observation 2 of 3`, `CREDITED`. Controller A run
`de340af2-d505-495e-a14f-5159e55b1633` remained `RUNNING` and `HEALTHY`; its
post-operation snapshot is
`7cb4fcdaa74657bb95f846a0f5e4a978ba3907b46a4a21fac2560d7cf2c3c669`.
Web health and the user observer pass. No B firewall allowance remains; at rest
only the persistent A `19120` allowance and default `{19120,19121}` drop rule
exist. There is no unresolved Controller B operation.
