# Reconcile SMI baselines, current truth, and planning surfaces Workpackage

Status: complete
Type: workpackage
Updated: 2026-07-21
Next Action: none

Project Map: work/maps/map-smi-firmware-stabilization-and-qualification.md
Canonical Truth: E:/dev/high_point/7520553_SMI_FW/README.md and E:/dev/high_point/7520553_SMI_FW/docs/

## Current Context

The SMI firmware workspace now exposes four linked knowledge surfaces:

- `discovery/` -> the July 12 repository reconnaissance;
- `plans/` -> the established SMI Tool Shed planning/evidence tree;
- `platform-standards/` -> an independent Git repository for HPT7 policies;
- `renesas-setup/` -> the shared known-good Synergy/e2 setup baseline.

Substantial firmware and controller work occurred after some of those surfaces
were written. Current source is 00-04-13 with SMI schema 2, configuration
recovery, graph/export changes, SD services 469/470/472/474, clean builds, and
new dual-controller evidence. Some older documents are intentionally valuable
pre-change baselines; others claim to be current and have become stale.

The firmware checkout also contains a physical ignored `work/` tree created
before the canonical `work/` tree was visible. It contains a new map,
inventory, and runtime evidence and must not be discarded or allowed to become
a second planning authority.

## Recommendation

Reconcile by classification and provenance, not by rewriting every older file.
Use five explicit roles:

1. **Baseline** — immutable observation of the system at a named date/hash.
2. **Current truth** — accepted behavior in firmware `README.md` or `docs/`.
3. **Active coordination** — current maps, workpackages, tickets, and checklists
   under canonical `work/`.
4. **Evidence/history** — dated build, runtime, decision, incident, and completed
   work records that remain immutable.
5. **Superseded** — a retained artifact with an explicit replacement link.

Avoid mass find/replace, silently modernizing historical evidence, relabeling
old Setup A/B results to current bench names, or copying one whole work tree
over another. Independent repositories retain their own Git history and receive
separate changes and commits.

## Current State

Completed:

- Junctions expose all four external knowledge surfaces.
- The Tool Shed snapshot and standard work layout are installed locally.
- A first audit identified definite stale facts and status contradictions.
- The Renesas setup verifier passes against the present machine and workspace.
- The canonical SMI plan already preserves historical/current bench-label
  distinctions and marks several completed/deferred workpackages correctly.

Incomplete:

- No complete classification inventory exists across all linked surfaces.
- July 21 service-469/470 work and evidence are absent from canonical plans.
- Discovery still presents 00-04-11 and schema 1 without a visible baseline
  banner or current-state successor.
- Platform policy adoption statuses predate accepted 00-04-13 configuration
  implementation and representative target evidence.
- Firmware configuration docs and planning evidence disagree on whether the
  remaining destructive fault cases were accepted/waived or remain required.
- The local `work/` tree and `work/` have not been collision/hash compared
  and consolidated.
- Renesas setup documentation contains a stale comparison path and omits the
  proven isolated build/generic J-Link connector additions.

## Goal

Produce one auditable navigation system in which a reader can tell what was
true before the changes, what is true now, what evidence supports each claim,
what work remains, and which repository owns each statement—without losing or
retrofitting historical records.

## Why It Matters

Mixed temporal states can cause an engineer to act on an obsolete firmware
version, repeat completed work, skip an open qualification gate, or mistake a
baseline observation for current behavior. Preserving provenance is also
necessary for safety, release review, and meaningful controller evidence.

## Major Outcomes

- Every relevant artifact has a temporal role, observation date, authority, and
  disposition.
- Historical discovery and evidence remain intact and visibly historical.
- `work/` is the sole current Tool Shed coordination tree.
- Firmware `README.md` and `docs/` hold settled current product truth.
- Platform standards accurately state SMI adoption and qualification status
  without implying that the whole production release is complete.
- Shared Renesas setup distinguishes the stable toolchain baseline from newer
  proven workflow additions.
- All indexes and links pass Tool Shed validation with no competing active maps.

## Delivery Stages

