Historical: Experiments

An experiment records a question, version, named conditions, operations, evidence state, and limitations. It does not replace operation plans or their records.

The catalogue can include a planned, tuned, or frozen protocol before confirmation exists. Confirmed and promoted entries must point to one or more complete operation records.

The frozen direct_control version 2 experiment contains the untouched confirmation operation for the four-task benchmark. Version 1 remains preserved separately. Neither protocol has an accepted run yet. Example and experimental protocol bundles remain in the repository without appearing as core studies on this page.

How an experiment is retained

An experiment directory contains experiment.toml and one ordinary plan file per operation. The archived runner writes a small experiment index plus one standard record for every operation.

Read the archived commands and examples.

The protocol fixes the question and named conditions. The operation records retain exact submitted and resolved configurations, seeds, tables, summaries, provenance, and checksums.

This page retains the earlier catalogue and protocol status. Read the historical contribution process for contribution rules or version history for the implementation boundary.