Deployment Flow

Deployment Flow

Current main does not use one universal “commit to production” pipeline. This page exists to retire that old story and restate the real deployment boundary.

Current Mainline Flow

GloriousFlywheel is GitHub-first and split into workflow families:

  1. Validate and proof — repo validation, platform proof, source Bazel proof, and bounded reporting workflows
  2. Build and publish — container, FlakeHub, release, and docs publication surfaces
  3. Targeted deploy — the ARC stack has an automated apply path on main when ARC-related paths change
  4. Operator deployment — the remaining stacks still rely on bounded internal operator deployment paths instead of a universal auto-apply stage

Pull Requests

Pull requests primarily run validation and proof workflows plus bounded ARC plan coverage when relevant paths change. They do not run a universal deploy stage.

Pushes To main

Pushes to main run validation, proof, and path-scoped publication or deploy workflows. Current automated deployment on main is intentionally narrow:

  • Deploy ARC Runners for the ARC stack
  • Deploy Docs for the docs site

The repo does not currently auto-apply every infrastructure stack on merge.

GloriousFlywheel