Philosophy

Design for composition, not isolation

Rules are not built as standalone artifacts. They are designed as cells that intentionally fit together:

• Shared conventions
• Predictable metadata flow
• Compatible tagging and labelling strategies
• Explicit integration surfaces

The goal is not maximal flexibility through abstraction, but intentional composability through design.

Encode real patterns, not just capabilities

Slash2-3Dot prioritises practical workflows over theoretical completeness. If a pattern is common in production, it is a first-class design concern — not an exercise left to the user.

Examples include:

• Bazel + Helm pipelines
• Post-rendering and metadata injection
• Building air-gapped artifacts for Packer or offline environments
• Reproducible packaging for infrastructure and application delivery
• Bridging Bazel outputs into existing deployment ecosystems

Opinionated, but pragmatic

The system encodes preferred patterns, standardises how common problems are solved, and reduces decision fatigue. Opinions exist to reduce friction, not enforce purity. The system favours:

• Explicit configuration over magic
• Predictability over cleverness
• Clear escape hatches when needed

Examples are products

Tutorial and reference repositories are not documentation afterthoughts. They are:

• Canonical demonstrations of intended usage
• Integration proofs across multiple rule sets
• Living design constraints that shape future development

A rule set is incomplete if it cannot be demonstrated as part of a larger, coherent system.