GloriousFlywheel Convergence Slice Plan 2026-04-16

GloriousFlywheel Convergence Slice Plan 2026-04-16

Snapshot date: 2026-04-16

Purpose

Consolidate the live execution surface after the reset closeout and stop treating the old milestone ladder as the active control plane.

Live GitHub Control Plane

Verified on 2026-04-16:

  • open GitHub milestones: 0
  • closed rollout issue: #208 Execute honey on-prem rollout and backend-authority convergence at 2026-04-16T16:56:05Z
  • merged rollout baseline: PR #209 feat(honey): migrate IaC stacks to on-prem honey cluster
  • current adjacent planning and follow-on lanes:
    • #210 downstream adoption tranche and migration kit
    • #211 GitHub-first forge boundary
    • #212 benchmark and competitive comparison
  • current open issues outside those lanes: #66, #44
  • current open PR count: 0

Interpretation:

  • the live GitHub surface is issue-and-PR driven right now
  • GitHub milestones are not the active execution vocabulary
  • #209 established the landed honey rollout baseline
  • the remaining convergence work now needs new reviewable slices instead of one lingering catch-all PR

Strategic Target

  • GitHub-first runner platform
  • one physical on-prem cluster: honey
  • tailnet-only operator plane
  • durable backing state biased toward bumble
  • sting reserved for explicit stateless compute capacity
  • no new primary dependence on Civo
  • cleaner Nix, Bazel, and Attic contract with eventual FlakeHub publication

What Has Already Proven Out

  • lab#72 merged
  • blahaj#68 merged on domain/tinyland.dev
  • tinyland.dev#136 is blocked by a repo packaging and build-order problem, not by the GloriousFlywheel runner contract
  • XoxdWM#28 is blocked by self-hosted capacity, not by a surfaced code failure

This means the runner contract is no longer hypothetical. The next blockers are backend convergence, rollout execution, and externalized downstream repo constraints.

Repo Health Reality

  • the local worktree still has a large amount of unmerged execution truth
  • too much of the active program still lives in one dirty checkout
  • no open PR currently carries the remaining convergence work
  • the repo needs fewer giant local surfaces and more reviewable slices

Canonical Slice Map

Slice A: Honey Rollout, Backend, And Operator Path

Primary owner surface:

  • post-#209 follow-on reviewable slice

Includes:

  • backend authority convergence
  • local-first operator path against honey
  • rollout truth for stack config, deployment docs, and apply order

Slice B: Dashboard Auth And Control Plane

Primary owner surface:

  • repo-local execution until broken into reviewable PRs

Includes:

  • tailnet-first auth model
  • dashboard read and mutation boundaries
  • control and auth audit surfaces

Slice C: PM And Docs Surface

Primary owner surface:

  • this note plus the program-surface and milestone-matrix notes
  • gloriousflywheel-post-209-pr-slice-map-2026-04-16.md
  • adjacent follow-on issues #210, #211, and #212

Includes:

  • adoption inventory
  • forge boundary
  • benchmark methodology
  • issue-driven execution framing

Slice D: Residual Dogfood And Cleanup

Primary owner surface:

  • follow-on cleanup after the merged #209 rollout baseline

Includes:

  • local composite-action cleanup
  • residual examples
  • secondary doc sweeps

Operating Rules

  1. Treat PR #209 as the landed rollout baseline, not the current open execution anchor.
  2. Treat #210, #211, and #212 as secondary lanes, not substitutes for rollout execution.
  3. Treat M1 through M5 and M#6 through M#12 as local sequencing vocabulary only.
  4. Prefer reviewable slices over adding more broad local-only planning sprawl.
  5. Keep honey rollout notes authoritative over stale milestone-era wording.
  • gloriousflywheel-post-209-pr-slice-map-2026-04-16.md

GloriousFlywheel