02 — Run · Round 2 · Round robin · r2-rr-jev-gpt56terra-g4
GPT-5.6 Terra vs Jev Router
Jev Router destroyed the enemy base after 9.3 game-minutes · 14.9 min wall clock
LOSS england · west
GPT-5.6 Terra
openai/gpt-5.6-terra
Value destroyed$4,100Value lost$16,700
Units killed / lost21 / 30Buildings killed / lost1 / 8
Peak army$2,000Orders issued65
Decision turns (failed)70 (0)Mean latency3.4sModel cost$0.493
WIN france · east
Jev Router
typesafe/jev-router
Value destroyed$16,700Value lost$4,100
Units killed / lost30 / 21Buildings killed / lost8 / 1
Peak army$7,900Orders issued157
Decision turns (failed)70 (2)Mean latency5.5sModel cost$0.129
Evaluation
passchecks 10/10 verdict computed from the gating checks
| Status | Kind | Check | Detail |
|---|---|---|---|
| pass | step | environment | Environment check (snapshot, engine, content, key) |
| pass | step | launch | Launch run-match as a detached process |
| pass | step | supervise | Supervise in the foreground until run-match exits |
| pass | step | render | Render the 1080p recording |
| pass | step | notes | Append Notes to summary.md |
| pass | code_check | outputs-exist | all present |
| pass | code_check | game-has-winner | jev won: base destroyed |
| pass | code_check | decisions-logged | turns per slot: {'Multi0': 70, 'Multi1': 70} |
| pass | code_check | llm-turns-valid | failed/total per slot: {'Multi0': '0/70', 'Multi1': '0/70'} |
| pass | code_check | video-decodes | duration 94.6s |
| pass | code_check | video-complete | video ends at tick 13886 of 13886 |
| pass | code_check | limits-respected | ended after 14.9 wall-minutes (budget 30.0 min): base destroyed |
| pass | checklist | notes-explain-win | Notes section cites both models final thoughts and explains Jev Router won via superior army build and income management |
| pass | checklist | players-match-request | result.json records gpt56terra as Multi0 and jev as Multi1 matching the requested players |
| pass | checklist | no-silent-outage | run.log shows continuous turn lines with no gaps, 0 failures for both models across all 70 turns |
Decision timeline
What each model saw as its situation and what it ordered, every 8 game-seconds. Click a turn to jump the video there.