Every entity, event, and logic block you build lives in your Development environment first. Promoting to Production is an explicit, reviewable step — nothing you build goes live automatically.
The three real states
- Active — what's currently live in that environment.
- Staged — a version queued to become active, not yet promoted.
- Prev — the version that was active before the last promotion, kept for one-step rollback.
Three states, not four
There's no separate "deleted" version state to reason about — removing a staged version, or an api definition entirely, is a real, immediate deletion, not a fourth lifecycle stage.
Promoting development to production
Production must be provisioned first
Publishing to an org with no Production environment yet returns a clear error rather than silently failing — provision Production (via a plan upgrade, see Billing & plans) before your first promotion.
No contract tests or mock generation exist
If you're picturing an automated contract-testing or mock-generation step as part of this pipeline — that's not a real, shipped feature here. Diff, publish, activate, and rollback are the whole flow; verification of a promotion is a manual review of the diff.