# Project Map: SMI 00-05-01 Transition Floor And Controlled Return

Status: active
Type: project-map
Updated: 2026-09-22
Source Idea: IDEA-0007
Technical Source: IDEA-0006
Requested Endpoint: work1 for SMI source; later physical and release endpoints require fresh direction
Next Action: review the SMI source candidate and select exact transition images; retain the bench pause
Campaign: standalone

## Outcome

Deliver a safe SMI 00-05-01 update floor, a direct controlled SMI rollback, and a safe return to revised DisplayTest. Preserve normal DisplayTest FAT32 handoff and explicit SMI HPT2 initialization. Qualify all transitions on both controller assemblies before any release decision.

## Direction and boundaries

1. Use the validated format-1 IMX header Title for family and numeric release identity, with MachineMask, layout, header CRC, and payload CRC as existing independent checks. USB filenames are discovery labels only. Ordinary update rejects older or unknown personality images before any QSPI erase.
2. Keep direct service rollback separate from ordinary update. Admit any valid SMI image without a version allowlist. SMI 00-05-00 or later needs no FAT32 conversion; a pre-00-05-00 FAT32-era release needs staged full-image validation and explicit in-place FAT32 preparation, history disposition, data-loss consent, CID recheck, media verification, and staged-image revalidation before internal-flash replacement.
3. Preserve service 471 as explicit HPT2 reinitialization if current SMI remains bootable and its UI usable after a pre-flash stop. Do not promise recovery after internal-flash replacement starts.
4. The DisplayTest 01-01 or later image belongs to its own project-bound lane. It must boot safely with HPT2 media, enforce its 01-01 fixture-to-fixture floor, and verify FAT32 for normal production handoff. After that FAT32 handoff its updater may install a valid older SMI personality; the 00-05-01 ordinary personality floor belongs to SMI while HPT2 media may remain. DisplayTest 01-00 is below the SMI return floor.
5. CVO and DVO have separate build and proof lanes. This SMI project cannot claim those delivered.

## Execution sequence

- Establish exact controlled IMX identities and current source behavior. Implement the SMI normal floor and verify deterministic negative cases, including a renamed valid file.
- Implement the explicit service rollback for any valid SMI image and FAT32 preparation for pre-00-05-00 images. Keep all media mutations outside the ordinary update path.
- Reconcile the separate DisplayTest lane against its own project authority and image evidence.
- After the owner resumes bench transition testing, capture baseline and post-change CID identity and prove forward, return, refusal, rollback, and failure recovery on A and B.
- Reconcile evidence and make a separate release decision. This map does not authorize programming, formatting, push, or release.

## Readiness gates

- G-APPROVED-IMAGES: select exact DisplayTest 01-01 or later and representative SMI release specimens with hashes and media requirements for qualification; these do not form production allowlists.
- G-SMI-CANDIDATE: implement and verify the SMI floor, separate any-valid-SMI rollback, preparation, retention, CID, and recovery behavior at the authorized endpoint.
- G-DISPLAYTEST-RETURN: prove revised DisplayTest safe HPT2 startup, 01-01 fixture-to-fixture floor, verified FAT32 production handoff, and legacy SMI admission only after that handoff in its own project lane.
- G-DUAL-CONTROLLER-TRANSITION: after the owner resumes bench work, collect CID-bound transition and fault evidence on A and B before release.

## Current limits

The owner has paused bench transition testing. The owner clarified that service rollback accepts any valid SMI image and DisplayTest return requires 01-01 or later. The published DisplayTest `01-00` release tests and initializes HPT2 media for production, so it does not meet this directive's FAT32 production handoff and is below the return floor. Select exact qualification specimens before physical testing; no image-version allowlist is required for software implementation. Incomplete gates stay open and visible.

## 2026-09-21 source checkpoint

The SMI source version is now 00-05-01. The ordinary update path parses family and two consistent numeric version spellings from the CRC-checked Title, checks the 00-05-01 personality floor and DisplayTest 01-01 return floor, and refuses malformed, unknown, or older identities before the first install QSPI erase. It does not use the USB filename as identity. Service code 151 now selects a distinct any-valid-SMI rollback path. A pre-00-05-00 image is fully staged before the SD owner rechecks CID and representative sector, prepares FAT32 in place, and lets USB recheck the staged CRCs before internal-flash replacement. The managed Release rebuild and subsequent incremental build pass; the existing 16-case firmware-update negative corpus and 15 code-review checks pass. This is a source candidate only; parser, SD preparation, fault recovery, and A/B transitions lack target evidence. No controller programming or SD operation occurred.

## 2026-09-22 source review

The legacy service branch now checks read-only SD preparation eligibility before the first QSPI erase, then checks again after staging when it requests the SD owner operation. The SD worker keeps FAT32 media unavailable to HPT logging until the older firmware takes over. Service-code consent text states that data loss is conditional on a pre-00-05-00 image. The managed Release rebuild and final incremental build pass; the existing 16-case update corpus and 15 review checks pass. The checked-in 00-05-00 IMX header has the expected controlled Title, format-1 layout, and four-MiB main/audio payloads. There is still no target evidence for the DisplayTest return, FAT32 failure/recovery boundary, or A/B transitions; no controller or card action occurred.

Read-only review of the separate DisplayTest 01-01 source found no personality version floor in `src/DisplayTestUpdateAdmission.h`, a 01-01 fixture-to-fixture minimum, and FAT32 handoff before personality installation. Its project record reports Controller B FAT32 handoff and installation of SMI 00-04-11, after a power cycle following an initially unresponsive install tap; old SMI logging remains unproven. The earlier reciprocal-floor requirement conflicted with that media-state design and is superseded above. This does not satisfy the SMI A/B return or rollback gates, and the SMI bench pause remains in force.
