App walkthroughs
Annotated Airlift App screenshots with matching fa commands — the catalog companion to the guided migration journey.
Understand the App before running a migration
For the primary App-first walkthrough, follow the
guided migration journey: one synthetic Azure Synapse to
Databricks Lakehouse engagement, artifact by artifact, with the next action per phase.
This page is the annotated screenshot catalog that supports it — each image paired with
the fa commands that read the same governed projection.
Every screenshot in this documentation is an automated capture from a governed, public synthetic Airlift workspace. The images contain no client data, credentials, workspace hostnames, or internal deployment references. Select an image to open the full-size view.
Each annotated image answers two questions in text as well as visually:
- What you are seeing explains which governed projection or workbench produced the UI.
- What to do next names the developer action and evidence needed to continue.
The text is intentional. Screen readers, llms.txt, llms-full.txt, and developers who
cannot inspect the image receive the same workflow explanation.
1. Choose the migration
The engagement portfolio prioritizes migrations that need attention and exposes one recommended action per engagement.
Each card is a governed migration record, not a manually maintained project-status tile.
Open an engagement or create a new one, then follow its recommended action.
fa engagement list --json
fa engagement status "$ENGAGEMENT_ID" --json2. Read the evidence gates
Migration status is calculated from terminal governed evidence, with the first incomplete gate identified explicitly.
A blocker names the missing decision, artifact, validation result, or review that prevents the next gate.
Open the blocker action instead of editing the percentage or marking the phase complete manually.
fa engagement status "$ENGAGEMENT_ID"
fa residue list --engagement-id "$ENGAGEMENT_ID" --json3. Inspect the exact migration output
The artifact explorer answers which exact bytes are being validated, deployed, reviewed, and certified.
Airlift stores immutable references and digests, not source code bodies or credentials.
Open an artifact to inspect its lineage and copy the digest used by validation and release requirements.
fa artifact list --engagement-id "$ENGAGEMENT_ID" --json
fa artifact show "$ARTIFACT_ID" --json4. Validate independently
Validation requests object-specific checks and records independent Experiments evidence against exact artifact digests.
The laboratory separates validation evidence from the converter that produced the candidate.
Select converted objects and required evidence tracks, request validation, and resolve any discrepancies.
fa validation run --file validation-request.json \
--idempotency-key "$ENGAGEMENT_ID-validation-v1"
fa validation list --engagement-id "$ENGAGEMENT_ID" --jsonScreenshot transcript
The complete documented UI catalog covers these developer-visible states:
| Area | What the image proves | Developer action |
|---|---|---|
| Engagements | Scope, owner, phase, blockers, and next action are visible together | Choose or create the governed migration |
| Source workspace | Navigation exposes only sources attached to the engagement | Run and admit the source assessment |
| Discovery | Accepted inventory and dependencies have immutable digests | Review and accept scope |
| Planning | Target design and waves are bound to accepted inventory | Freeze the selected plan |
| Conversion | Attempts, residues, and target artifacts retain lineage | Repair residue and register output |
| Transfer | Watermarks, checkpoints, rejects, and reconciliation are visible | Complete restartable movement |
| Deployment | Airlift requirement is separate from Runway observation | Deploy the same digest with fr |
| Validation | Experiments evidence is independent of conversion | Resolve failed discrepancies |
| Assurance | Readiness tracks and certificates are evidence-derived | Complete missing tracks and acceptance |
| Cutover | Frozen scope, rehearsal, approvals, health, and rollback must agree | Execute only after the gate passes |
For a source-specific sequence, open Azure Synapse or SQL Server. Other source pages use clearly labeled representative workflow images until that source has its own admitted workspace evidence.
Guided migration journey (App walkthrough)
The primary App-first walkthrough of one Azure Synapse to Databricks Lakehouse migration — artifacts first, with one governed next action per phase.
Demonstrate an Azure migration
A developer-oriented demo script for presenting the Synapse and SQL Server Azure migrations with Airlift — visible artifacts, evidence boundaries, and next actions.