RFCs

RFCs

GloriousFlywheel does not currently maintain a large standalone RFC archive.

Instead, active architecture decisions live as:

  • short internal decision summaries here
  • focused GitHub issues when a fresh repo-level slice is intentionally reopened
  • deeper supporting notes in docs/research/
  • a future public projection under public-docs/ rather than in the full internal docs tree

Snapshot date: 2026-04-29

Use Cleanup Program when the question is sequencing or workstream structure rather than architecture boundary.

In Effect

These decisions are already part of the current repo and runtime contract:

  • honey is the only physical cluster target
  • GitHub is the primary forge surface
  • GitLab is the current compatibility runner surface; Woodpecker/Codeberg remain future adapter work, not equal-maturity control planes
  • Nix bootstrap on self-hosted Nix lanes is workflow-owned
  • ARC scales runner count horizontally, not one runner pod’s memory envelope
  • heavy Rust and Nix workloads should use tinyland-nix-heavy
  • Attic and Bazel are acceleration layers, not publication surfaces
  • FlakeHub is not part of the active runtime or bootstrap contract
  • release tags publish the tagged flake and the documented GHCR image set
  • repo identity is not runner taxonomy; capability classes are the product contract
  • implementation overlays own owner-specific GitHub App media, tfvars, backend coordinates, private anchors, and stable core pins
  • owner-distinct ARC scale-set names are auth/registration identities, not workflow labels and not a global capacity policy
  • stateless Docker-capable CI can use sting as compute-expansion relief, but kube-API mutation workflows such as ARC plan/apply remain honey-bound until sting control-plane reachability is proved
  • public alpha currently means a scrubbed fresh-history export, not a direct full-repo visibility flip
  • source-repo dogfood proves shared cache acceleration; it does not yet prove universal full remote offload for every developer workload
  • Bazel remote execution now has a narrow explicit //app:build proof through the GF REAPI cell, but it is not selected as the default product path; Buildbarn, Buildfarm, BuildBuddy, and NativeLink remain peer projects / possible spike targets, not GloriousFlywheel dependencies
  • forge adapter boundaries are documented in Forge Adapter Matrix

Recently Landed RFC Lanes

Public Alpha Export And Visibility Boundary

This boundary is now landed in the primary docs and tooling:

  • PR #419 added the scrubbed public-alpha export seed
  • just public-alpha-export-check and just public-alpha-export are the safe fresh-history mirror route
  • direct full-repo visibility remains blocked until history/current-tree disposition is recorded
  • TIN-551 is complete, but direct visibility is still a separate gate

Implementation Overlay Boundary

This boundary is now landed in the primary architecture docs:

  • PR #420 restored the implementation-overlay boundary and guarded destructive ARC cleanup
  • PR #422 added the implementation-overlay workstream and enrollment-preflight surface
  • tinyland-inc/tinyland-infra and Jesssullivan/jesssullivan-infra are the current owner-overlay authority candidates
  • overlay CI validates registration and cache/auth reachability, not final live state authority
  • live state movement still requires stable core pins, backend credentials, and explicit rehome or teardown decisions

#215: FlakeHub Publication And Discovery

This boundary is now landed in the primary docs:

  • FlakeHub remains a publication and discovery surface, not runtime/bootstrap
  • release-tag scope is documented in Release Baseline
  • builder-side publication guidance lives in the clean-derivation and release notes, not in the runtime contract

#211: GitHub-First Product Boundary

This boundary is now landed in the primary docs:

#213: Honey Runner Workspace Hygiene

This boundary is now landed in the primary docs:

  • honey hosts may be long-lived, but _work/<repo> trees are disposable scratch
  • bounded audit and remediation now live in the operator-facing runbook, troubleshooting guide, and justfile reference
  • lifecycle and escalation rules now live in Honey Runner Workdir Contract

Active Execution Lanes

There are no broad legacy sprint execution lanes in the current canon. The active development flow is intentionally narrow:

  • keep management-truth cleanup green before the next feature slice
  • keep the public-alpha export route green while direct full-repo visibility remains blocked
  • promote Tinyland/Jess implementation-overlay authority without changing workflow labels into owner or repo taxonomy
  • resolve current operational debt: shared-label global capacity policy, implementation-overlay state rehome, TIN-758 developer-machine Bazel cache exposure policy, Bazel external repository fetch authority, bumble kubelet/imagefs capacity separation, and live compatibility-residue disposition. The April 29 ARC runtime/CNI checkpoint is complete; future broker/session continuity incidents should reopen from fresh runtime evidence.
  • keep the May-Aug RBE sprint gated by target eligibility, backend architecture, and product wrapper decisions before implementing NativeLink-shaped tasks or expanding public docs to claim broad remote build
  • route Docker-capable downstream image publication through shared capability labels and owner-overlay registration, not repo-shaped labels such as a permanent massageithaca-dind lane
  • defer native aarch64, riscv, Dawn/GPU, localized warm-cache guarantees, and advanced runner classes until each has a named proof surface and bounded owner

Supporting Decision Notes

GloriousFlywheel