Dependency graph · 03 of 08 · Order

What blocks what: the critical path in six boxes

Skyport's remaining components join the contract stream instead of waiting behind it, so each is built once. Ownership must be split before agents get write tools, which is why it sits on the path to the Autopilot core.

What blocks what: the critical path in six boxes Dependency graph in four ranks: the contract foundation feeds both the outputs and new born-A+ components and the ownership split; both feed the Autopilot core with the planner; and that feeds both the Skyport AI workloads and the evaluation gate. Contract foundationguard · strict schema · validateOutputs + new componentsMongo, OAuth: born A+Ownership splitbase layer · release fileAutopilot core + plannerClearance · AgentRun · toolsSkyport AI workloadssix shapesEval gate + autonomyregression, ladderRANK 1RANK 2RANK 3RANK 4Nothing on the right can start until everything it points from is done and verified.LEGENDThe acceptance test lives hereMilestone workstreamDepends on

Principle honored

Never retrofit. A component built before the contract needs a second pass; one built after is born with outputs, verify checks and full descriptions.

What changes

  • Parallel and safe: docs and walkthroughs, the Autopilot repo setup, Modelplane reading.
  • Not parallel: the ownership split and Clearance write tools.
  • Skyport parts 4 and 5 (Mongo, OAuth) ride rank 2.

Also

The Skyport AI workloads also read baggage-api, so baggage-api and MongoDB must exist by rank 4, which the plan guarantees.

Hangar · Autopilot · plan