Cutover control room

Open Cutover control in the Airlift Databricks App after a wave has been frozen. The screen is a projection of governed state, not a second workflow or monitoring system.

Each wave card shows:

• the frozen scope digest and object count;
• runbook version, timed steps, owners, and rollback links;
• rehearsal and parallel-run verdicts;
• the exact certified effector generation and expiry;
• readiness blockers and open incidents;
• hypercare and source-disposition state.

If the frozen wave contains a development certificate, the card shows Development evidence and readiness remains blocked even after a successful rehearsal. This is the expected development endpoint. Independent certificates, an admitted deployment digest, a certified effector, and the required operational window must replace the development proof before production. See Development assurance.

The Start cutover action appears only when the evidence projection is ready and the wave is eligible. Submitting it starts or attaches to the same durable Temporal workflow used by fa cutover start. The workflow checks policy again, so stale browser state cannot bypass a gate.

Use Open incident whenever operational risk appears. The action immediately blocks production readiness. Resolve the incident through a governed command with evidence; closing a work item in an external system does not advance Airlift state.

After a completed wave and independent cutover-verification observation, Start hypercare pins the minimum observation deadline and acceptance criteria digest. Radar or an external monitor continues to own raw operational truth. Airlift records only the admitted reference and uses its verdict in migration policy.

For bulk configuration, CI, and evidence ingestion, use the cutover CLI.