Flight Core Traceability

Flight Core traceability keeps source, compiler, artifact, firmware, and

evidence-bundle rows connected by stable trace IDs.

The machine-readable table is space/flight-core-traceability.tsv.

Trace Stages

The S1 gate requires rows for:

• source;
• typed/effect IR;
• native IR;
• object output;
• linker artifact;
• firmware image;
• evidence bundle.

The gate does not run every heavy backend or release operation. It verifies

that Flight Core release inputs have a stable trace shape and that the positive

source corpus reaches OISA output through the current compiler path.

Release Use

Release records can use these trace IDs to connect profile source, native

lowering evidence, object/linker artifacts, emulator firmware, and hashed

evidence bundles. Physical target traces are a separate Phase S2 input.