Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Closed beta. Monte is in closed beta. Interfaces and docs change quickly.
| Term | Meaning |
|---|---|
| Environment | The graded world an agent acts on: the tasks, the grader, and any tools and per-task state. See Environments. |
| Task | One problem for the model, plus the data needed to score an attempt at it. |
| Rollout | One attempt at one Task, from prompt through to a graded reward. |
| Grader | Scores one attempt into a reward, usually between 0 and 1. It defines what “good” means for its Environment. |
| Split | A frozen list of Task IDs. Every Measurement owns three: train, dev, and test. |
| Term | Meaning |
|---|---|
| Measurement | A frozen evaluation contract over one Environment: which Tasks run, under which settings, and what counts as correct. See Measurement. |
| Fingerprint | A hash over the Task files, the grader, the prompt, and the harness. A Run is refused when any of them has moved. |
| Baseline | The base model’s score before any training, written as eval@0. Every later score in the same Cohort is read against it. |
| Term | Meaning |
|---|---|
| Run | One execution recorded as a row. Either a training Run, which produces a Checkpoint, or an eval Run, which scores one. |
train@N / eval@N | N is the Checkpoint’s absolute step count, never a run index. The training Run ending at step 50 is train@50, and eval@50 scores what it produced. |
| Checkpoint | The model’s saved state at one step. |
| Servable folder | The weights and tokenizer directory an inference server can load, in Hugging Face layout. |
| Load-check | One prompt pushed through a real serving stack to prove a servable folder actually serves. It is not a score and not a Run. |
| Recipe | The named file stating how a training Run trains: model shape, algorithm, batch geometry, optimizer. See Training. |
| Run plan | The complete merged settings of one Run, resolved before launch, printed for confirmation, and stored alongside the Run. What you approve is what executes. |
| Term | Meaning |
|---|---|
| Cohort | The Runs sharing a base model and comparability config: the set within which a number means something. Each one needs its own Baseline, and a delta never crosses from one Cohort into another. |
| Lineage | A Checkpoint’s descent path back to the base model, with every hop labelled by the Recipe that produced it. Checkpoints form a tree, so one Cohort can hold several Lineages. See Improvement. |
| The claim | The test score of the Checkpoint the tool selected. test is read exactly twice per Cohort, at the Baseline and here. |
| Promoting | Exporting a claimed Checkpoint’s servable folder as a checksum-verified copy, behind a confirmation you type out in full. |
| Term | Meaning |
|---|---|
| Ledger | The append-only, per-Measurement record of Runs: what happened, in what order, with what score. Every surface reads it through one API rather than touching the files. |
| Trace | One Run’s attempt at one Task: the rollout verbatim, plus the grader’s own fields. |
| Provenance | The hashes carried on every row, covering the code, the configuration, the Splits, the comparability config, and the container image. |
