Repository Boundaries¶

Public clarity depends on keeping each repository focused.

`productive-k3s`¶

Owns ecosystem explanation, public navigation, roadmap, quickstarts, and public-facing site content.

Owns the runtime and base installation engine, supported core addons, lifecycle scripts, and technical validation of the core platform.

Owns scenario assembly, infrastructure profiles, provisioning logic, OpenTofu and Ansible layers, and reusable infrastructure automation.

Owns the user-facing command line experience and should map users onto compatible core and infra bundles.

Owns optional integrations, experiments, and non-core extension paths.

Owns private or commercial profiles that should not be published through the public repositories.

If content explains the ecosystem at a public level, it likely belongs here.

If content documents implementation details, it should usually live in the repository that owns that implementation.