Deployment stage
stage describes the cloud environment this checkout deploys to. The loop only ever reads it — it never creates, changes, or tears a stage down.
{
"stage": {
"resolve": "cat .sst/stage",
"productionStages": ["prod"]
}
}
| Key | Shape | Default | Purpose |
|---|---|---|---|
stage.resolve |
string or null |
null |
A command run from the repository root whose stdout is the stage this checkout deploys to. It must print one line, and print nothing (or exit non-zero) when there is no stage; every consumer reads empty as "no stage", never as an error. Keep it cheap — it runs on a timer. |
stage.productionStages |
string[] | [] |
The stage names that are production. No name is universal — one organization's is prod, another's is live — so listing a stage here is a claim that deploying to it affects real users. |
Most repositories have no stage, and null is the honest answer rather than a gap: doctor reports the block as not applicable rather than missing, and resolve: null records that somebody looked. Setup proposes a command from the shapes it finds — an SST, Serverless, Pulumi, or Terraform layout, or a *_STAGE variable — but never reports one as detected, because finding the tooling does not tell it how your checkout picks its stage.
Three consumers use it: /devstride:release names the stage at the production gate, so the owner approves a specific consequence; /devstride:branch-hotfix says which stage the checkout points at before touching a database and stops to ask when that stage is production; and the status line renders it, in red for a production name.
A stage is not a local environment
They are different axes, and both produce a per-checkout name, so the confusion is quiet.
localEnvironmentnames the local instance — this checkout's database, tables, and ports — and the loop owns its lifecycle.stagenames the cloud stack this checkout deploys to; several worktrees legitimately share one, and the repository's own deploy tooling owns it.