| Stage | Outcome | Entry Evidence | Exit Evidence |
| --- | --- | --- | --- |
| 1. Freeze and inventory | No-mutation manifest of every artifact, hash, modification time, Git owner, temporal role, and claimed status | Junction targets accessible | Reviewed classification inventory; ambiguous items explicitly marked |
| 2. Reconcile authority | One ownership matrix for firmware docs, plans, discovery, standards, setup, and evidence | Stage 1 inventory | No artifact has two current authorities; baseline/current boundaries approved |
| 3. Consolidate Tool Shed state | Unique local artifacts/evidence safely merged into `work/`; duplicates hash-verified; collisions reviewed individually | Authority matrix and backups | Canonical plan index includes all retained artifacts; local duplicate authority eliminated |
| 4. Capture July 21 delta | Services 469/470/474 behavior, watchdog fix, builds, controller runs, and logger health added to current planning/evidence | Source diff, build artifacts, J-Link observations | Claims link to exact code/build/runtime evidence and current next actions |
| 5. Reconcile status conflicts | Configuration, service 472, SD release gates, and stale checklists have one explicit accepted status | Owner decisions and existing evidence | Completed, deferred, waived, open, and release-blocking states are unambiguous |
| 6. Refresh current-facing docs | Current docs updated; baseline discovery retained with dated banner/successor; setup and standards updated in their proper repositories | Stages 1–5 | Searches find no unlabeled obsolete current claims; changelogs/ADRs preserve policy history |
| 7. Verify and close | Indexes regenerated, stale links checked, repo boundaries verified, and final diff reviewed | All scoped edits complete | Tool Shed checks pass; independent Git diffs are intentional; closeout summary approved |

## Detailed Sequence

1. Capture read-only manifests for the firmware repository, local `work/`,
   `work/`, `discovery/`, `platform-standards/`, and `renesas-setup/`.
2. Record each surface's real filesystem target and Git top-level; never assume
   a junction shares the firmware repository's history.
3. Create an inventory row for every Markdown planning/documentation artifact
   with: role, observed-as-of date/hash, current authority, confidence, and
   keep/update/supersede/merge decision.
4. Review ambiguous documents before edits. In particular, distinguish a
   baseline that is old by design from a current document that is stale.
5. Hash-compare the physical workspace `work/` tree with canonical
   `work/`. Copy only unique evidence/artifacts after reviewing path
   collisions. Do not overwrite by timestamp alone.
6. Move the July 21 firmware map/inventory content into the established
   stabilization map or link a deliberately scoped successor; do not retain two
   competing top-level active maps.
7. Add dated evidence for service 470 runs 03305/04904, power-cycle recovery,
   service-474 ownership behavior, watchdog remediation, and clean builds.
8. Add the service-469 implementation and live qualification sequence as
   active work, including greater-than-90-day, exact-90-day, 89-day, and signed
   cleanup gates.
9. Decide and record whether representative configuration fault coverage is
   accepted complete. If accepted, update firmware docs to describe waived or
   deferred exhaustive cases; otherwise reopen the completed workpackage.
10. Keep service-472 comparative media qualification explicitly deferred if
    that remains the owner decision; do not describe it simultaneously as a
    production-release gate.
11. Mark obsolete checklists as complete, superseded, or still active based on
    their exact unverified acceptance criteria—not their age.
12. Preserve the July 12 discovery as a named baseline and add a dated current
    delta/current-state successor covering 00-04-13 and schema 2.
13. Update HPT7 platform policy adoption statuses and changelog in the separate
    standards repository, linking the accepted firmware evidence.
14. Correct the Renesas comparison path and append the proven isolated-build
    and generic dual-J-Link workflow without rewriting the stable toolchain
    baseline.
15. Regenerate indexes, run stale-path checks, search for obsolete unlabeled
    `00-04-11`, schema-1, setup-label, and status claims, and review each
    repository diff independently.

## Milestones

### Milestone 1: Classification complete

- [x] All documentation and planning files are inventoried.
- [x] Every item is labeled baseline, current truth, active coordination,
  evidence/history, or superseded.
