Files and schemas¶
These pages describe authored files and persisted outputs that cross a GPTNT command or process boundary. Configuration model pages describe their validated fields; this section describes names, locations, and on-disk relationships.
Available file contracts¶
| Files | Contract |
|---|---|
| Manuals | Manual profile inputs and derived outputs |
| Experiment specifications | Generated attempt inputs and frozen suite, mission, and player state |
| Player records and outcomes | Per-turn Parquet rows, terminal footers, summaries, and outcomes |
| DuckDB | Tables built from player-record Parquet for result analysis |
| Static evaluation outputs | Metadata, predictions, metrics, and how-do-you output |
| Submission bundles | Schema-version-2 manifests and interactive or static payloads |
| Output layout | Default locations and ownership of generated files |
Run manifests and player settings are covered by the configuration reference. Runtime-only Redis values are covered by the runtime implementation reference.
Authored input and cache output
Commit manual profiles and sources.toml when they define benchmark content. Treat
output/manual_cache/ as derived data: copy it for offline preparation, but do not edit its
manifests or compiled files by hand.