Fabric family integrations
Fabric family composition
Use Airlift with Platform, Harness, Experiments, Runway, Radar, and Tower without duplicating state ownership.
Fabric family composition
The governing law is simple:
Airlift may block on sibling state; it never re-owns it.
| Product | Owns |
|---|---|
| Airlift | scope, readiness, waves, certificates, cutover policy, migration ledger |
| Platform | governed mutations, authorization pipeline, invocation and audit spine |
| Harness | bounded agents and Databricks execution plumbing |
| Experiments | parity, BDD, evaluation, and quality evidence |
| Runway | immutable release deploy, promote, reconcile, rollback |
| Radar | operational observations, anomalies, and intervention evidence |
| Tower | work, tasks, assignments, and human coordination—not migration truth |
Composition uses stable foreign references, digests, idempotency, and reconciliation. Runway, Radar, and Tower are optional. When a sibling is absent, configure an admitted external evidence provider for the required observation or mark the corresponding track not applicable through the versioned validation profile. Never create a look-alike sibling state model inside Airlift.