# Project Map: SMI firmware stabilization and qualification

Status: active
Type: project-map
Updated: 2026-09-08
Requested Endpoint: work3
Next Action: complete the Work3 validation/build gate and freeze the reconciled local candidate
Campaign: standalone

## Desired outcome

Freeze a locally coherent SMI firmware candidate whose implemented filesystem, logging,
export, configuration, and qualification behavior agrees with the current documentation and
whose applicable static checks and managed Debug and Release builds pass. Keep production
promotion and external qualification as explicit Work5 obligations instead of hiding them in
this Work3 outcome.

Remote setpoint release integration is a separate development cycle and is tracked by its own
project map. It may share the eventual Work5 batch, but it is not merged into this map's Work3
scope.

## Current evidence and incident disposition

- Controller B read-only evidence on 2026-09-08 identifies the installed card as
  `035344535330384780977F00850185AB` and records a successful guarded whole-card HPT
  initialization. The status object does not retain the initiating actor or command source, so
  it proves the initialization occurred but cannot prove whether it originated at the HMI,
  service command, or qualification automation.
- The current graph cache and export retained bound both start at HPT timestamp `305619300`.
  A bounded graph-RAM extraction contains no older real record. The photographed earlier-data
  display was therefore stale graph RAM around the media-generation change, not recoverable
  data on the current initialized HPT generation.
- Qualification media intended for production logging must be restored through an explicit,
  approved production-media initialization after qualification, with power-off replacement
  rules and before/after CID evidence. That destructive operation is not performed by Work3.

## Work3 gates

| Gate | Completion evidence |
| --- | --- |
| Scope and documentation | Current behavior, incident disposition, exclusions, and successor obligations are explicit. |
| Graph/export evidence | Current Controller B CID, initialization status, cache bounds, and graph data CSV are captured read-only. |
| Static validation | Every applicable repository `script/check-*.ps1` suite passes. |
| Managed builds | Canonical managed Debug and Release rebuilds pass and artifact hashes are recorded. |
| Freeze | Intended changes and generated firmware artifacts are frozen in one local commit without push or release. |

## Transfer after Work3

The following remain real work, but are deliberately transferred rather than represented as
unfinished Work3:

1. Work5 production promotion and verification of every eligible awaiting candidate in the
   active release cohort, including this candidate and the separate remote-setpoint candidate.
2. Exact combined-candidate qualification on the required controllers and external SD Qualifier
   evidence where the release contract requires it.
3. Explicit restoration/reinitialization of any qualification SD card selected for production
   use, with the controller powered off for removal/insertion and complete CID identity evidence.

## Excluded or separately activated work

- Temperature-profile and RTD-sensor development cycles are not part of this Work3 or the
  automatic Work5 batch unless separately activated.
- No hardware programming, destructive media action, powered SD removal/insertion, push,
  production release, ECO, or rollout is authorized by this map.
