Levels 1 and 2

Planned. This page describes designed behaviour that is not built yet. Details may change before it ships.

Every app starts at level 0, with gliss.yaml only. A project moves up a level by adding files, never by changing tools.

Level	What you write	Checked against	Who it is for
0: Catalog	`gliss.yaml`	The catalog	Every builder
1: Composed	`gliss.yaml` plus `garden.yml` with Gliss action types	The same catalog	Apps with several services and their own tests
2: Custom	Your own Helm charts or manifests	IT’s policy	Engineering teams. IT enables it per project.

At levels 1 and 2 you work with Garden, the engine under Gliss. Start with Garden basics.

What is different from plain Garden

The project uses the gliss provider. A deploy becomes a signed release request; there is no kubeconfig.
Terraform and Pulumi actions, local mode and port forwarding are not available.
Live code sync is Git-backed and works in Preview only.
The action cache holds hashes and results only, never code or logs.