← Mission 1 · FD Build

Build Sub-Mission

Mission 1C · Mission Progress & Trajectory

Help the Pilot understand whether a Mission is actually getting closer to its intended outcome, rather than confusing activity with verified progress.

CALM · Operational Observation

Mission Progress · V0

Progress is evidence of movement, not volume of activity

Live Mission state connected

Flightdeck does not assign a percentage complete yet. This model reads the parent Mission’s durable build state and separates what has been verified, what is currently in flight, and what is authorized next.

Completed · Verified

Mission 1A–1F have each passed their bounded V0 implementation Gate and are now under operational observation. The Mission 1 parent state was reconciled so Navigator no longer presents the completed 1B tightening pass as active work.

Current · In flight

Mission 1 — Operational observation across verified build lanes

Gate: Real Mission use remains understandable and actionable without stale summaries or unnecessary attention cost; any newly exposed gap is attached to the affected build lane before expansion.

Next · Authorized

Keep the six verified Mission 1 build lanes under real-use observation. Reopen only the affected lane when a concrete usability, authority, freshness, dependency, learning, or verification gap appears; continue unrelated authorized Missions independently.

Progress rule

Activity can create evidence. Evidence can pass a Gate. Only a passed Gate advances verified progress.

Progress

Completed → Current → Next Progress V0 is live and connected to durable Mission build state. The first implementation Gate passed without adding scoring, prediction, schema, or infrastructure. Cockpit trajectory language is now evidence-honest: CALM no longer manufactures an unsupported “On course” claim.

Current Gate

Observe the live progress anatomy during real Mission movement and verify that it communicates direction without implying unsupported certainty.

Next authorized action

Use real Mission changes to test whether the Pilot can tell what was verified, what is in flight, and what is authorized next. Add trajectory sophistication only if observation exposes a concrete gap.

Pilot authority

No Pilot approval currently required. Work remains inside the authorized envelope.

Authorized scope

What this aircraft is carrying

Completed / Current / Next progress anatomy
Pass → Gate → verified outcome progression
Visible distinction between activity and verified progress
Trajectory language without unsupported prediction
No percentage-complete score until evidence supports one
No new schema or infrastructure in the first pass

Governance

Independent flight, visible dependencies

Evidence Before Expansion applies to this sub-mission independently. A Gate here does not stop another FD Build sub-mission unless a real dependency requires it. Parent Mission 1 remains the cockpit view for the whole build fleet.