← Mission 1 · FD Build

Build Sub-Mission

Mission 1D · Mission Dependencies & Blockers

Make dependencies and blockers visible so the Pilot can tell what merely informs a Mission, what is waiting on something else, and what actually prevents progress.

CALM · Operational Observation

Dependencies & Blockers · V0

Not everything a Mission waits on is a blocker

This first anatomy separates context the Mission should know about from a dependency that constrains a Pass and from a true blocker that prevents authorized progress.

Informational

Relevant context or another Mission’s state. Worth seeing, but it does not constrain the current Pass.

Mission can keep flying

Waiting

A specific future action or piece of evidence constrains what can happen next, while unrelated work may continue.

Constrains a Pass, not necessarily the Mission

Blocking

The Mission cannot make authorized progress until this dependency changes or is resolved.

Mission grounded

Current 1D flight state

No true blocker has been established for this sub-mission. Production visibility was verified, so this V0 can proceed inside the existing build envelope.

Classification rule

A dependency becomes a blocker only when evidence shows it prevents the next authorized progress—not merely because another event has not happened yet.

Progress

Dependencies & Blockers V0 is live. Pilot inspection confirmed that informational, waiting, and blocking states are understandable enough to proceed to observation.

Current Gate

Observe real dependency changes and verify that true blockers are distinguished from waiting work.

Next authorized action

Use real Mission movement to test dependency classifications before adding automation or cross-Mission inference.

Pilot authority

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

Authorized scope

What this aircraft is carrying

Visible dependencies and blockers on Mission detail
Informational vs waiting vs blocking state
Explicit grounded / not grounded distinction
Dependency ownership or source where already known
No automatic cross-Mission inference in the first pass
No graph database, orchestration layer, or new infrastructure

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.