01

Phase 1 Roadmap Cockpit

Program Now

Where is Phase 1 now, and what changed most recently?

Engineering complete10
Merged into main10
Product accepted by Mike0

No feature currently Active

F1, F2, F3, F4, F5, F6, F7, F8, F9, and F10 are merged and browser-proven. Their Mike reviews remain open.

→
Material acceptance conditionMike acceptance is allowed to trail engineering, but Phase 1 cannot close until the required operating scenarios are accepted.
02

Phase 1 Roadmap Cockpit

Outcome Waves

What changed operating reality does each wave unlock?

W13/3 browser-proven

Review optimizer results and recover safely

F1 saved-candidate browsing, F2 candidate-difference explanation, and F3 restore-integrity detection are merged and browser-proven. Mike acceptance remains pending for all three features.

F1 Browse saved candidatesF2 Explain candidate differencesF3 Detect restore integrity failure
Visible exitBrowse candidates, explain changed work, and reject an incomplete restore.
W23/3 browser-proven

Trust planning inputs

F4 B2B exception review, F5 B2C channel model, and F6 planning readiness are merged and browser-proven. Mike product-owner acceptance remains pending; these capabilities will be reviewed in the operating cycle they support.

F4 Review B2B import exceptionsF5 Apply the Phase 1 B2C channel modelF6 Show planning readiness
Visible exitImport demand and distinguish a planning warning from a hard blocker.
W32/2 browser-proven

Current Plan To Floor Packet

F7-F8 Current Plan To Floor Packet is merged and browser-proven. Mike agreed with the routine-plan and explicit replacement policies; complete product-owner acceptance remains pending.

F7 Select and supersede a local current planF8 Generate the daily and floor packet from the current plan
Visible exitPut one local plan in force and show its identity on every required output.
W42/2 browser-proven

Status To Performed Work

F9-F10 Status To Performed Work is merged and browser-proven. Mike product-owner acceptance remains pending before the Phase 1 acceptance gate.

F9 Show customer and management status from the current planF10 Record completion and reconcile planned versus actual
Visible exitRecord what happened and reconcile planned work with performed work.
03

Phase 1 Roadmap Cockpit

Feature Lifecycle Pipeline

Where is every product feature, and what gate comes next?

Identified

0
None

Shaped

0
None

Owner Approved

0
None

Delivery Ready

0
None

Active

0
None

Browser Proven

10
F1 Browse saved candidatesF2 Explain candidate differencesF3 Detect restore integrity failureF4 Review B2B import exceptionsF5 Apply the Phase 1 B2C channel modelF6 Show planning readinessF7 Select and supersede a local current planF8 Generate the daily and floor packet from the current planF9 Show customer and management status from the current planF10 Record completion and reconcile planned versus actual

Owner Accepted

0
None

Delivered

0
None
Browser Proven
Product code, focused tests, and real-browser evidence exist.Owner Accepted
Mike confirms the behavior supports the operating workflow.Delivered
Merged behavior and required product acceptance are both present.
04

Phase 1 Roadmap Cockpit

Dependency & Next Unlock

What can begin next without violating the one-lane policy?

Foundation
F1 Browse saved candidatesBASE-CAND
Unlocked next
F2 Explain candidate differencesF1
F3 Detect restore integrity failureF1
Dependency stage 3
F4 Review B2B import exceptionsF2
Dependency stage 4
F5 Apply the Phase 1 B2C channel modelF4
Dependency stage 5
F6 Show planning readinessF5
Dependency stage 6
F7 Select and supersede a local current planF6
Dependency stage 7
F8 Generate the daily and floor packet from the current planF7
Dependency stage 8
F9 Show customer and management status from the current planF8
Dependency stage 9
F10 Record completion and reconcile planned versus actualF9
None
No path
One active core-feature ship lane
05

Phase 1 Roadmap Cockpit

Phase Acceptance Coverage

Which Phase 1 behaviors have engineering proof, and which still need Mike?

Browser proof and merge do not imply product acceptance.Every scenario remains open until the required Mike review is recorded.
P1-A01Daily operating cycleF8 Generate the daily and floor packet from the current planF9 Show customer and management status from the current planF10 Record completion and reconcile planned versus actualBrowser proof presentMike acceptance pending
P1-A02B2B import exceptionsF4 Review B2B import exceptionsBrowser proof presentMike acceptance pending
P1-A03B2C channel modelF5 Apply the Phase 1 B2C channel modelBrowser proof presentMike acceptance pending
P1-A04Planning readinessF6 Show planning readinessBrowser proof presentMike acceptance pending
P1-A05Candidate and current-plan safetyF1 Browse saved candidatesF7 Select and supersede a local current planBrowser proof presentMike acceptance pending
P1-A06Candidate history and explanationF1 Browse saved candidatesF2 Explain candidate differencesBrowser proof presentMike acceptance pending
P1-A07Current-plan supersessionF7 Select and supersede a local current planBrowser proof presentMike acceptance pending
P1-A08Consistent output identityF8 Generate the daily and floor packet from the current planF9 Show customer and management status from the current planBrowser proof presentMike acceptance pending
P1-A09Minimum actualsF10 Record completion and reconcile planned versus actualBrowser proof presentMike acceptance pending
P1-A10Persistence and recovery integrityF3 Detect restore integrity failureBrowser proof presentMike acceptance pending
F6 · Show planning readiness
Enlarged view of the running scheduler demonstrating Show planning readiness with fictional data

Real running-product evidence using fictional data. Click outside the image, press Escape, or choose Close to return to the roadmap.