Hangar

The SDLC, from the platform side

Seven stages, one platform underneath

For a developer, shipping software should feel like three steps: write it, push it, see it running. The platform's job is everything in between that makes those steps feel simple. Each stage below is how I think that part should work, the place in Hangar that does it, and what changes when the author is an AI agent.

  1. 01 Plan and design Contracts first, decisions in writing Agree on what good looks like once, write it down as an API, and write down why. An API-driven control plane, ready for AIHonest by design
  2. 02 Onboard and code One file, scaffolded for you A developer's first push should just work, and they should only ever have to look after one file. The platform is a productPaved roads, with security built in
  3. 03 Build and test Rootless builds, pinned catalogs, real tests Build without special privileges, change shared things carefully, and test against the real thing. The platform is a productEvent-driven by default
  4. 04 Secure and govern Honest gates, workload identity, no stored keys The safe path should be the easy path, and a check that isn't real yet should say so. Paved roads, with security built inHonest by design
  5. 05 Release and deploy Only a merged commit crosses a boundary No cluster holds another cluster's credentials. The only thing that crosses a boundary is a reviewed, merged commit. Every change is a reviewed commitEvent-driven by default
  6. 06 Operate and observe One trace per change, one pane of glass You should be able to follow any change from start to finish in one place, and trust the numbers you see. Event-driven by defaultInterfaces people trust
  7. 07 Measure and improve Scorecards, evals and written-down gaps Measure honestly, share the number, and keep a written list of what still needs work. Honest by designThe platform is a product