GloriousFlywheel GPU Proof Surface 2026-04-22

GloriousFlywheel GPU Proof Surface 2026-04-22

Snapshot date: 2026-04-22

Owner surfaces:

  • #320 / TIN-335
  • #338 / TIN-377
  • #333 / TIN-371
  • #44

This note records the current bounded GPU truth after the advanced-runner matrix landed and the first GitHub-first GPU canary was named explicitly.

The goal is not to claim a mature shared GPU runner product lane. The goal is to stop describing GPU only as stale GitLab-shaped backlog now that there is repeatable self-hosted GPU evidence in one named downstream repo.

Current Proof

  • repo: Jesssullivan/cmux
  • workflow: GPU Smoke Test (Self-Hosted)
  • run:
    • 24756928163 on main
  • commit:
    • f64a777
  • job:
    • GPU smoke test (cmux-nix) 72432003462
  • gate:
    • GitHub environment gpu-tests

The run completed success on main. The job logs show:

  • Build libghostty (Nix) success
  • Build cmux-linux (Nix) success
  • Test config parser (Nix) success
  • GPU smoke test success

This is not a metadata-only probe. It is a real self-hosted build-and-runtime smoke path on an authoritative branch.

Why This Counts

  • the proof is on an authoritative branch
  • the workflow runs on a named self-hosted GPU-capable lane: cmux-nix
  • the workload performs real build work before runtime validation
  • the runtime path is explicit and gated rather than ambient
  • the proof is GitHub-first rather than only GitLab-shaped module theory

Why This Is Still Bounded

  • the proof is repo-scoped to Jesssullivan/cmux
  • the workflow requires gpu-tests environment approval
  • GloriousFlywheel does not yet own a shared ARC or honey GPU lane with a default-branch contract
  • Dawn, WebGPU, and local NVIDIA-fabric follow-ons are still backlog and are not proved by the current cmux smoke

Current Product Boundary

The honest current claim is:

  • GPU now has one named repo-scoped GitHub-first proof surface
  • that proof surface is Jesssullivan/cmux GPU Smoke Test (Self-Hosted)
  • GloriousFlywheel still does not have a platform-owned shared GPU runner contract
  • #44 remains the broader Dawn / WebGPU / shared-GPU backlog slice

Next Decision

One of these should happen next:

  1. keep cmux as bounded repo-scoped proof and move to the next shared GPU promotion decision
  2. promote beyond cmux into a named shared honey GPU lane with operator docs and a real downstream canary
  3. split Dawn / WebGPU follow-on truthing into its own explicit proof surface

Until one of those happens, GPU should remain explicit but bounded in public docs and tracker surfaces.

GloriousFlywheel