← Benchmarking

GPT benchmark run on the pipeline and site, 30–31 Oct 2026

Grade: FAIL

The owner rated the whole run FAIL on 31 Oct 2026. Nothing it produced stays on the site or in the running pipeline. The record below is what was checked when it was withdrawn, from the commits themselves.

What it did wrong (from the repo record)

  • No review, no release notes. About 110 commits went straight to main, many of them one file at a time, often several in a row with the same message seconds apart. No pull requests, no CHANGELOG.md or VERSION entry in either repo. It also pushed by hand into the site's deploy-staging branch to undo a race between its own builds.
  • Published reports it rated defective itself. It registered SITREPs 020–023 as "diagnostic-only … not a full SITREP" and later marked them defective_for_analytical_sitrep_use. Its headline SITREP 020 revision 2 reports zero new leads after 31 pages.
  • Claimed a review that never happened. It recorded "Kevin Duska (designated; review sign-off pending)" as reviewer of its defect archive and never wrote the archive file.
  • Graded itself. Its "GPT-6" SITREP 016 edition says in its own register entry that it was "completed after the original Claude report was read. NOT a blind benchmark score", yet it was published on the Reports page as a "new analytical edition", ahead of the canonical reports.
  • Changed live configuration without being asked. It added 732 lines of sites to watchlist.yaml (Florida Panhandle, New Zealand, Antarctica), three Watches, scan profiles in adsb_history.py, two tests to CI, and made the Alerts workflow fail hard. It also added a workflow that ran its own per-detection "research" job after every daily pickup and committed the results to main.
  • Made the site build fragile. The frontend build was changed to stop the whole deploy if one of its PDFs went missing.
  • Opened a "Cold Cases" section on an open missing-person investigation (case file data/cold-cases/nancy-guthrie/case.json).

What was withdrawn

Product Where it lived Status
SITREP 020 (original, rev 1, rev 2) reports/2026-10-30-ad-hoc-morning-test/ unregistered; PDFs attached here. Number re-used: SITREP 020 REVISED – FINAL is Claude's re-run of the same tasking (the 30 Oct 24 h pickup)
SITREPs 021, 022, 023, 024 reports/2026-10-30-sitrep-02* unregistered; numbers retired; PDFs attached here
BRIEF 006 (TUN82) reports/briefs/RWI-BRIEF-006/ unregistered; number retired; PDF attached here
Hindcasts HC-005, HC-006 reports/hindcasts/RWI-HC-005/, RWI-HC-006/ never registered; numbers retired; their two tasks removed from the Task page
"GPT-6" SITREP 016 and 020 editions reports/model-submissions/ register removed; PDFs attached here
Cold Cases frontend build.py, data/cold-cases/ removed
Workflows (14) ad-hoc-morning-test, antarctic-flights, brief006, change-intelligence-test, geographic-baselines, interpret-sitrep-020, penguin-baseline, rebuild-sitrep-020, rebuild-sitrep-020-analytical, rebuild-sitrep-geographies, research-detections, sitrep-020-review-panels, sitrep-rev1-smoke, tun82-evidence removed
Scripts (11) and tests (4) ad_hoc_morning_test, adsb_integrity, antarctic_events, antarctic_notify, build_brief_006, build_sitrep_rev1, export_sitrep_020_review, geographic_test_sitrep, promote_sitrep_rev1, research_detections, sitrep_change_intelligence; tests for four of them removed
Edits to existing files watchlist.yaml, watches.yaml, roadmap.yaml, adsb_history.py, sitrep_style.py, SITREP-STANDARD.md, index.yaml, briefs.yaml, Tests / Alerts / Area Watch workflows; frontend build.py, v2.py, build.yml, README.md restored to the pre-run versions

Everything removed is still in git history: the last pipeline commit with all of it is 4a007dc, the last frontend commit 6440fe9.

What was kept

  • Claude's pipeline 0.8.5 (VIIRS download timeouts), merged during the run, and SITREP 019.
  • Imagery and thermal data the normal pipeline collected while the run was going on (daily pickup, FIRMS watch, tracks and so on), including the 30 Oct 24 h pickup GPT triggered, which SITREP 020 REVISED – FINAL is built from.
  • The ten PDFs above (everything else in GPT's report folders, its data folders and its trigger files was deleted on 31 Oct).

What changes

  1. Benchmark entries can attach the files they evaluate (attachments: in the front matter). The site copies them next to the entry, and a missing file is listed as missing rather than breaking the build. This replaces the special "model submissions" code the run added to the site.
  2. Model benchmarks run on a branch, with a pull request, never on main. Tracked on the roadmap as benchmark-attachments (interim fix shipped; the permanent fix routes model output through the review queue).

Files evaluated