Run manifest¶

A run manifest is a YAML mapping accepted by gptnt doctor, gptnt generate, and gptnt run. Schema version 2 is the only accepted version. Unknown fields are rejected on the manifest, roster entries, and anchors.

Complete example¶

runs/quickstart.yaml is the smallest checked-in manifest that exercises a two-player suite:

# A `run.yaml` manifest: the single, declarative source of truth for one run.
#
# It names the suite(s), how many rooms to play, and which players take part. Validate it
# (structure + config-name cross-checks) with:
#
#     gptnt doctor runs/quickstart.yaml
#
# then generate its specs and run them:
#
#     gptnt generate runs/quickstart.yaml
#     gptnt run runs/quickstart.yaml

spec_version: 2
suites:
  - single-pairwise-sync
rooms: 2

players:
  - player: test-defuser
  - player: test-expert

# Where the resume check reads completion from: `local` (on-disk outputs, needs no W&B) or `wandb`.
# W&B logging itself is driven by the ambient WANDB_* environment, not configured here.
source: local

observability: limited

Use Create a run manifest for the authoring procedure.

Field effects not conveyed by the schema¶

displays assigns room processes to X display numbers in round-robin order. None preserves the ambient DISPLAY. source selects the local or W&B completion ledger used to filter completed attempts. attempts_per_mission changes generation depth rather than suite identity.

Each suites entry accepts <name> for the latest frozen revision or <name>@<revision> for one specific frozen revision. gptnt run rejects pre-generated specifications whose suite names and revisions do not match these selectors.

Manifest fields¶

Roster entries¶

Anchors¶

Completion source¶

local = 'local'

wandb = 'wandb'