# Executive Directive: diaganose and resolve format error after fresh smi install.

Status: promoted
Type: idea-brief
Role: project-executive-directive-v1
Updated: 2026-09-30
Next Action: finish and qualify the generation-recovery correction on A and B using one exact 00.05.02 candidate under MAP-0010
Readiness Review: performed by the receiving Plan Cycle; ask the CEO only about material ambiguity
Produces: MAP-0010

## CEO Directive

diaganose and resolve format error after fresh smi install.

## Desired Outcome

After a fresh SMI firmware installation, SD-card initialization/formatting should complete on the first attempt and leave a usable HPT log store. Diagnose the observed first-attempt failure, correct its proven cause in the common firmware path, and retain enough failure detail to distinguish media I/O from invalid metadata on any future occurrence.

## Current Position

The owner reproduced the first-format failure on two controllers with different SD cards running the latest GitHub release, v00.05.01. The second format succeeded in the same powered session, without card removal or intervening diagnostics. The first screenshot under `work/01-q&a/` reports failure during "commissioned-media reopen": media status 0x05 and SD driver 0x00000000. The second screenshot reports success. These captures establish the symptom, not its root cause.

Source trace: `initializeHptWholeCard()` completes format, formatted-media reopen, and the three-lane commissioning append before the failing reopen (`src/Thread_SdCard_entry.c`). Status 0x05 is HPT_STATUS_CORRUPT. `HptTripleCircularOpenQualification()` can return CORRUPT for invalid metadata or some failed reads (`src/HptTripleCircular.c`). The adapter resets its displayed last SSP status after a successful read, and the legacy probe can obscure the original failure (`src/HptLogStoreRenesas.c`, `src/HptLogStoreQualification.c`). No service 467/468 or CID was captured before the original successful retry; the later diagnostic-candidate reproduction below resolves that evidence gap for Controller A. This incident overrides historical first-pass success claims for this release.

Candidate `b7f9cd9fda8b` embeds 00.05.02 and preserves the first SD read error/sector and reopen stage/lane. Canonical clean Debug and Release rebuilds and focused source checks passed. Both approved, expendable controller cards received that exact Release image, retained their baseline CIDs and readable sectors, and each completed a Format 2 request without retry while already HPT formatted. That did not test the fresh FAT32 condition.

The owner authorized using the same cards through an ordinary SMI-to-DisplayTest-to-SMI transition. Controller A reported success for both updates. Read-only flash identity verified the published DisplayTest image and then the exact diagnostic SMI 00.05.02 return image, while the same CID remained valid and readable. The expected `SD card not Format 2` message appeared after SMI installation. Its first CID-bound Format 2 request from FAT32 was acknowledged and **failed at commissioned-media reopen** with HPT status CORRUPT (5), driver status zero, and open stage DIRECTORY (6), lane 0. Deep RAM capture found media generation 1 with old segment-1 generation-2 metadata accepted in all three lanes; directory rebuild failed. No retry was sent. Source inspection identified that format read only sector 0 for the prior generation even though FAT32 overwrote it and old HPT segment metadata survived. Commit `f51d98e7` reads both superblock copies and surviving initial segment metadata before choosing a strictly greater generation. Its clean Debug and Release builds are in progress. Physical correction qualification and B's fresh FAT32 sequence remain open. Physical evidence: `work/evidence/hpt-log-store-circular-mirror/00-05-02-preflash-20260930/baseline.md` and linked captures.

## Progress

- [x] Directive captured exactly in canonical project state.
- [x] Codex has delegated the directive into a bounded plan and execution chain.
- [ ] 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

Finish the corrected 00.05.02 candidate and verify A's first Format 2 against the preserved failed card. Recreate FAT32 on the same card, then qualify first-attempt success on A and B with CID and terminal status evidence. Complete graph qualification and release gates on one frozen image.

## Why This Next

The reproduced first failure identifies a generation collision with surviving HPT metadata. The correction must still prove first-attempt success after FAT32 preparation on both approved controls before the release can be qualified.

## Blockers

- Corrected candidate builds and physical first-format qualification remain open. Graph touch behavior and shared 00.05.02 release gates also remain open.

## Operator Needs

- None for the source build; coordinate ordinary controller update steps when the corrected image is ready.

## Shared Release Target

The owner assigned both this directive and the other active SMI defect directive to the next firmware release, 00.05.02 (controller display 00-05-02; GitHub release tag v00.05.02). The currently published baseline is v00.05.01. Format diagnosis and correction (IDEA-0009) has planning priority 1; graph zoom correction (IDEA-0008) has priority 2. Build and qualify one exact 00.05.02 candidate containing both verified fixes. Record its source commit, embedded version, image filename, artifact hashes, and controller evidence. Completion requires that both fixes appear in the same qualified and published 00.05.02 image, followed by release verification. A candidate or a passing build alone does not satisfy the release outcome.
## Completion Condition

- Reproduce or isolate the first-attempt failure with the exact v00.05.01 format/commission/reopen sequence. Preserve failing phase, first SD error and sector, and which superblock, retirement snapshot, checkpoint, or lane-header check rejected the store; do not infer card damage from 0x05 alone.
- Identify a supported root cause and implement the smallest general correction. Preserve fail-closed behavior for actual transport errors, invalid metadata, and incomplete commissioning. Make diagnostics retain the original failure instead of showing a later success as its cause.
- Verify the correction with focused format/reopen and fault-injection checks, including one-attempt success after a fresh SMI install, interrupted or failed reads/writes, and a subsequent reopen/readback of the commissioning record. Run the canonical managed Debug rebuild and record artifact identity.
- Obtain separately authorized physical qualification evidence on both affected controller/card combinations, using approved expendable media: service 467 CID identity at baseline and after any powered-off card replacement, initialization, or reboot relevant to the result; service 468 terminal status; exact firmware image identity; and first-attempt pass/fail. Do not perform or request powered SD removal, and do not initiate destructive physical reformatting solely from this directive.
- Reconcile the result against v00.05.01 and update current release/qualification truth before declaring the outcome complete. A retry-only success is insufficient.

## Authority And Delivery Boundary

- Preserve any endpoint, target, timing, non-goal, or authority language stated in the directive.
- The requested delivery target is one 00.05.02 SMI firmware release containing both fixes. Deployment and publication require their release qualification gates and explicit owner authorization.
- 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-30

- Directive issued after first format failed and second format worked on two controls with different SD cards following a fresh SMI firmware install.
- The owner confirmed both attempts occurred in one powered session; no diagnostic service capture was made between attempts. The latest GitHub release at intake is v00.05.01.
- Screenshot evidence: `work/01-q&a/first format attempt failed, second worked, reproduced on 2 controls, different sd cards.png` and `work/01-q&a/second format attempt worked.png`. No firmware change or physical test was made during directive intake.





