Current State

Current State

This is the canonical public status document for GloriousFlywheel.

Use this page for the current product boundary, operating contract, and active work. Treat docs/research/ as supporting evidence and deeper planning notes, not the primary product surface.

Snapshot date: 2026-04-20

What GloriousFlywheel Is Now

GloriousFlywheel is a GitHub-first self-hosted Actions runner platform built around:

  • ARC on the honey on-prem cluster
  • Attic for Nix acceleration
  • optional Bazel remote-cache acceleration
  • a SvelteKit dashboard and related operator surfaces
  • OpenTofu, Bazel, and Nix tooling to operate the platform

Current Operating Contract

  • honey is the only physical cluster target
  • bumble is the durable-state and storage-biased node inside honey
  • sting is the stateless compute-expansion node inside honey
  • operator access is tailnet-first and private
  • GitHub is the primary forge surface
  • GitLab remains a compatibility path, not the primary control plane
  • tinyland-nix is the general 8Gi Nix lane
  • tinyland-nix-heavy is the heavy Rust and Nix canary, currently pinned to honey while sting runtime startup is under repair
  • the honey Nix lanes do not depend on a shared /nix/store PVC for baseline scheduling
  • the runner image now carries Determinate Nix, but workflows should still prefer nix-job or otherwise verify/bootstrap explicitly
  • Attic and Bazel are acceleration layers, not publication surfaces
  • FlakeHub is planned only as post-bootstrap publication and discovery
  • attic, arc-runners, gitlab-runners, and runner-dashboard now use the environment-owned S3-compatible state path on honey
  • GitHub-hosted paths are acceptable only when they are explicit publication, docs, or otherwise bounded external-authority exceptions, not when they still own the same dogfood path being claimed as self-hosted

Current Reality

  • PR #209 established the merged honey rollout baseline
  • PR #234 now gives GloriousFlywheel itself a green default-branch proof path with live tinyland-docker, tinyland-nix, and tinyland-nix-heavy verification
  • repo-owned tinyland-nix, tinyland-docker, and tinyland-nix-heavy now carry the normalized cache and runtime contract
  • the baseline tinyland-nix path no longer depends on the bumble-bound OpenEBS /nix/store PVC to schedule on honey
  • tinyland-nix-heavy has been proven under a real heavy Rust/Nix canary; the lane is temporarily pinned to honey while sting runner startup is repaired
  • the first real heavy-Nix downstream canary is Jesssullivan/yt-text#67
  • Jesssullivan/scheduling-kit#64 and Jesssullivan/acuity-middleware#50 are now the clearest repo-owned downstream package-lane enrollments on main
  • Jesssullivan/MassageIthaca now reflects repo-owned runner authority on main, so it no longer needs to be counted only as a named non-default-branch authority exception
  • Jesssullivan/XoxdWM now has successful default-branch self-hosted fast CI on xoxdwm-nix, even when the repository runners API still reports zero visible runners while the scale set is idle
  • release tags v0.1.0, v0.1.1, and v0.1.2 were cut from merged main with green GitHub release, GHCR image, and FlakeHub publication runs
  • recent orgwide repo activity is still much wider than real runner enrollment: on the current 30-day non-fork workflow surface, downstream enrollment is 9 / 39 repos on default branches, or about 23%
  • orgwide reporting now has a live operator path through just orgwide-enrollment-scoreboard, which prints the three numbers needed to stay honest: real runner authority, template consumers by mode, and named authority exceptions
  • orgwide promotion planning now has a live operator path through just orgwide-enrollment-queue, which turns that live census into claim protection, template cleanup, platform-prereq, promotion, and keep-hosted categories
  • GloriousFlywheel currently has no open pull requests; the live control plane is issue-driven

Active Work

  • active initiative: GloriousFlywheel Hardening and Expansion (Apr–May 2026)
  • active project: GloriousFlywheel Month 1 — Hardening and Expansion
  • #277 / TIN-279: broaden downstream rollout beyond the first canary tranche
  • #279 / TIN-281: automate runner hygiene and orgwide enrollment

Biggest Remaining Gaps

  • #277: tranche-1 downstream adoption proof is landed, but broader rollout is still not a repeatable migration story across the repo surface
  • #279: runner workspace hygiene now has a bounded honey _work/* lifecycle contract with a run-driven checkout-triage entrypoint plus a bounded reconcile loop, and orgwide enrollment now has live scoreboard and queue commands, but promotion execution is still narrow relative to recent repo activity

Go Deeper

GloriousFlywheel