# Tool Shed campaign reconciliation — 2026-08-14

Status: complete
Type: evidence
Updated: 2026-08-14
Next Action: none; follow `work/00-campaigns/active-queue.md`
Parent: work/00-campaigns/completed/007-audit-and-reconcile-unqueued-incomplete-work-campaigns.md
Canonical Truth: README.md, docs/, direct source/test/build/runtime evidence, and work/00-campaigns/active-queue.md

## Outcome

Root `work/` was reviewed by artifact substance and lifecycle state, not only
by filename or the generated index's narrow active count. Every campaign-level
incomplete outcome is now represented by an owner campaign request. Supporting
maps, inventories, templates, runbooks, and historical evidence remain linked
to those campaigns without being duplicated as owner outcomes.

No source, build, deployment, controller, power, SD-card, USB-drive,
controlled-document, publication, or Marshal mutation was performed. Existing
unrelated worktree changes were preserved.

## Evidence reviewed

- Root README and the current `docs/` front doors.
- `work/maps/map-smi-firmware-stabilization-and-qualification.md`.
- Both incomplete execution checklists and all eight active workpackages.
- The one active firmware ticket, two explicitly deferred temperature
  workpackages, active inventories, reusable runbooks, and the SSP/HCD spike.
- The accepted Aug. 10 and nine-campaign administrative closeout evidence.
- Current owner queue status and every lifecycle request under
  `work/00-campaigns/`.

## Campaign-level disposition manifest

| Artifact or outcome | Evidence-backed disposition | Owner campaign(s) | Blocker / dependency |
| --- | --- | --- | --- |
| Bounded HPT export latency ticket | Incomplete; existing request retained | 003 | 002, then owner latency-budget and later target authority |
| USB VBUS adapter regeneration gate | Incomplete; new active request, explicitly blocked | 008 | separate clean-regeneration/build authorization; depends 002 |
| Controller-neutral A/B execution workpackage | Gate 2/start work retained; physical completion added | 005, 006, 009 | exact bundle, plan, and per-operation physical authority |
| HPT2 bounded-stop/recovery checklist | Incomplete; clean-campaign execution added | 009 | depends 006; no historical-credit synthesis or command replay |
| Firmware code-review mitigation workpackage | Firmware complete, target evidence open; new request | 010 | depends 009; exact negative/recovery authorizations |
| Degraded SD operation workpackage | Firmware complete, target/media evidence open; new request | 011 | depends 010; protected fault/power procedures |
| Independent HPT validator workpackage | Software release integrated, physical proof open; new request | 012 | depends 009; expendable card, reader, powered-off transfer, read-only authority |
| Triple-mirrored circular HPT workpackage | Initial release qualification open; new closeout request | 013 | depends 009–012 and exact first-family evidence |
| Accelerated endurance/media workpackage | Current pair, initial release, and retail breadth remain | 009, 013, 015 | staged physical/sample gates; no specimen-specific production behavior |
| Standalone Pi SD Qualifier application | Gate 2/start retained; defining end-to-end acceptance added | 005, 006, 014 | 014 depends 013 and requires disconnected-runtime proof |
| SD supply-change closeout checklist | Gates 1–4 mapped to ordered chain; ECO/rollout closeout added | 002–006, 009–016 | controlled-document and external rollout authority remains stage-specific |
| Temperature-control profile recovery workpackage | Incomplete but owner-deferred; active blocked request records the gate | 017 | all currently open SMI workpackages, including 008 and 016, must close |
| RTD validity/interlock workpackage | Incomplete but owner-deferred; active blocked request records the gate | 018 | 017 plus explicit owner approval of the RTD-only contract |

## Supporting and historical artifact dispositions

| Surface | Disposition | Campaign relationship |
| --- | --- | --- |
| SD qualification current-state inventory | Marked complete as a historical Aug. 13 snapshot after all stale campaigns became terminal | Superseded for execution by the owner queue |
| SSP 2.7/USBX/HCD research spike | Marked complete with `Disposition: no-action`; reopen only on explicit authority plus contradictory evidence | No active campaign; 008 is only the already-implemented adapter regeneration proof |
| Version-5 FAT32-to-HPT inventory | Active supporting cleanup inventory, not an independent owner outcome | 011 and 013 |
| SD qualification candidate inventory | Waiting supporting intake inventory, not an independent owner outcome | 015 |
| Current Setup B inventory | Dynamic connected-bench identity evidence, not an independent outcome | 009–013 as applicable |
| Project map | Active coordination surface; header redirected to the owner queue | All campaigns |
| Marshal reconciliation runbook | Active reusable procedure, not unfinished project delivery | 016 only after workspace closeout |
| Controller-test checklist templates | Retained as non-ready execution contracts, not duplicate outcomes | 010 and 011 |
| Evidence files with partial or historical status prose | Preserved as evidence; they cannot independently reopen or close work | Their parent campaigns/workpackages |

## Reviewed execution order

After this audit closes, the dependency-safe owner order is:

1. 002 checkpoints the reconciled planning/evidence baseline.
2. 008 is a short independent closeout placed after that checkpoint but remains
   blocked; the queue may continue to 003 while authorization is absent.
3. 003–006 correct and freeze firmware, establish Gate 2, and start one clean
   contract-bound campaign.
4. 009 completes that clean A/B campaign before separate destructive or
   negative qualification expands target risk.
5. 010 and 011 finish firmware-negative/recovery and degraded-SD evidence.
6. 012 performs independent read-only media validation after campaign closeout
   permits a controlled powered-off card transfer.
7. 013 closes the HPT media 2.0 initial release using all prerequisite evidence.
8. 014 proves the standalone application journey; 015 expands the rolling
   retail pool; 016 performs the ECR/ECO rollout and project closeout.
9. 017 and 018 remain blocked at the tail, preserving their explicit owner
   deferral and RTD contract-approval gates.

The order intentionally separates production firmware success from
qualification evidence, keeps powered SD-card handling prohibited, and avoids
allowing the independent VBUS gate to halt the SD critical path while it lacks
authorization.

## Verification

- Campaign lifecycle mutations used fresh state tokens and the deterministic
  queue script.
- New requests contain explicit completion gates, dependencies, authority
  boundaries, and primary artifact links.
- Queue validation, index regeneration, stale-path review, work-state review,
  and whitespace checks are required after lifecycle completion.
