Deployment lifecycle

Defines rule deployment statuses, promotion strategy, proxy settings, and debug configuration. Shipped in bundled `deployment.toml`; clients MAY override via `.opentide/configurations/deployment.toml`.

Requirements

Every rule status value MUST match a configured status name in merged deployment.toml.
The set of statuses is configuration, not specification: implementations MUST NOT assume the bundled status names exist.
Status ordering is NOT normative. No transition graph is defined or enforced; any configured status MAY be set directly.
Status promotion MUST respect [promotion] settings when promotion.enabled is true.
Deprecated statuses MUST NOT be used for new rules (opentide emits warnings).
Platform-specific status on configuration blocks MUST also be valid deployment statuses when set.

Definition

Status entries (`[[statuses]]`)

Field	Type	Required	Description
`name`	string	yes	Status identifier (e.g. `STAGING`)
`description`	string	yes	Human-readable description
`strategy`	string	yes	Deployment strategy enum

Bundled statuses

Name	Strategy	Description
`DESIGN`	`INERT`	Under active functional design, without technical translation
`DEVELOPMENT`	`PREVIEW`	Under active technical implementation
`IMPROVING`	`PREVIEW`	Functionally qualified, undergoing refinement
`STAGING`	`PREVIEW`	Deployed in staging for operational testing
`ACCEPTANCE`	`PREVIEW`	Ready for production; analyst validates alert and playbook
`PRODUCTION`	`RELEASE`	Active production deployment
`DISABLED`	`DISABLEMENT`	Accessible but not active
`REMOVED`	`DELETION`	Fully deprecated, archival flag only

Strategy semantics

The strategy on a status determines what opentide deploy does with a rule in that status:

Strategy	Deploy behaviour
`INERT`	Rule is not deployed to any platform
`PREVIEW`	Rule is deployed to staging/preview targets only
`RELEASE`	Rule is deployed to production targets
`DISABLEMENT`	Any active deployment of the rule is disabled (kept but inactive)
`DELETION`	The rule is removed from platforms

Status changes and promotion

There is no lifecycle state machine. Statuses are a flat, configurable set: the only constraint enforced on a rule is that its status matches a configured status name. Any status MAY be set directly in YAML, in any order, and no transition is validated.

Promotion, when promotion.enabled is true, is a single jump — not a step along a progression:

Status strategy	Effect of promotion
`RELEASE`, `DISABLEMENT`, `DELETION`	Non-promotable; the status is left unchanged
Any other strategy (e.g. `INERT`, `PREVIEW`)	Rewritten directly to `promotion.promotion_target`

flowchart LR
  D["opentide deploy<br/>promotion.enabled = true"] --> Q{"status strategy"}
  Q -->|"RELEASE / DISABLEMENT / DELETION"| U["status unchanged"]
  Q -->|"any other strategy"| T["status := promotion_target<br/>(default PRODUCTION)"]

Intermediate statuses are not stepped through: a rule in the bundled DESIGN status promotes straight to PRODUCTION. Promotion rewrites the status values inside a rule's platform configurations blocks.

The bundled status names in the table above suggest an editorial workflow (design → build → stage → release → retire), but that ordering is convention only and applies solely to the bundled configuration. Clients that override deployment.toml define their own statuses, and any progression between them is enforced by their own process, not by OpenTide.

`[promotion]`

Field	Type	Default	Description
`enabled`	boolean	`true`	Whether status promotion is allowed
`promotion_target`	string	`PRODUCTION`	Default target status for promotion

`[proxy]`

Field	Description
`proxy_user`	Optional; use with `proxy_password` for auth
`proxy_password`	Optional proxy password (env var substitution supported)
`proxy_host`	Proxy hostname
`proxy_port`	Proxy port

When both proxy_user and proxy_password are present, authenticated proxy is used; otherwise host:port only.

`[debug]`

Field	Type	Description
`mdr_test_uuids`	list[string]	UUIDs of rules usable for debugging
`proxy_enabled`	boolean	Enable proxy in debug mode
`ssl_enabled`	boolean	Enable SSL in debug mode

Top-level

Field	Default	Description
`default_responders`	`""`	Default responder team when not set on rule

Relationships

rule-1.0.md — status field on rules and platform blocks
configuration.md — override mechanism
platforms.md — per-platform deployment
metaschema-keywords.md — tide.config.statuses keyword

Version	Date	Notes
1.0	2026-06-25	Initial spec from opentide `deployment.toml`