RFCs
GloriousFlywheel does not currently maintain a large standalone RFC archive.
Instead, active architecture decisions live as:
- short public decision summaries here
- focused GitHub issues
- deeper supporting notes in
docs/research/
Snapshot date: 2026-04-19
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:
honeyis the only physical cluster target- GitHub is the primary forge surface
- GitLab and Codeberg are compatibility surfaces, 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
- forge adapter boundaries are documented in Forge Adapter Matrix
Recently Landed RFC Lanes
#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:
- GitHub is the plainly stated primary surface
- GitLab and Codeberg are compatibility surfaces with caveats
- the active public boundary lives in Current State, Forge Adapter Matrix, and Adoption Quickstart
#213: Honey Runner Workspace Hygiene
This boundary is now landed in the primary docs:
honeyhosts 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 remaining repo-level sprint execution lanes in the canonical docs. Follow-on benchmark expansion and longer-tail platform work now live in backlog and product-positioning lanes instead of active sprint closeout.
Supporting Decision Notes
- Current State
- Bzlmod Topology
GloriousFlywheel Backend Target State 2026-04-16GloriousFlywheel Clean Derivation Promotion Workflow 2026-04-15GloriousFlywheel Nix Builder Bootstrap And Scaling Options 2026-04-16