Doors onto DoD cloud
You are not choosing a cloud. You are choosing whose landing zone you occupy.
An on-prem midsize agency has four honest doors. Phase Zero names one. Nothing migrates in those six weeks. Hygiene is why programs stall. Occupancy is the point.
The fork
Named AO, impact level, residual controls, handling path, 03:00 owner. Join does not sign the ATO.
Local provider
They build on a known pattern. They do not get a unique road.
An integrator or regional partner may stand the LZ or factory. They contract for occupancy on ECMA / Cloud One / Platform One / Black Pearl / OEM government-region patterns. They do not get a unique architecture because 'our mission is different.'
Residual and the AO stay the agency's.
Not this
Occupancy is an AO signature, not a go-live slide.
- Not A CSP bake-offFour primes are a vehicle catalog. First occupancy is one partition.
- Not The migrationPhase Zero names the door. Waves wait on hygiene, IATT, then ATO.
- Not An ATONo program, CLIN, or provider signs residual risk for this mission.
- Not ThunderdomeHow people arrive. Not whose landing zone you occupy.
Phase Zero
Name the door. Do not occupy it.
Named fork on the Cloud Foundation Team charter: join, stand-up, hybrid. Vehicle (CLIN) named. Local provider named only if stand-up, and only on a known pattern.
The sponsor leaves able to say which door, whose residual, and who is 03:00. They do not leave with occupancy.
The road does not change. Position on it does.