# Start clean contract-bound SD Qualification campaign

Status: complete
Type: campaign
Updated: 2026-08-17
Next Action: none
Campaign ID: 006-start-clean-contract-bound-sd-qualification-campaign
Campaign Number: 006
Outcome: Create and start one clean qualification campaign from the normal website, bound to immutable firmware, plan, fixtures, controller roles, and SD-card identities.
Primary Focus Areas: sd-qualifier-app
Supporting Focus Areas: smi-firmware, hpt-media-logging, usb-host-publication, controller-automation, power-fault-control, qualification-release
Depends On: 005-complete-sd-qualifier-gate2-release-plan-acceptance
Decision: none
Detour For: none
Return To: none
Completion Gate: The campaign records immutable identifiers and CID traceability, both controller roles are ready, required physical authorization is obtained, and the durable start produces no replay or duplicate execution.
Completion Evidence: work/evidence/campaign-006-clean-contract-bound-preexecution-checkpoint-20260817.md
Completion Date: 2026-08-17
Completion Order: 7
Disposition: completed

## Request Context

Priority: 5
Target: `http://srv-rpi00.local/sd-qualifier/`
Repository Coordination: local Tool Shed in `E:\dev\high_point\7520553_SMI_FW`
Coordination: coordinated
Parent: `work/checklists/checklist-sd-card-supply-change-project-closeout.md`

## Goal

Using the normal authenticated website workflow, create and start one clean SD
qualification campaign bound to the exact frozen corrected firmware bundle,
`SMI-SDQ-CONTRACT-V1`, and the accepted immutable
`CARD_FAMILY_INITIAL` plan. Do not reuse or synthesize historical campaign
credit.

## Dependency gate

Require request `005` to have a documented Gate 2 `GO`, with exact SDQ release,
image, migration, backup/rollback, contract, plan, firmware-bundle, and fixture
identities. Recheck appliance health, zero open campaigns, execution
quiescence, controller-role isolation, and protected runner readiness. Any
identity drift is a `NO-GO`, not permission to patch live code during campaign
creation.

## Required work

1. Use a normal authorized operator through the website; do not create or
   manipulate the campaign through ad hoc shell/database operations.
2. Select the exact admitted firmware bundle and accepted plan. Record campaign
   ID/version and frozen firmware, contract, plan, controller, probe/endpoint,
   power-channel, sample, and evidence-policy identities.
3. Enter complete traceability for each intended eligible sample. Capture and
   bind the required service-467 or equivalent CID identity block at baseline:
   protocol/card status, CID-valid and representative-read status, decoded MID,
   manufacturer, OEM/application ID, product, revision, serial, manufacturing
   date, and raw 128-bit CID. Record `CID unavailable` plus the reason if it
   cannot be obtained.
4. Prove Controller A and B are independently ready and that neither lane waits
   for the other except for a recorded genuine shared-system/safety condition.
5. Review the complete campaign preflight and exact first runnable leaves. Do
   not admit old campaign rows as completion credit.
6. Starting this queue item authorizes campaign creation, identity capture, and
   read-only readiness/preflight work. Before the first firmware-programming,
   controller-power, destructive-media, or other consequential physical
   operation, obtain explicit operator authorization naming the exact operation,
   target role, firmware bundle, samples, and safety state.
7. After that authorization, use the website's high-level Run action to place
   the clean campaign into its intended controlled execution state. Stop after
   confirming durable campaign/lane state, no command replay, and truthful UI
   progress; completing the full qualification is later campaign work.

## Safety and evidence rules

- Never remove or insert an SD card while its controller is powered. Card
  replacement requires controller power off, followed by boot-time
  classification and a new CID capture.
- Do not use hidden SSH-selected test cases or raw browser-supplied controller
  commands. The UI sends only high-level durable actions.
- Do not reject a card or conclude qualification merely because campaign start
  is blocked or inconclusive.
- Preserve every campaign event and evidence artifact; do not overwrite the 11
  terminal historical campaigns.

## Completion gate

Complete when one clean campaign exists with immutable identities and complete
baseline traceability, both role readiness results are truthful, the operator
has explicitly authorized any consequential first operation, and the campaign
has durably entered the intended controlled start state without replay or
coding changes. If physical authorization is not provided, leave the campaign
at the safe pre-execution gate and keep this queue item unchecked.
