generate¶
gptnt generate composes a run manifest into persisted experiment specifications. It validates
configuration and benchmark integrity without checking runtime infrastructure.
Usage¶
| Input or option | Required | Effect |
|---|---|---|
MANIFEST |
Yes | Existing run.yaml manifest to compose. |
--output-dir PATH |
No | Writes specifications to this directory. Also reads EXPERIMENT_SPECS_DIR. |
--force |
No | Continues despite failed policy and preflight checks. Any later records without verified release provenance cannot be submitted. |
The command performs these operations in order:
- Load and validate
RunManifest. - Check benchmark integrity and the selected player roster without runtime infrastructure.
- Compose the suites, missions, pairings, players, and attempts into
ExperimentSpecobjects. - Write one JSON file per specification.
Default output¶
Without an override, the output directory is:
Each file uses the <attempt_name>.json pattern. gptnt run runs/<name>.yaml later reads every
*.json file recursively from output/experiment_specs/<name>/.
gptnt generate runs/quickstart.yaml --output-dir output/experiment_specs/quickstart # (1)!
- The explicit path matches the default for
runs/quickstart.yaml. Use the option only when you need another location.
Specifications were written
The command prints Wrote <count> spec(s) to <path> after all JSON files are written.
Nothing is written after a failed gate
A failed integrity, player, roster, or composition check stops before the output operation. An
empty generated plan also stops with No experiment specs were generated from this manifest.
Generated specifications retain benchmark identity
A specification records the selected suite name, revision, and digest. Regenerate after changing a manifest, suite selection, mission input, protocol, player selection, or attempt count. Do not mix files generated from incompatible inputs in one output directory.