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.

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 such as tinyland-infra

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)

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

GloriousFlywheel