Production readiness

Airlift separates installed capability from project readiness. A successful build or configured connector does not prove that a source estate is safe to migrate.

Installation checks

The installation must prove:

• authenticated actor and organization derivation;
• fail-closed authorization and cross-tenant denial;
• durable event, projection, idempotency, and recovery behavior;
• secret-backed evidence signing and public-key verification;
• Lakebridge job and artifact-store connectivity;
• Temporal workflow replay, cancellation, timeout, and restart behavior.

Run the structural diagnostic first:

fa doctor --profile production

doctor validates configuration shape. Connectivity and behavior require integration and deployment tests.

Source-profile checks

For the selected source, retain evidence for:

• accepted inventory, dependencies, exclusions, and source version;
• representative deterministic conversion and residue classification;
• snapshot and incremental transfer, watermark, restart, lag, and reconciliation;
• object-specific functional, data, security, and performance scenarios;
• business-owner acceptance of the selected validation profile.

Generate the source-specific checklist with:

fa source plan <source>

Automated cutover checks

Do not enable automated cutover until the target-specific effector proves:

1. a durable pre-effect checkpoint;
2. one non-idempotent apply attempt;
3. independent observation of the resulting external state;
4. explicit handling of verified, not_applied, failed_applied, and uncertain outcomes;
5. one compensation attempt after a definitively failed applied effect;
6. a frozen scope, timed runbook, passing rehearsal, and unexpired matching effector certification;
7. passing parallel-run evidence and no open incidents.

Projects that do not provide and certify this effector can use an approved manual procedure while Airlift records scope, approvals, evidence, outcome, and rollback state. Automated production cutover remains disabled for that project.

Claim language

Use precise terms in project documentation:

• configured means required settings are present;
• connected means the external boundary completed an authenticated smoke test;
• validated means the named scenarios produced immutable admitted evidence;
• certified means Airlift minted a signed certificate from the active profile;
• cut over means the external effect was independently verified and recorded.

Do not use one term as a substitute for another.

Modernization and value checks

Before promoting a modernization release, prove that its baseline migration certificate is still active, the separate Runway deployment reconciled to the intended artifact, the Experiments comparison passed every functional guardrail and declared outcome metric, and the promoter is separate from the recommender and decision-maker.

Before publishing measured value to a client, retain at least three scoped observations and achieve medium or high computed confidence. A new observation makes an earlier summary stale. Engagement results are not universal product claims.