Environments

The operator builds a change once and promotes it through three environments before it reaches the mission. Development is the lab, training is the rehearsal, and operational is the live mission. A change earns its way forward one tier at a time, and nothing reaches operational that has not survived the two tiers below it.

The three are isolated from one another so a fault in one cannot reach the next. They also run a feedback loop, the operator instruments each tier, collects what it produces, and folds the result back into better tooling and sharper training.

        flowchart LR
  Dev["Development<br/>build and break"] --> Train["Training<br/>rehearse vs OPFOR"]
  Train --> Ops["Operational<br/>live mission"]
  Train -. "data, lessons" .-> Dev
    

Tiers

Each environment trades freedom for fidelity. Development is the most open and the least like the mission; operational is the most constrained and the most real; training sits between, close enough to the mission to rehearse against and walled off enough to fail safely.

Environment	Purpose	Access	Data
Development	Build and break tooling	Open to the operator	Synthetic, low sensitivity
Training	Rehearse and measure against OPFOR	Operators and OPFOR	Realistic, not live
Operational	Run the live mission	Tightest, need-to-know	Real, highest sensitivity

Development

Development is the operator’s lab. Tooling is built, broken, and rebuilt here at speed, with no path to anything live and no data worth protecting. The only goal is to make the capability work, so the environment stays disposable and a mistake’s blast radius stops at the bench.

Training

Training is the rehearsal tier, built to mirror operational closely enough that what works here works on the mission, while staying walled off from it. OPFOR plays the adversary, and the activity it generates is the point. The operator instruments the tier, collects the data OPFOR produces, and analyzes it to improve the tooling and sharpen the training before either reaches the mission. A capability that cannot hold up against OPFOR here does not ship to operational.

Operational

Operational is the live mission. Access is tightest, the data is real, and the tradecraft is genuine, so the environment changes slowly and deliberately. A change lands here only after it has cleared development and training, and the operator promotes it under the same review and audit trail every other tier inherits.

Mapping

The three are the operator’s names for tiers the rest of the section already describes by their industry terms. A pipeline promotes a change through them and a landing zone separates them by account.

Environment	Pipeline stage	Account
Development	Dev	Sandbox
Training	Staging	Non-prod
Operational	Production	Prod

References

• Landing Zones for the account boundaries each environment sits in.

• Resilience for the failure domains the operational tier needs.

• CI / CD for the pipeline that promotes a change through the tiers.

• Observability for the instrumentation behind the training feedback loop.

• Rehearsals and PCC/PCI for how a mission is rehearsed before contact.