Evidence ledger and exports
Understand immutable event evidence, content-digested exports, certificate envelopes, and retention requirements.
Evidence ledger and exports
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.
The Platform Host invocation/event ledger is the audit spine. Airlift projections are replayable views; they do not replace the source events. Large reports and provider outputs live in an artifact/evidence store and enter the ledger by immutable reference and digest.
Inspect and admit those references with fa evidence inspect and fa evidence admit.
Admission registers artifacts only: it cannot manufacture an Experiments verdict, a
Runway release result, a Radar observation, or a cutover decision. See live evidence
commands for the schema, App locations, and automation outcomes.
Evidence pack
airlift.evidence_export assembles the object or wave trail: governed events addressed
to the subject plus related object/wave events, policy revision, and current projection.
The export records its own key and SHA-256 report digest. That digest proves content
identity, not signer identity.
Migration certificate
The migration certificate is an Ed25519-signed envelope derived from admitted readiness evidence. Verify it independently with:
fa certificate verify migration-certificate.json --keys public-keys.jsonEvidence retention
Retain immutable references for the application build, deployment, source snapshot, provider runs, certificates, approvals, and observation windows used for each migration decision. Screenshots, mutable branch links, and dashboard state without a bounded observation window are supporting context only.