Architecture · 01 of 08 · The family

Hangar with Autopilot: six products and one reference system

Autopilot sits beside Airframe and Glidepath, not above them. It uses Airframe's contract through tools, uses Glidepath's guardrails as gates, and shows up in Tower as an Agent tab.

Hangar with Autopilot: six products and one reference system Architecture of the Hangar platform: Tower as the command console, Airframe, Autopilot and Glidepath as the middle layer, Apron as ground infrastructure, with Skyport as the reference system deployed by Glidepath and Modelplane as an outside model backend reached through Autopilot's model proxy. HANGAR · THE PLATFORMFORMSAGENT TABRELEASESTOOLSGATESCLUSTERSDEPLOYSMODEL PROXYTowercommand console · BackstageAirframeXRDs · chart · contractAutopilotClearance · AgentRun · proxyGlidepathCI/CD · guardrails · releasesAproncluster template · groundSkyportdemo apps + agentsModelplaneself-hosted modelsAutopilot is the sixth product. It drives the Airframe A+ program and Skyport gains six AI workloads.LEGENDNew: AutopilotExists todayGround infrastructureReference systemOutside Hangar

Principle honored

One vocabulary, six products: Hangar, Apron, Airframe, Glidepath, Tower, Autopilot. Clearance and Flight recorder are features of Autopilot, like Tower's Ground Control.

What changes

  • Airframe gains a machine-readable contract (the A+ program).
  • Autopilot adds Clearance, the AgentRun claim and a model proxy.
  • Skyport gains six AI workloads, one per workload shape.

Independence

Each product keeps its own repo and its own install. Autopilot needs Airframe and Glidepath; it does not need Tower to run, only to be seen.

Hangar · Autopilot · plan