GloriousFlywheel Orgwide Enrollment Queue 2026-04-18

Snapshot date: 2026-04-18

Purpose

Turn the orgwide enrollment reality check into an execution queue.

This note is the operational follow-on to:

The goal is not to migrate “all recent repos.” The goal is to:

protect the credibility of the platform claim
promote the highest-leverage template and hybrid surfaces
avoid wasting rollout energy on repos that should simply stay hosted or stay out of the runner-adoption denominator

Starting Point

From the 2026-04-18 live scan:

88 recent non-fork repos across tinyland-inc and Jesssullivan
47 have no Actions workflows
41 have workflow files
only about 15% of the downstream workflow surface currently shows real runner enrollment on default branches
that rises to about 18% if the MassageIthaca dev/main authority branch is counted

That means the next queue should optimize for credibility and leverage, not coverage theater.

Queue Design Rules

1. Do Not Count Everything That Mentions A Runner

These are not the same thing:

real shared ARC lanes on the authority branch
repo-owned dedicated lanes on the authority branch
raw [self-hosted, ...] compatibility or hardware jobs
hosted reusable workflow consumers
branch-gated or product-branch-only adoption

2. Do Not Spend ARC Budget On Repos That Do Not Need It

Some repos should remain:

no-workflow repos
tiny utility repos
hardware-only repos
docs/publication repos
one-off experiment repos

Those repos should not distort runner-enrollment metrics.

3. Fix Claim-Breaking Hybrids Before Chasing New Logos

The current biggest reporting risk is not lack of repo names. It is hybrid repos being spoken about as if they were clean platform adopters.

Queue A: Claim Protection

These repos should move first because they shape whether the platform claim is currently honest.

`Jesssullivan/MassageIthaca`

Problem:

dev/main is the live repo-owned runner proof after #189
GitHub default branch is still main
an orgwide default-branch census therefore understates the repo and creates reporting ambiguity

Required action:

either move the authoritative branch boundary into a documented stable state
or stop using default-branch-only language when citing MassageIthaca

Exit condition:

MassageIthaca counts cleanly in adoption reporting without branch caveats

`tinyland-inc/tinyland.dev`

Problem:

real tinyland-nix use exists
authoritative Bazel, publish, and staging-deploy paths remain hosted

Required action:

decide whether tinyland.dev is meant to be:
- a runner dogfood repo
- a cache-only repo
- a permanently hybrid repo

Exit condition:

the authoritative CI and deploy story matches the public claim

`Jesssullivan/XoxdWM`

Problem:

the non-fork repo in the denominator is Jesssullivan/XoxdWM
but the self-hosted fast path is currently gated to tinyland-inc/XoxdWM
Jesssullivan/XoxdWM now has USE_SELFHOSTED=true
both repo surfaces currently report 0 accessible runners
many workflows still fall back to hosted
hardware jobs still use raw [self-hosted, honey] on that fork-shaped path

Required action:

define one canonical authority repo surface with real runner inventory
near-term, either restore accessible shared runners on the Jess repo or turn the toggle back off until they exist
then make the Jess repo itself the real shared ARC path
treat any later move to tinyland-inc/XoxdWM as a separate ownership migration after repo convergence
quarantine hardware and compatibility lanes as explicit exceptions

Exit condition:

the repo can be described without activation-mismatch hand-waving

`Jesssullivan/yt-text`

Problem:

strong downstream shared-runner canary
docs and fuzz still escape to hosted

Required action:

treat the GitHub Pages deploy path as a durable GitHub-native exception
make an explicit keep-hosted versus migrate decision for fuzz
stop implying that both hosted paths are the same kind of problem

Exit condition:

yt-text is either cleanly hybrid-by-policy or more fully converged

Queue B: Template Contract Cleanup

These repos matter because they let one fix move several packages at once.

`tinyland-inc/tinyvectors`

Problem:

it now explicitly uses js-bazel-package.yml in hosted mode
that means it is no longer ambiguous, but it also should not be counted as a runner-enrolled repo

Required action:

stop treating it as an unresolved classification problem
only move it again if the repo is intentionally promoted from hosted to shared or repo_owned

Exit condition:

tinyvectors is either intentionally left hosted or migrated through an explicit promotion PR

