Runtime implementation¶
These pages trace how gptnt run validates work, starts processes, assigns services, exchanges
commands, records progress, and handles failure.
Maintainer reference
This section describes the current implementation. Its classes, private modules, Redis keys, and HTTP routes are not supported extension interfaces unless another reference page says so.
Trace by operation¶
| Operation | Page |
|---|---|
| Validate, prepare, spawn, submit, monitor, and terminate | Run orchestration |
| Queue specifications, match services, and run sessions | Experiment manager |
| Configure KTANE, observe state, and apply actions | Game service |
| Prepare model input, perform calls, communicate, and record | Player service |
| Determine readiness, availability, and expiry | Service registry |
| Inspect liveness keys, request channels, and timeouts | Heartbeats and RPC |
| Write player records, finalise outcomes, and ingest results | Recording and completion |