Append/get foundationfoundation
+0append failed: ledger.json does not exist
accepted run · R5/r5Droid
Droid
× sol
Generation 4 of five · harness v0.186.0 · gpt-5.6-sol · high reasoning requested
score3.003.00 visible + 0.00 holdout
- duration
- 46m15 agent turns
- reported tokens
- 459,488input + output
- cache read / input
- 2376.57%reported telemetry · not ranked
- tool calls
- 145harness-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.
Atomic batches and idempotencybatch
+0append failed: ledger.json does not exist
Deterministic paginationpagination
+0append failed: ledger.json does not exist
Legacy schema migrationmigration
+3Crash-safe writesatomicity
+0append failed: ledger.json does not exist
Interrupted-write recoveryrecovery
+0append failed: ledger.json does not exist
Multi-process concurrencyconcurrency
+0concurrent append failed: 1
Checksummed compactioncompaction
+0append-batch failed: ledger.json does not exist
Export/import round triproundtrip
+0append failed: ledger.json does not exist
Replay and integrityreplay
+0append failed: ledger.json does not exist
Full regression auditaudit
+0append failed: ledger.json does not exist
Scale and performancescale
+0append-batch failed: ledger.json does not exist
Adversarial concurrent batchesstress-concurrency
+0stress batch failed: 1
Fault injection and validationvalidation
+0Expected compact to fail
Large integrated stress runscale-stress
+0scale batch failed: 1
holdout0 / 11 checks passed+0.00
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
- 333,324
- cached input tokens
- 7,921,664
- output tokens
- 126,164
- reasoning tokens
- 47,670
- started
- Aug 4, 2026
- ended
- Aug 4, 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
- R5 · r5
- amendment
- factory droid cli harness and cliproxy route
- challenge
- challenge-8b563735b78d6c098b563735b78d6c097efd
- schedule
- schedule-d6c0ef3cd1b47e41d6c0ef3cd1b47e41e4be
- run key
- 6ad332a1d17455e23695e385
- logical identity
- factory-droid|gpt-5.6-sol|4|1|1
04 / attempt history
Failures stay outside the score.
No infrastructure-invalid attempt is recorded for this logical run. Attempts are retained for reliability analysis and never averaged into task performance.
- attempt 1completed
completed evidence archived before campaign selection
46m · Aug 4, 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.