Architecture · 01 of 19 · Hangar today

Hangar as it is, and the one new component beside it

Nothing here replaces a Hangar component. Clearance sits next to Tower and federates its MCP actions. Durable writes are git commits the cluster pulls, like any human commit. Ephemeral agent runs are claims to Crossplane, dev clusters only.

Hangar as it is, and the one new component beside it Architecture in four planes: agents and people, interface and policy, git as the only write path, and the pull-based cluster, showing the existing Tower, repos, Glidepath, ArgoCD and Airframe, with a single new component, Clearance, added beside Tower. AGENTS AND PEOPLEINTERFACE AND POLICYGIT · DURABLE WRITE PATHCLUSTER · PULL-BASEDMCPUIFEDERATESPRCOMMITCHECKSPULLEDAPPLIESAGENTRUN CLAIM · DEV ONLYAgent workloadany framework · any modelEngineerworks in TowerClearanceMCP · CEL policy · auditTower (Backstage)portal · MCP actionsApp + gitops reposPRs · platform/envsTenants repoxr-requests/GlidepathTekton · PaC · brokerArgoCD ×2platform · appsAirframeXRDs · compositionsDurable changes are commits. Ephemeral runs are claims that Crossplane renders.LEGENDNew: ClearanceExists todayActorGoverned callExisting flow

Principle honored

Durable mutations are git commits (service-catalog-design.md §0). Ephemeral runs are claims to Crossplane, an already-privileged and audited control plane. Each cluster pulls, and holds no other cluster's credentials.

What changes

  • One new service: Clearance (Python), an InfraService like skyport-broker, with a model proxy beside it.
  • It federates the Backstage MCP actions already in app-config.yaml instead of re-implementing catalog and scaffolder tools.
  • Airframe gains one XRD, AgentRun, and one Python composition function. Nothing else changes.

What is real

Checked in the repos today: Tower, the tenants repos, the two ArgoCD instances and Airframe v0.3.90 all exist as drawn. Whether the Backstage mcpActions endpoint is live on a cluster is not verified; check that first.

Hangar · Autopilot