# Executive Directive: Deliver a safe SMI 00-05-01 update floor while preserving a return path to revised DisplayTest and the FAT32 production handoff. Prove the transition on both controller assemblies before release.

Status: promoted
Type: idea-brief
Role: project-executive-directive-v1
Updated: 2026-09-22
Next Action: keep bench work paused; when the owner explicitly resumes it, diagnose the Controller A final internal-flash replacement using candidate 00.05.01-10dbb9151938-4e7dfb2f7333 before restarting the transition matrix
Readiness Review: READY-WITH-PRM-GATES at revision 3; four gates transferred to MAP-0009
Produces: MAP-0009

## CEO Directive

Deliver a safe SMI 00-05-01 update floor while preserving a return path to revised DisplayTest and the FAT32 production handoff. Prove the transition on both controller assemblies before release.

## Desired Outcome

Use IDEA-0006 as the technical scope and decision record. Deliver an SMI 00-05-01 candidate whose validated IMX Title governs family/version identity and whose ordinary updater refuses pre-00-05-01 personality images before QSPI erase. Provide a separate direct service rollback to any valid SMI image without a version allowlist. For any admitted FAT32 target, validate and stage the image before explicit target-media preparation: retain verified FAT32, format another readable classified layout after data-loss consent, and stop on missing or unreadable media; service 471 remains the HPT2 recovery action if current SMI survives a pre-flash failure. Preserve an SMI return path to DisplayTest 01-01 or later that safely handles HPT2 media and then verifies FAT32 handoff. DisplayTest may install a valid older SMI personality after that FAT32 handoff; its fixture-to-fixture minimum is 01-01. Keep SMI's HPT2 initialization explicit. Require transition, refusal, and rollback evidence on both controller assemblies before release.

## Current Position

The owner confirmed that SMI 00-05-00 was never deployed on a production controller and excluded it from target qualification. Controller A accepted and exactly staged candidate `00.05.01-22a3205bae13-da6887348e38`, but internal flash remained the previously installed candidate; the final transition cause is unresolved. The card remained readable FAT32, uninitialized, and CID-stable. The owner then added target-driven FAT32 preparation and disabled-chart requirements, superseding that candidate. Commit `10dbb91519384cc9144b94e8a79057c8f47c0630` contains the revised source and deterministic build outputs. Clean Debug and Release rebuilds passed and reproduced those bytes. Replacement immutable candidate `00.05.01-10dbb9151938-4e7dfb2f7333` validates against its source commit. Bench work remains paused.

## Progress

- [x] Directive captured exactly in canonical project state.
- [x] Codex has delegated the directive into a bounded plan and execution chain (MAP-0009).
- [ ] The requested outcome has evidence and is reconciled.

Only check a milestone when canonical lifecycle state or linked evidence supports it. Codex updates
this section as work moves; the generated `work/100k.md` never guesses progress.

## Recommended Next Action

Keep all controller work paused. When the owner explicitly resumes bench testing, validate the exact replacement candidate boundary and diagnose the Controller A internal-flash replacement before restarting the transition matrix.

## Why This Next

The revised source closes the owner-specified media and UI requirements and now has an immutable replacement candidate. The first Controller A ordinary update staged QSPI without replacing internal flash, so that transition boundary must be diagnosed before more transition scoring.

## Blockers

- Controller A staged the selected IMX in QSPI but did not replace internal flash; the cause is unresolved.
- Bench testing is paused until the owner explicitly resumes it.
- DisplayTest 01-01 still needs its separate controlled IMX identity and A/B return qualification.
- The SMI A/B transition, HPT2 initialization, logging, retention, export, and representative rollback gates remain open.

## Operator Needs

- No operator action is pending while bench testing is paused. After an explicit resume, follow one bench instruction at a time for the Controller A transition diagnosis.

## Completion Condition

The SMI and DisplayTest implementation and release identities satisfy IDEA-0006; both controller assemblies pass the forward, return, renamed-file, ordinary legacy-refusal, and representative direct rollback matrix; in-place FAT32 preparation, service-471 recovery, and retention safeguards are verified; the resulting release decision is evidence-backed and reconciled to this directive.

## Authority And Delivery Boundary

