# Executive Directive: to investigate, verifiy if it is an issue and resolve graph time range to real data.

Status: promoted
Type: idea-brief
Role: project-executive-directive-v1
Updated: 2026-10-05
Next Action: obtain explicit owner authorization for a scoped local Work1 commit, then checkpoint the revised 00.05.03 graph candidate and reconcile the evidence-backed outcome
Readiness Review: performed by the receiving Plan Cycle; ask the CEO only about material ambiguity
Produces: MAP-0012

## CEO Directive

to investigate, verifiy if it is an issue and resolve graph time range to real data.

## Desired Outcome

Make the directive true through the smallest coherent set of subordinate cycles.

## Current Position

MAP-0012 captures the Controller A investigation, confirmed navigation and endpoint-label defects, and revised 00.05.03 bench candidate. The owner caught that the first candidate still panned a 12-hour graph by six hours; source review found the same half-window behavior at the other ranges. The revised candidate passed 25 Controller A views across all five ranges, with two left and two right moves at each zoom and ten HD webcam photos. All historical moves advance by a complete displayed interval. The revised candidate graph cache matched all 61 retained SD export records at the same minute timestamps and temperatures. Full flash readback matched the revised SREC. The scoped local Work1 commit remains pending under the workspace's explicit commit authorization rule. Release qualification and rollout remain separate.

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

After explicit owner authorization, checkpoint the revised and verified 00.05.03 graph source and Tool Shed state locally, then reconcile the directive outcome.

## Why This Next

Controller A verified the revised candidate with exact flash readback, ten physical camera photos, 25 range/pan views across 1, 3, 6, 12, and 24 hours, and 61 independent SD-export record matches. The Work1 endpoint still requires its scoped local commit.

## Blockers

- The workspace `AGENTS.md` requires an explicit owner request before staging or committing; that request is pending.

## Operator Needs

- Decide whether to authorize a scoped local Work1 commit. No push or firmware release is included.

## Completion Condition

The directive's outcome is evidence-backed, reconciled, and reported back to the operator.

## Authority And Delivery Boundary

- Preserve any endpoint, target, timing, non-goal, or authority language stated in the directive.
- Without explicit delivery language, source-changing work stops at a verified Work1 candidate.
- 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-10-05

- Directive issued by the project owner through the 100k command surface.