- [x] Ambiguous status claims are listed without being silently resolved.

### Milestone 2: Planning authority consolidated

- [x] Unique local `work/` artifacts/evidence are preserved in `work/`.
- [x] Duplicate files are hash-confirmed before removal or redirection.
- [x] The established stabilization map contains or links all July 21 work.
- [x] Only one current Tool Shed index/navigation path remains authoritative.

### Milestone 3: Current truth reconciled

- [x] Firmware docs and plans agree on completed, waived, deferred, open, and
  release-blocking qualification.
- [x] Discovery baseline is visibly historical and has a current successor.
- [x] Platform standards and recommendations reflect proven SMI adoption.
- [x] Renesas setup retains its baseline and includes proven newer workflows.

### Milestone 4: Verification and handoff

- [x] Tool Shed indexes regenerate successfully.
- [x] Stale-path checks pass.
- [x] No independent `.git` boundary was copied, removed, or absorbed.
- [x] Each repository has a scoped, reviewable diff and closeout summary.
- [x] The owner can identify the next firmware action from one map in under a minute.

## Resolved Questions

- The representative configuration fault campaign is accepted complete for
  00-04-13 based on the recorded owner waiver. Exhaustive interruption
  boundaries and direct driver-failure injection remain documented exclusions.
- The firmware-workspace `work/` path is now a junction to canonical
  `work/`. The former physical tree is recoverably retained at
  `E:/dev/high_point/AI_Plans/7520553_SMI_FW/migration-backup/workspace-work-precanonical-20260721`.
- Controller A owns the dedicated service-469 data/export campaign. Controller
  B receives normal final-image/service-screen smoke coverage; repeat the full
  fixture campaign on B only if a hardware-specific concern appears.
- Full-capacity format/fill/power-cut and manual graph/export matrices remain
  00-04-13 release gates. Broader comparative service-472 media qualification
  remains incomplete but owner-deferred and is not a current release gate.
- Discovery retains the July 12 baseline and uses a dated July 21 successor
  rather than a history-destroying full rewrite.

## Execution Result

- Classified all knowledge surfaces in
  `work/inventories/inventory-smi-knowledge-surfaces-temporal-classification.md`.
- Imported and SHA-256 verified 19 evidence files; preserved two unique local
  artifacts as explicitly superseded context; regenerated canonical indexes.
- Captured services 469/470/474 implementation, release hash, controller runs,
  logger health, and remaining export gates in dated canonical evidence.
- Reconciled firmware configuration/evaluator status, discovery temporal role,
  platform adoption status, and Renesas setup additions.
- Passed Tool Shed stale-path checks, Renesas setup verification, service 469
  and 470 regression checks, firmware/platform diff whitespace checks, junction
  target checks, and discovery baseline-notice checks.

## Completion Standard

This completion standard is satisfied: historical baselines remain intact and
clearly labeled, current firmware truth agrees with accepted evidence, all
active coordination lives in canonical `work/`, linked repositories have
intentional status updates, no stale link or duplicate authority remains, and
recorded owner waiver/defer decisions are reflected without closing unrelated
release gates.

## Closeout Routing

- Current truth promoted to: `E:/dev/high_point/7520553_SMI_FW/README.md` and
  `E:/dev/high_point/7520553_SMI_FW/docs/`.
- Active coordination retained in: `E:/dev/high_point/AI_Plans/7520553_SMI_FW/work/`.
- Historical context remains in: dated discovery, evidence, incidents, ADRs,
  completed workpackages, and Git history.
- Platform policy changes retained in: `E:/dev/high_point/HPT7-Control-Platform-Standards/`.
- Shared setup baseline retained in:
  `E:/dev/high_point/AI_Discovery/Renesas_Synergy_e2_Setup/`.
- Runtime/status evidence: dated controller-specific records under canonical
  `work/evidence/`.
- Cleanup deferred to: removal of the recoverable migration backup after owner
  retention review, and temporary service-469 J-Link scripts after the active
  fixture/export campaign closes.
