Compatibility Kit

Compatibility Kit

Snapshot date: 2026-04-19

Decision

The Bzlmod overlay compatibility kit lives in Jesssullivan/bzl-cross-repo, not in the main GloriousFlywheel repository.

This decision only covers legacy symlink-merge and downstream-consumer compatibility mechanics. It did not create the Tinyland or Jess Honey implementation-overlay authority candidates now being repaired in tinyland-inc/tinyland-infra and Jesssullivan/jesssullivan-infra, and it should not be read as replacing that owner-specific authority boundary.

GloriousFlywheel retains the attic-iac module name in MODULE.bazel for internal build structure and backward compatibility. It does not publish the full platform as a Bazel Central Registry module during this sprint.

What The Kit Covers

  • Legacy Bzlmod overlay patterns for downstream consumers
  • local_path_override development flows
  • Downstream merge-and-modify examples
  • Transitional consumers and historical overlay references such as older tinyland-infra material

What It Does Not Cover

  • Primary onboarding for new adopters (use the adoption quickstart instead)
  • Multi-forge enrollment (use forge adapters)
  • Cache or runner configuration (use the core substrate docs)
  • Current owner implementation authority for Tinyland or Jess Honey

Why

The overlay-first adoption story created too much conceptual flattening. It made local overrides and merge mechanics feel more central than the runner, cache, and cluster truth. The clearer story is: deploy core, enroll forge, choose pools, attach caches, customize policy.

Migration Path

Existing overlay consumers should:

  1. Continue using bzl-cross-repo for Bzlmod composition
  2. Migrate configuration to direct OpenTofu variable overrides
  3. Treat the compatibility kit as transitional, not permanent

Separately, GloriousFlywheel still needs to finish promoting and proving the current implementation-overlay authority candidates before live state is rehomed or repo-shaped residue is torn down.

GloriousFlywheel