Generated capability catalog

This page is generated from the versioned Airlift SDK contracts during every documentation build. Do not edit it manually. It describes identifiers and declared developer routing; it does not claim that a provider is installed or certified in your organization. Query the tenant capability registry for evidence-derived coverage.

Capability identifiers

Proof levels

1. contract_only
2. hermetic_proven
3. workspace_proven
4. client_proven
5. production_certified

Supported preflight targets are assessable, executable, certifiable, cutover_certified.

Delivery modes

• unavailable
• not_applicable
• external
• human
• automated
• mixed

An external, human, or mixed route still requires current evidence for the pinned provider generation. not_applicable is a governed disposition, not an omitted test.

Automation dispositions

• deterministic
• agent_repairable
• human_remediation
• retain_or_federate
• replace_native
• retire
• excluded
• unsupported

Independent required-construct denominator

Contract version: 1.

Only variants in this table can advance beyond cataloged. Every required construct must join to exactly one current, source-version-matched registry-v2 cell at the target proof level. Missing contracts, missing cells, duplicates, stale evidence, version mismatches, and unavailable execution routes fail closed.

Declared validation profiles: airlift.database_object.baseline, airlift.data_asset.baseline, airlift.orchestration.baseline, airlift.notebook_script.baseline, airlift.spark.baseline, airlift.kql.baseline, airlift.security.baseline, airlift.networking.baseline, airlift.consumer.baseline, airlift.operational_dependency.baseline, airlift.data_movement.baseline.

Construct-scoped cells (registry v2)

Registry-v2 cells add constructScope with construct, artifactKind, targetPattern, automationDisposition, optional sourceVersion, and optional documentationReference. The program term known_constraints maps to the replay-safe limitations field; required_validation_profile maps to validationProfileIds.

A construct cell proves only the named source construct. One cell never raises the whole source variant's derived support level or clears engagement preflight by itself; advancement requires the complete independent denominator and every mandatory lifecycle capability.

Repository construct routing

This repository-owned catalog is the normalization and routing contract consumed by assessment, conversion, artifact admission, the API, the App, and fa source constructs. It reports implementation status only. It does not report provider installation, execution, validation, or proof.

Databricks target-integration states

These construct-independent, source-independent integrations are declared identifiers. Declaring one does not configure, connect, observe, or prove anything. They are not MigrationCapability members and never aggregate into a source variant's derived support level.

Every Airlift surface renders exactly one observed state per integration:

Configuration, an environment variable, a catalog declaration, a screenshot, dashboard state, model output, and caller-declared metadata never raise proof and never render as observed. Dashboards, Genie, model output, screenshots, and provider configuration have no mutation, approval, waiver, certificate, deployment, cutover, or proof authority.

Source and variant identifiers

Static implementation routing describes shipped developer workflow breadth; it is not workspace or client proof. Only the authenticated capability matrix can render an organization's current, evidence-derived state.

Runtime checks

fa source doctor synapse --variant synapse_dedicated_sql
fa source constructs synapse --variant synapse_dedicated_sql
fa source limitations synapse --variant synapse_dedicated_sql
fa source certify synapse --variant synapse_dedicated_sql --level certifiable
fa engagement preflight eng_<id>

These commands query the authenticated organization registry. source certify is a fail-closed readiness check; it does not mint a migration certificate or promote a provider claim.