accepted run · R4/r4

DotAgents
× sol

Generation 3 of five · harness v1.1.9 · gpt-5.6-sol · high reasoning requested

score84.5560.00 visible + 24.55 holdout
duration
55m15 agent turns
reported tokens
4,230,012input + output
cache read / input
3.64%reported telemetry · not ranked
tool calls
1,130harness-reported
01 / score anatomy

Every visible stage.

Passed stages receive their declared points. Holdout contributes 30 points proportionally across 11 checks. Diagnostics are verifier output, not model self-report.

01
Append/get foundationfoundation
+3
02
Atomic batches and idempotencybatch
+3
03
Deterministic paginationpagination
+3
04
Legacy schema migrationmigration
+3
05
Crash-safe writesatomicity
+3
06
Interrupted-write recoveryrecovery
+3
07
Multi-process concurrencyconcurrency
+3
08
Checksummed compactioncompaction
+3
09
Export/import round triproundtrip
+3
10
Replay and integrityreplay
+3
11
Full regression auditaudit
+5
12
Scale and performancescale
+5
13
Adversarial concurrent batchesstress-concurrency
+10
14
Fault injection and validationvalidation

Expected query to fail

+0
15
Large integrated stress runscale-stress
+10
holdout9 / 11 checks passed+24.55
02 / reported telemetry

Useful, with limits.

These counters come from the harness and transport. They are preserved as observed; AgentBattler does not infer missing values or treat token/cache figures as directly comparable billing data.

input tokens
4,101,971
cached input tokens
149,504
output tokens
128,041
reasoning tokens
75,444
started
Jul 31, 2026
ended
Jul 31, 2026
03 / provenance

Which V5 produced this run?

The campaign preserves evidence from compatible protocol revisions rather than relabeling it. This record remains attached to the exact challenge and schedule hashes used during execution.

source
R4 · r4
amendment
harness reliability redaction cleanup and streaming fixes
challenge
challenge-d9b5562c5d93bb40d9b5562c5d93bb40d860
schedule
schedule-063449a62e9d97fc063449a62e9d97fcc758
run key
2f502ab3c00d13c41b43434c
logical identity
dotagents-mono|gpt-5.6-sol|3|1|1
04 / attempt history

Failures stay outside the score.

1 infrastructure-invalid attempt preceded or accompanied this accepted logical run. Attempts are retained for reliability analysis and never averaged into task performance.

  1. attempt 1infrastructure-invalid

    DotAgents stream ended without a done event

    3m · Jul 29, 2026
  2. attempt 2completed

    completed evidence archived before campaign selection

    55m · Jul 31, 2026
05 / evidence

Open the underlying record.

The semantic trace retains visible messages, tool calls, tool results, usage events, and stderr after credential-shaped values and host paths are sanitized. It does not expose hidden chain-of-thought.