Stacks

What a stack is, and what its claim means

A stack is a root module that composes modules already in the catalogue, wired in dependency order: the network first, then keys and identity, then the workloads that need them. Each component module keeps its own page, its own verification record and its own price, so a stack can be bought as a set or assembled a piece at a time from the same parts. There is no hidden glue: the source of the root is the wiring, and the wiring is what the live test of the root exercises.

The claim on each card is derived from the records, not written on the card. Root live-tested means the composed root itself was applied to a real account, asserted against and destroyed, so the wiring between the modules is covered by that evidence; 3 of the 6 stacks carry it today. All N modules live-tested means every component has passed that cycle on its own while the composed root has not been run as one apply, which is a weaker statement and is worded as one. A stack with neither says nothing rather than something softer.

Landing zones are the stacks a platform team arrives with a name for; the landing zones page walks through what each one provisions. For a single service across clouds, the solutions pages compare the component modules one at a time.