- Preserve any endpoint, target, timing, non-goal, or authority language stated in the directive.
- Initial CEO intake does not authorize code, build, programming, SD preparation, bench testing, push, or release. Subordinate source-changing work defaults to a verified Work1 candidate until a later delivery endpoint is authorized.
- The owner's latest 2026-09-22 clarification explicitly authorizes replacing the installed DVO firmware with SMI on Controller A and Controller B. Pre-program CID is recorded unavailable because DVO lacks service 467; post-program CID evidence is mandatory.
- The service rollback is explicit and accepts any structurally valid SMI image, with no version allowlist. Do not treat the ordinary floor as a ban on controlled recovery or treat common internal-flash failure risk as unique to downgrading. Do not require field SD-card replacement.
- Interrupt only for a genuine material decision or authority boundary.

## Delegation Contract

Initial issuance is durable intake only. Tool Shed appends this Idea through canonical planning
order, checkpoints it, and stops so other directives may be captured first. Reissuing the exact
active directive delegates or resumes it when doing so will not preempt another working campaign.

The Plan Cycle interprets this directive, the Roadmap Cycle organizes it when needed, the Milestone
Cycle materializes bounded campaigns, Campaign Cycles execute, and Evidence/Outcome Cycles report
the result back to 100k. The CEO is not required to select those internal mechanics.

## Exploration Log

### 2026-09-21

- The owner accepted the recommended CEO framing from the IDEA-0006 discussion. Preserve that brief as the technical source and keep this directive as the executive outcome.
- The owner directed IDEA-0006 and this CEO directive to include direct service rollback to approved older SMI firmware and in-place FAT32 preparation. Service 471 is the existing explicit HPT2 recovery action when current SMI remains bootable.
- The owner later clarified that service rollback accepts any valid SMI image, and corrected the DisplayTest normal return floor to 01-01 or later. The earlier named-image questions are superseded; exact images remain qualification specimens.

### 2026-09-22

- Read-only review of the separate DisplayTest 01-01 source found FAT32 handoff before personality installation, no DisplayTest personality version floor, and a 01-01 fixture-to-fixture minimum. Its project record reports a Controller B transition to SMI 00-04-11 after FAT32 handoff, with an initially unresponsive install tap requiring a power cycle; old SMI logging remains unproven. The SMI ordinary 00-05-01 floor and DisplayTest return floor are distinct. SMI A/B target qualification and this project's bench pause remain open.
- Owner designated Controller A as the initial target control for the SMI 00-05-01 transition work. Controller B remains the second required release-qualification assembly. The designation does not itself resume bench work or authorize a target operation.
- Source review removed the late-format false-failure timeout and made the read-only USB media flush informational after staged CRC verification. Release rebuild, 16 update cases, and 15 review checks pass; target fault behavior is still open. SMI 00-05-00 and 00-04-11 specimens are identified by controlled hashes, while 00-05-01 and DisplayTest 01-01 IMX candidate bytes remain pending. A newer DisplayTest Controller B record demonstrates new SMI 00-04-11 FAT32 records in a five-minute export; post-restart retention was not checked.

### 2026-09-22 direct 00-05-01 updater correction

- The owner confirmed that 00-05-00 was never deployed on a production controller and excluded it from this qualification. A deterministic host-built 00-05-01 IMX now provides the correct SMI QSPI resources directly, so the next target step uses Settings > Update Firmware and does not install the 00-05-00 development image.

### 2026-09-22 Controller A result and owner requirements detour

- Controller A Settings > Update Firmware listed and accepted `7520553_SMI_00_05_01.imx`. QSPI main and audio matched the selected image, but internal flash remained the prior candidate. CID `05000C61736466672200001C8901A34F`, representative-sector validity, FAT32 classification, and operational configuration remained stable. The final flash-transition cause is unresolved.
- The owner required target-driven FAT32 preparation: retain verified FAT32; format another readable classified layout only when the admitted target requires FAT32; stop on missing or unreadable media. The owner also required the main chart to use its gray disabled appearance whenever logging is unavailable.
- The revised SMI source implements those requirements. Twenty-four identity/media cases, thirteen FAT32 transaction checks, sixteen update cases, main-chart availability checks, both canonical builds, and related review/warning/USB/FileX checks pass. Commit `10dbb91519384cc9144b94e8a79057c8f47c0630` was rebuilt cleanly and reproduced the committed bytes. Immutable candidate `00.05.01-10dbb9151938-4e7dfb2f7333` contains Release S-record SHA-256 `4E7DFB2F7333202C71A736DF6692512030DB43508A1CCD0C556E7E8C1EB6B326`; manifest SHA-256 is `6F753689C56EFACE054C802FF782FFCC193BFAE2D7F5E948F0BE20F44FA86586`. No controller programming or SD formatting occurred during the detour or freeze.
