Live evidence commands
Inspect, admit, query, and export immutable migration evidence without copying provider verdicts or secrets into Airlift.
Live evidence commands
Airlift admits immutable artifact references into the migration ledger. It does not turn a JSON file into a validation verdict, deployment result, or cutover authorization. Fabric Experiments, Runway, Radar, and client-approved adapters retain ownership of their results; Airlift stores their identifiers, content digests, producer generations, and lineage.
1. Inspect before admission
fa evidence inspect live-evidence.json
fa evidence inspect live-evidence.json --json > .airlift/evidence-inspection.jsonInspection is local. It validates the secret-free schema, timestamp order, source identity, run references, artifact digests, and disallowed credential-like keys. A historical failed run remains valid evidence—it is reported as failed rather than erased.
2. Admit artifact references
fa evidence admit \
--file live-evidence.json \
--engagement-id <engagement-id> \
--estate-id <estate-id> \
--idempotency-key source-workspace-run-v1 \
--json > .airlift/evidence-admission.jsonThe command invokes the governed airlift.artifact_register action once for the manifest
and once for each referenced artifact. It records no file bodies and no credentials. The
JSON result includes providerVerdictsAdmitted: false; provider evidence must still enter
through its admitted principal and policy path before readiness can pass. Artifact
admission cannot manufacture an Experiments verdict.
3. Inspect the admitted ledger
fa evidence list --engagement-id <engagement-id>
fa evidence show <artifact-id> --json
fa artifact list --engagement-id <engagement-id>In the Databricks App, open Engagements → active engagement → Artifacts for immutable references and Runs for assessment, conversion, transfer, deployment, and validation execution references.
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.
The run ledger links provider-owned executions to the governed engagement without copying their internal state.
A provider success remains evidence to evaluate; it does not automatically advance Airlift readiness.
Open the relevant run reference and verify that its digest, scope, producer, and verdict match the gate.
4. Export governed evidence
fa evidence export \
--file evidence-export.json \
--idempotency-key wave-evidence-export-v1An evidence export is a content-digested view of the governed event trail and current projection. The digest proves byte identity; only a valid signing envelope proves signer identity. Retain the export with the application build, source snapshot, provider runs, certificates, approvals, and observation windows that supported the decision.
Automation outcomes
| Exit | Meaning |
|---|---|
0 | schema inspection, admission, query, or export request succeeded |
1 | the governed action or policy rejected the request |
2 | command usage or the local manifest is invalid |
4 | the requested remote resource was not found |
6 | authentication, transport, or service availability failed |