Hangar

Log

Hangar is never finished

Hangar is where I try things, so it keeps changing as I learn. These are the milestones so far, newest first, each linked to the place where I wrote down what happened and why.

  1. This site

    Hangar gets a home on the web: the platform, its principles and its diagrams in one place, built from the same repo.

  2. Autopilot, the sixth product

    Design for running any AI agent workload, bounded and audited. The Clearance core, the AppSpec planner, nine Skyport agent definitions and six Preflight cases are built and tested; the AgentRun XRD is drafted. The Airframe scorecard lands with a committed baseline of 27 out of 100.

  3. Infisical operator retired on the prod cluster

    All five apps and Glidepath itself migrated onto the new Airframe pin and External Secrets, phase by phase, with the plan and each phase recorded as it closed.

  4. The prod cluster, rebuilt

    The upper cluster is rebuilt from the Apron template instead of being patched in place.

  5. Every app stack scaffolds its cicd.yaml

    The last hand-authored step in onboarding goes away. The same week, docs across every repo get one table of contents and TechDocs wiring in Tower.

  6. SecretStore on Infisical, built

    One secret store per app and cluster, shared across that app's environments, never across clusters.

  7. The Hangar brand

    The project is renamed Hangar, with the instrument-dial mark family: one gauge, one glyph per product, and the calm-cockpit colour rule.

  8. A self-hosted transparency log

    Rekor and Trillian join the self-hosted Fulcio, so image signatures get a real transparency-log timestamp.

  9. Testkube, and reading the source

    The documented multi-namespace mode turns out to be paid-only in the source. The shared-namespace design ships, with a Kyverno policy closing the gap RBAC cannot.

  10. Lower and upper environments become a real boundary

    Built and verified live after a real bug: a separate AppProject, not just a separate folder.

  11. AI triage in the control plane

    A Composition Function watches Argo Rollouts and dispatches a diagnosis on degradation. Proven end to end: a real broken canary, a real diagnosis, a real fix PR. The application chart is verified live the same day.

  12. Design resolved, build starts

    The GitOps strategy and service-catalog design settle, and the platform around Glidepath begins: Crossplane as the control plane, ArgoCD for delivery, Backstage as the pane of glass.