Databricks-native commands

Use fa databricks-native when the customer already runs Databricks. This is not a pretend migration from an external system. The source estate is databricks, and the program starts from an immutable current-state baseline.

Register the source profile

fa source inspect databricks
fa source plan databricks --variant databricks_unity_catalog

Available variants are databricks_unity_catalog, databricks_workspace_consolidation, and databricks_cost_performance.

Create the native manifest

{
  "schemaVersion": 1,
  "estate": {
    "name": "Analytics platform",
    "variant": "databricks_unity_catalog",
    "workspaceRefs": ["workspace://analytics-prod"],
    "snapshotAt": "2030-01-15T12:00:00.000Z"
  },
  "reason": "unity_catalog_upgrade",
  "baselineEvidenceRef": "evidence://experiments/native-baseline-v1",
  "assets": [
    {
      "assetId": "sales-database",
      "name": "Sales Hive database",
      "kind": "hive_metastore_object",
      "dependencies": [],
      "owner": "sales-data",
      "currentStateDigest": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "issues": ["Uses workspace-local storage paths."],
      "metrics": { "tables": 42 }
    }
  ]
}

Inventory may cover workspaces, metastores, Hive Metastore objects, Unity Catalog assets, jobs, pipelines, notebooks, warehouses, clusters, policies, permissions, dashboards, models, endpoints, shares, lineage, cost observations, and operational dependencies. Store identities, digests, aggregate metrics, and issues—not credentials or raw client data.

Typed reasons include Unity Catalog upgrades, workspace consolidation, permission and path modernization, serverless or Lakeflow adoption, Delta and liquid clustering, runtime upgrades, dashboard transitions, and cost/performance optimization.

Inspect and plan

fa databricks-native inspect --file native-manifest.json
fa databricks-native plan \
  --file native-manifest.json \
  --json > native-plan.json

Every asset becomes a deterministic, advisory, or human recommendation. The plan requires baseline behavior, allow-and-deny permission tests, performance and cost guardrails, immutable release and rollback evidence, an operational observation window, and owner acceptance.

Register

fa databricks-native register \
  --file native-plan.json \
  --engagement-id <engagement-id> \
  --estate-id <estate-id> \
  --artifact-id <immutable-artifact-reference> \
  --idempotency-key <stable-key>

The plan records the family execution contract:

• Airlift owns the baseline, modernization intent, recommendations, evidence references, promotion policy, and value record.
• Harness may produce bounded advice or repair candidates.
• Experiments owns A/B, BDD, parity, performance, and cost evaluations.
• Runway owns preview, deployment, promotion, reconciliation, and rollback.
• Radar owns operational observations.
• Tower owns work references.
• Platform owns governed mutations and audit.

Use fa to inspect Airlift migration/modernization status and request governed changes. Use fr to execute releases. Airlift may block on Runway or Radar evidence; it never copies their state or provides a second deploy command.