Append/get foundationfoundation
+0append failed: duplicate event id: a1
accepted run · R4/r4Claude Code
Claude Code
× sol
Generation 4 of five · harness v2.1.220 · gpt-5.6-sol · high reasoning requested
score19.363.00 visible + 16.36 holdout
- duration
- 3h 07m15 agent turns
- reported tokens
- 31,740,622input + output
- cache read / input
- 97.11%reported telemetry · not ranked
- tool calls
- 448harness-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: duplicate event id: a1
Deterministic paginationpagination
+0append failed: duplicate event id: a1
Legacy schema migrationmigration
+3Crash-safe writesatomicity
+0append failed: duplicate event id: a1
Interrupted-write recoveryrecovery
+0append failed: duplicate event id: a1
Multi-process concurrencyconcurrency
+0concurrent appends lost updates or sequences
Checksummed compactioncompaction
+0compaction changed logical records
Export/import round triproundtrip
+0append failed: duplicate event id: a1
Replay and integrityreplay
+0append failed: duplicate event id: a1
Full regression auditaudit
+0append failed: duplicate event id: a1
Scale and performancescale
+0scale append/query lost records
Adversarial concurrent batchesstress-concurrency
+0concurrent batches lost events or sequence numbers
Fault injection and validationvalidation
+0Expected compact to fail
Large integrated stress runscale-stress
+0paged stress query returned 10001 events
holdout6 / 11 checks passed+16.36
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
- 31,523,568
- cached input tokens
- 30,612,480
- output tokens
- 217,054
- reasoning tokens
- 0
- started
- Jul 30, 2026
- ended
- Jul 30, 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
- 5f371af3dd627a15beb4716b
- logical identity
- claude-code|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
3h 07m · Jul 30, 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.