Append/get foundationfoundation
+3accepted run · R4/r4DotAgents
DotAgents
× luna
Generation 5 of five · harness v1.1.9 · gpt-5.6-luna · high reasoning requested
score70.5546.00 visible + 24.55 holdout
- duration
- 1h 07m15 agent turns
- reported tokens
- 7,187,308input + output
- cache read / input
- 2.94%reported telemetry · not ranked
- tool calls
- 3,150harness-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
+3Deterministic paginationpagination
+3Legacy schema migrationmigration
+3Crash-safe writesatomicity
+3Interrupted-write recoveryrecovery
+3Multi-process concurrencyconcurrency
+0concurrent append failed: 1
Checksummed compactioncompaction
+0replay failed: idempotency event id is invalid
Export/import round triproundtrip
+3Replay and integrityreplay
+0replay failed: ledger snapshot sequence state mismatch
Full regression auditaudit
+0replay failed: ledger snapshot sequence state mismatch
Scale and performancescale
+5Adversarial concurrent batchesstress-concurrency
+10Fault injection and validationvalidation
+0Expected compact to fail
Large integrated stress runscale-stress
+10holdout9 / 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
- 7,029,635
- cached input tokens
- 206,336
- output tokens
- 157,673
- reasoning tokens
- 104,127
- 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
- 1aad87997b79b383f9da2106
- logical identity
- dotagents-mono|gpt-5.6-luna|5|1|1
04 / attempt history
Failures stay outside the score.
3 infrastructure-invalid attempts preceded or accompanied this accepted logical run. Attempts are retained for reliability analysis and never averaged into task performance.
- attempt 1infrastructure-invalid
DotAgents stream ended without a done event
19m · Jul 30, 2026 - attempt 2infrastructure-invalid
DotAgents stream ended without a done event
43m · Jul 31, 2026 - attempt 3infrastructure-invalid
DotAgents turn exceeded 1800000 ms
1h 26m · Jul 31, 2026 - attempt 4completed
completed evidence archived before campaign selection
1h 07m · 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.