Skip to content

1 · First auditable run

You will distinguish “the command exited” from “the experiment can be audited,” and you will know which file to open first when the two disagree.

A run is not one metric. Turnkey resolves inputs and components, evaluates cases, records ordered events, derives aggregate metrics, and preserves the resolved run description. Those layers let you trace a surprising score back to a concrete case and runtime decision.

configuration → resolved run → cases + events → metrics → audit

Use the source-preview setup from Install, then inspect the CLI and repository smoke path:

Terminal window
uv run turnkey --help
bash scripts/run_dataset_adapters_smoke.sh

The smoke path proves a local adapter flow. It does not prove that credentials, model endpoints, or remote datasets work.

If an aggregate score looks wrong, start with the affected row in cases.jsonl, then correlate its events in events.jsonl. metrics.json is the summary to recompute, not the only source of truth.

Download the Chapter 1 notebook

Next: Build your own detector.