GloriousFlywheel Rollout Execution Refresh 2026-04-22

Correction on 2026-04-24: This note is preserved as historical runner-rollout narrowing from before the pooled-substrate reset. It is not the active execution queue. Read its runner-promotion and active-rollout language as historical context only, not as the current product frame.

Snapshot date: 2026-04-22

Purpose

Refresh the active runner-rollout execution set after the broader tranche-2 note named a larger post-tranche-1 set.

The key question here is narrower than “what repos are interesting?”

It is:

• which repos still belong in the active runner-execution queue today
• which repos should stay named only as hosted or cache-acceleration surfaces
• which repo still carries the real runner-migration prerequisite

Inputs

• config/orgwide-enrollment-queue.json
• docs/current-state.md
• docs/cleanup-program.md
• docs/research/gloriousflywheel-broader-downstream-rollout-tranche-2-2026-04-22.md
• docs/research/gloriousflywheel-queue-c-migration-candidate-truthing-2026-04-18.md
• live gh repo view and gh api repos/<repo>/actions/runners checks on 2026-04-22
• live workflow-file reads for betterkvm, tinyclaw, remote-juggler, and tinyland.dev on 2026-04-22

Live Findings

tinyland-inc/betterkvm

• default branch is still sid/initial-scaffold
• repo runner inventory is still 0 accessible runners
• current workflow files on that branch are still:
  • .github/workflows/ci.yml
  • .github/workflows/release.yml
  • .github/workflows/secrets-scan.yml
• inspected jobs still run on ubuntu-latest
• ci.yml still carries the explicit comment: Switch to tinyland-nix when ARC runners are deployed

Decision:

• betterkvm remains the only real active runner-migration prerequisite in the current queue
• it stays named because the blocker is real platform reachability, not because the repo is already runner-enrolled

Jesssullivan/tinyclaw

• default branch is main
• repo runner inventory is 0 accessible runners
• .github/workflows/build.yml, pr.yml, release.yml, ghcr.yml, and upstream-sync.yml all still run on ubuntu-latest

Decision:

• tinyclaw is still fully hosted on main
• it should not stay in the active runner-promotion queue just because it is an active repo
• it only belongs back in the migration queue if there is an explicit product decision to move one authoritative lane onto ARC

Jesssullivan/remote-juggler

• default branch is main
• repo runner inventory is 0 accessible runners
• inspected workflow paths still run on hosted surfaces:
  • .github/workflows/ci.yml uses ubuntu-latest, ubuntu-24.04-arm, macos-latest, and macos-15
  • .github/workflows/nix-ci.yml uses hosted runners while consuming Attic
  • .github/workflows/release.yml, containers.yml, gtk-gui.yml, test-install.yml, and tofu-apply.yml are also hosted in the inspected paths

Decision:

• remote-juggler is still a hosted repo with real Nix and Attic acceleration
• it should be kept out of active runner-enrollment claims unless a specific authoritative lane is intentionally moved onto tinyland-nix
• this is runner-adjacent work, not current runner-rollout execution

tinyland-inc/tinyland.dev

• the repo still belongs in the named set because it shapes public rollout truth
• the Nix plus Attic builder path remains part of the product story while the broader Bazel, container, publish, and staging paths remain hosted by policy

Decision:

• tinyland.dev remains the named hybrid-by-policy boundary
• it is active rollout truth, but not a promotion candidate in the same sense as a repo that is about to move one authoritative lane onto ARC

Updated Execution Read

The active runner-rollout execution subset is now smaller than the broader tranche-2 naming note suggested.

Active Runner-Execution Set

• tinyland-inc/betterkvm
  • still the only real active runner-migration prerequisite
• tinyland-inc/tinyland.dev
  • still the named hybrid-by-policy boundary that keeps public rollout claims honest

Explicitly Outside Active Runner Execution

• Jesssullivan/tinyclaw
  • hosted by current policy
• Jesssullivan/remote-juggler
  • hosted plus cache-acceleration adjacent

These repos are still relevant to the broader product picture. They are no longer honest to describe as the next active runner-promotion targets.

Recommendation

Update the queue and canonical docs so that:

• promotion_candidates is empty until a real new candidate exists
• betterkvm remains the only active runner-migration prerequisite
• tinyland.dev remains explicit as hybrid-by-policy
• tinyclaw moves to keep_hosted
• remote-juggler moves to keep_hosted with cache-acceleration context

Exit Condition

This refresh can retire once one of the following becomes true:

• betterkvm proves a real self-hosted lane or is declassified
• tinyland.dev converges more of its authoritative path onto shared runners or stays explicitly hybrid-by-policy without ambiguity
• tinyclaw gets a deliberate runner-mode decision
• remote-juggler moves one authoritative lane onto ARC or is permanently treated as hosted plus cache acceleration