Chapter 26 — File and Schema Reference
Run artifacts
| Artifact | Purpose |
|---|---|
*.iris |
Primary captured diagnostic bundle; opened by the Bench. |
iris.log |
Tracker-side log, capture outcomes, and applied commands. |
scratch/ |
Temporary runtime support; a clean tracker close removes its own temporary files. |
iris.cmd |
Supported live commands staged for the tracker when requested. |
| Bench-derived analysis and Bench log | Kept in a separate machine store; derived analysis is rebuildable from the bundle. |
| Run notes | User-authored observations; not included in the MCP measurement stream. |
| Exported PDF or AI report | A selected presentation of captured data, with scope and coverage to review. |
| Recorded playback | A display recording; its frames are not additional model measurements. |
Do not treat a derived cache as the primary run record. Preserve the bundle and tracker log, and keep exported or user-authored artifacts according to your team's recordkeeping policy.
Data sources and missing values
Reported training/holdout metrics originate in your training code. Probe outcomes and internal channels originate in the instrument's captures. User-defined functions derive values from existing channels. Keep those sources separate when reading an export.
A missing key, an explicit null, a zero reading, a not-applicable label, and a pending result are different states. Read the channel's definition and stated reason. Do not fill a missing measurement with zero or fabricate intermediate samples to smooth an exported series.
Provenance for comparisons
Keep run identity, step, metric name, unit, probe/domain definitions, capture mode, and any uncertainty or reduced-coverage labels with the data. A same-named channel can have a different definition in another version; preserve a definitions-differ warning instead of silently combining it.
The bundle is not a full model checkpoint, but it and its derived artifacts can contain confidential information about the model and inputs. Apply the sharing and access guidance in Chapter 14.
