gait-capture-runpack

To capture and verify a deterministic runpack for CI gate failures, provide a normalized run_record.json as input. The workflow runs gait run record to generate a verifiable bundle and manifest digest, then executes gait verify to produce a final handoff block for incident triage.

A runpack manifest digest is a verifiable cryptographic output generated from a normalized run record. You need it during incident triage and audits to prove runpack integrity and ensure the executed artifacts match the expected deterministic build.

You generate a ticket-ready handoff block by processing a run_record.json through gait run record and gait verify. The resulting output includes the run_id, bundle, manifest_digest, and a ticket_footer for immediate handoff to external teams.

The runpack verification workflow requires no external dependencies. It operates independently using a normalized run_record.json input and the gait command-line tool to execute the record and verify operations for artifact generation.

The best way to audit runpack integrity across CI pipelines is to generate a verifiable bundle and manifest digest for each run. Capturing deterministic runpacks provides auditable artifacts that confirm whether pipeline executions match expected build criteria.

Runpack verification fails without a normalized run_record.json because the gait run record command requires a structured input to accurately generate the bundle and manifest digest. Ensure your run record conforms to the expected normalized format before execution.