niklaslenzGLM-5.3-Flash in the Gauntlet
2 DGX Sparks 256 GB · TensorFold 1.1.9, Mia's GLM-5.3-Flash 1104 recipe (d4226a1, EXL3 4 bpw, DFlash2), no prompt cache
What happened on the course
Each range is one task with one answer and no retry. Every wrong or missing target is a miss and costs a penalty loop. The race time is thinking, running, shooting and loops together.
| # | Task | Targets | Hits | Thinking | Buzzer | Penalty loops | Range time |
|---|---|---|---|---|---|---|---|
| 1 | River ferry (puzzle, level 1) | ✕✕✕✕✕ unusable answer | 0 / 5 | 5.3 s | no | 5 (60.0 s) | 72.5 s |
| 2 | Painter (code, level 2) | ✕✕●✕● | 2 / 5 | 4.2 s | no | 3 (36.0 s) | 47.4 s |
| 3 | Bench seating (puzzle, level 3) | ●✕●●● | 4 / 5 | 4.9 s | no | 1 (15.0 s) | 27.1 s |
| 4 | Snake (code, level 4) | ✕✕✕✕✕ | 0 / 5 | 19.6 s | no | 5 (75.0 s) | 101.8 s |
● hit, ✕ miss. The range time runs from arriving at the mat to leaving the range, loops included. A buzzer means the thinking cap ran out and the game forced the answer.
Every number has its file
Result (result.json) Race log (log.jsonl) Model answers (io.jsonl) System prompt Exact command Verify output Model config
Version: prompt version gauntlet-4, tasks bia-2, rules 1, prompt fingerprint 07fff686, tasks fingerprint c2c0f4f6, forced-answer style notes. Verified: the replay of the race log reproduces the end state and every code answer re-runs to the same verdict. Forced-answer style: how the game asks for the answer when the buzzer sounds (a prefilled answer start, or notes when the engine refuses that). Command and config are normalized: internal addresses appear as 127.0.0.1.
- No prompt cache for this race. The answer function was often called without a required field, which counts as a failure.
Who made what
No full v2 run of this exact setup is on the site yet. · How the game test works · All races