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

Status: active
Type: project-map
Updated: 2026-09-21
Source Idea: IDEA-0007
Technical Source: IDEA-0006
Requested Endpoint: work1 for SMI source; later physical and release endpoints require fresh direction
Next Action: implement and verify the SMI normal updater floor while identifying exact approved rollback and DisplayTest images
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 only named approved released older SMI images. SMI 00-05-00 needs no FAT32 conversion; a named 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 revised DisplayTest image belongs to its own project-bound lane. It must boot safely with HPT2 media, enforce the reciprocal normal update floor, and retain FAT32 for normal production handoff.
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 and FAT32 preparation only when the approved older image set is named. 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: name exact revised DisplayTest and approved older SMI release images with media requirements and acceptance specimens.
- G-SMI-CANDIDATE: implement and verify the SMI floor, separate named rollback, preparation, retention, CID, and recovery behavior at the authorized endpoint.
- G-DISPLAYTEST-RETURN: prove revised DisplayTest safe HPT2 startup, reciprocal normal floor, and FAT32 production 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 revised DisplayTest release and older SMI rollback image set are not named. Software implementation may proceed only where those identities are unnecessary; incomplete gates stay open and visible.
