Experiments¶
An experiment is the record created when a plan launches. It contains the approved plan, execution progress, decisions, code, compute usage, and reports.
Experiments can test a hypothesis, build data, analyze evidence, produce code, or create a report. They appear in the thread Timeline.
Experiment boundaries¶
Launching another plan creates a new experiment. Execution retries within the existing plan remain in the current experiment.
What an experiment contains¶
An experiment can contain:
- the approved plan
- chronological progress, decisions, and deviations
- code and files created or changed during the work
- compute jobs and usage
- connected training or evaluation runs, such as Weights & Biases runs
- one or more reports
- critic review and the planner's interpretation in the parent thread
Views appear only when relevant: Reports after one exists, Compute after usage, and Metrics after a compatible run is linked.
Lifecycle and status¶
The experiment's worker executes the plan and records meaningful progress in Timeline. It can continue independently and pauses when it needs a decision or encounters a blocker it cannot safely resolve.
Queued and Running are active. Needs decision and Blocked need attention. Completed and Stopped are inactive. Read the latest Timeline entry for detail.
Stopping does not erase the work. The plan, code, decisions, and partial outputs remain available.
Experiment views¶
An experiment can contain these views:
| View | Use it for |
|---|---|
| Reports | The durable answers and outputs. This view appears once the worker publishes a result. |
| Timeline | The live landing view while work is running and the chronological record afterward. |
| Plan | The approved intent, inputs, controls, outputs, and resource assumptions. |
| Worker | Detailed execution logs and direct steering when ordinary thread-level guidance is not enough. |
| Compute | Jobs, accelerators, runtime, and compute consumption. |
| Metrics | Linked training or evaluation measurements when available. |
| Code | Files added, changed, or deleted by the experiment. |
Some views appear only when the required data exists. Use the parent thread for follow-up plans and Worker for direct changes to active execution.
Experiments within a thread¶
One thread can contain many experiments. Summary shows the current synthesis and Timeline lists experiments chronologically.