Multi-Repo Layout

Multi-Repo Layout

This document describes the repo layout that matters today, plus the older compatibility-era layout that still explains some surviving files and docs.

Current Primary Layout

Current Repository Roles

GloriousFlywheel

  • Host: GitHub (tinyland-inc/GloriousFlywheel)
  • Role: primary source of truth for the runner platform, cache surfaces, dashboard, and operator tooling
  • Current deployment target: the honey cluster
  • Current product boundary: GitHub-first, tailnet-first, local-first from this repo

Downstream Consumers And Canaries

  • Examples:
    • tinyland-inc/lab
    • tinyland-inc/tinyland.dev
    • tinyland-inc/blahaj
    • Jesssullivan/XoxdWM
    • Jesssullivan/yt-text
  • Role: prove the shared runner contract, bootstrap rules, cache contract, and migration kit on real repos outside GloriousFlywheel itself

Compatibility Surfaces

The repo still contains compatibility paths for:

  • GitLab-oriented runner and dashboard control paths
  • Codeberg and cross-forge documentation
  • historical overlay-oriented deployment notes

These are not the primary operating model anymore.

Current CI And Deployment Flow

  1. Work is developed and applied from this repo.
  2. The operator path is local-first via just tofu-init, just tofu-plan, and just tofu-apply.
  3. honey is the only physical cluster target.
  4. Downstream repos consume runner labels, composite actions, and shared cache conventions from GloriousFlywheel.

Historical Overlay And GitLab Context

Earlier versions of the system were organized around:

  • a public upstream repo
  • private overlays
  • GitLab-driven CI and HTTP state
  • mirrored or forwarded GitHub-to-GitLab repository flows

That context still matters for:

  • reading older docs
  • understanding compatibility paths
  • interpreting the surviving archived gf-overlay state surface

It should not be treated as the current primary repo layout.

GloriousFlywheel