Hosted `npm-publish.yml` Family

Repos:

tinyland-inc/vite-plugin-a11y
tinyland-inc/tinyland-rate-limit
tinyland-inc/tinyland-physics
tinyland-inc/tinyland-color-utils
tinyland-inc/tinyland-a11y-engine

Problem:

these repos consume ci-templates
but the workflow they consume is still hosted
they are easy to overcount if the metric is “template usage”
all five repos are also archived

Required action:

classify this whole family as hosted template consumers outside the active migration queue
keep them visible in template-mode reporting, but stop treating them as a current enrollment debt surface

Exit condition:

template metrics no longer masquerade as runner metrics
the archived package family is no longer described as an active migration set

`tinyland-inc/ci-templates`

Problem:

the recent V2 work improved js-bazel-package.yml
but the template surface still spans both hosted and self-hosted package families

Required action:

keep the reusable-workflow capability matrix current
treat js-bazel-package.yml as the only current runner-flexible workflow
treat npm-publish.yml as hosted-only unless its contract changes

Exit condition:

template adoption can be reported by mode instead of by raw repo count
reusable workflow capability is no longer spoken about as one fuzzy surface

Queue C: Real Migration Candidates

These repos are active enough to matter, but they are not yet real runner enrollments.

`tinyland-inc/betterkvm`

Reason:

active
explicit hosted pin still exists on the live default branch
default branch is still sid/initial-scaffold
good candidate for tinyland-nix promotion only after branch intent is less transitional

Required action:

normalize branch authority, then replace the hosted Nix runner pin with real shared ARC use

`Jesssullivan/tinyclaw`

Reason:

active
fully hosted on the scanned branch
no current evidence that it is already runner-adjacent
should not stay in the queue by inertia alone

Required action:

make an explicit keep-hosted versus migrate decision

`Jesssullivan/remote-juggler`

Reason:

active
still overwhelmingly hosted
currently better described as build-acceleration or cache-adjacent than runner-enrolled

Required action:

either migrate one authoritative lane to ARC
or stop discussing it as part of the current runner story

Queue D: Keep Hosted And Keep Out Of The Metric

These repos should not currently consume rollout attention.

Examples:

Jesssullivan/jesssullivan.github.io
Jesssullivan/server-fan-splitter-pcb
Jesssullivan/modular-atx-power-rack
Jesssullivan/zig-notify
Jesssullivan/hiberpower-ntfs
Jesssullivan/zig-ctap2
Jesssullivan/re-ems
Jesssullivan/zig-keychain
Jesssullivan/zig-crypto
tinyland-inc/tinyland-auth-pg
tinyland-inc/crs310-8g-2s-in
tinyland-inc/tinyland-auth-redis
tinyland-inc/huskycat-gl
tinyland-inc/network-topology
tinyland-inc/waifu-mirror

These repos are not “failures.” They are simply not where the platform should spend enrollment energy today.

Immediate Work Order

Recommended order:

MassageIthaca make branch authority and reporting line up
tinyland.dev decide whether it is a runner repo or a cache repo
XoxdWM separate canonical ARC from hardware and hosted fallback
yt-text either finish convergence or formalize hybrid exceptions
template mode reporting apply the enrollment scoreboard contract so hosted, shared, and repo-owned template consumers stay visible in one table
npm-publish.yml family choose hosted-by-policy versus self-hosted promotion
betterkvm promote or declassify
tinyclaw promote or declassify
remote-juggler promote or declassify

Weekly Scoreboard To Track

Do not track only raw repo count. Track these instead:

recent non-fork repos
recent repos with workflows
recent downstream repos with real shared ARC authority paths
recent downstream repos with real repo-owned authority paths
recent downstream repos with explicit authority exceptions
recent hosted-only workflow repos
template consumers by mode:
- hosted
- shared
- repo-owned
authority exceptions count

Honest Near-Term Target

The next useful target is not “most repos.”

The next useful target is:

make every repo currently cited in platform claims defensible
make every template consumer mode explicit
reduce the number of hybrid repos that are being spoken about as if they were homogeneous

That would materially improve the truthfulness of the GloriousFlywheel story without pretending the org is already broadly enrolled.