Skip to main content
StackKits uses CUE as the source of truth for kit contracts. Your StackSpec is checked against that contract before artifacts are generated or a target is changed.

​
The workflow

Initialization creates a complete StackSpec for the selected kit. Validation checks that intent against the release’s CUE contracts. Generation then derives disposable rollout artifacts from the validated input. When a setting changes, update the StackSpec and repeat validation and generation; do not edit generated files directly.

​
Shared schema package

Kit contracts share the foundation CUE package, imported as github.com/kombifyio/stackkits/foundation. It defines #FoundationStackKit, the shared contract that platform and kit schemas extend with their own services and constraints. Published archives and the installer include the package as foundation/, with its shared kit contract in foundation/stackkit.cue.
Releases before v0.18.22 named this package base and exposed #BaseStackKit. Both names are retired. Kit authors and tooling must import github.com/kombifyio/stackkits/foundation and extend #FoundationStackKit.

​
Boundary

The standalone StackSpec describes StackKits intent. Provider credentials, provider lifecycle, and server procurement stay outside that contract. A StackKits workspace remains usable without a hosted kombify dependency.