# Executive Directive: Mitigate the data-log graph zoom defect so operators can zoom in before nine hours of data have accumulated, without displaying fabricated samples or future data.

Status: promoted
Type: idea-brief
Role: project-executive-directive-v1
Updated: 2026-09-30
Next Action: verify the graph correction under MAP-0011 in the shared 00.05.02 candidate
Readiness Review: performed by the receiving Plan Cycle; ask the CEO only about material ambiguity
Produces: MAP-0011

## CEO Directive

Mitigate the data-log graph zoom defect so operators can zoom in before nine hours of data have accumulated, without displaying fabricated samples or future data.

## Desired Outcome

Remove the artificial nine-hour wait before Graph Zoom In becomes available on a
new data log. Short logs should offer useful narrower views while time before
the first real sample remains empty and time after the newest persisted sample
does not appear as logged data. Preserve normal zoom, pan, and follow-newest
behavior for longer logs.

## Current Position

The defect is diagnosed in `src/HMI_MainEventHandler.c`. Graph opens in a
12-hour view ending at the newest record, so its center is six hours behind
that record. Button Zoom In keeps the center while proposing a six-hour view;
its left edge is therefore nine hours behind the newest record. The planner
rejects any proposal whose left edge precedes the oldest record. The completed
`TKT-0007` addressed live follow-newest behavior, not this short-log bound.
This directive is captured and has not yet been delegated for implementation.

## 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

Verify the graph correction under MAP-0011 and complete the shared 00.05.02 candidate after the format defect is resolved.

## Why This Next

The source correction is in progress; the next material evidence is a passing candidate build and target behavior across short and mature logs.

## Blockers

- None.

## Operator Needs

- None.

## 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

A focused correction removes the nine-hour threshold without fabricating
samples or future data. Verification covers short histories below the
threshold, the nine-hour boundary, mature logs, all zoom levels, pan limits,
and follow-newest behavior. Run the repository's focused graph checks and
canonical managed Debug rebuild, record the results, and reconcile the
directive's outcome before reporting completion.

## 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

- The owner requested a Tool Shed directive to mitigate the graph zoom defect.
- Source diagnosis: `initializeGraphTemp()` sets a 12-hour viewport ending at
  the newest record; `planZoomPanActions()` centers the six-hour zoom on that
  viewport and `considerAndPopulateAnyNewTime()` rejects its left edge until
  at least nine hours of records exist. No firmware change was made at intake.

