Append/get foundationfoundation
+3accepted run · R4/r4DotAgents
DotAgents
× luna
Generation 4 of five · harness v1.1.9 · gpt-5.6-luna · high reasoning requested
score12.0012.00 visible + 0.00 holdout
- duration
- 1h 01m15 agent turns
- reported tokens
- 7,797,878input + output
- cache read / input
- 2.88%reported telemetry · not ranked
- tool calls
- 3,160harness-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-batch failed: ledger: duplicate event id: b1
Deterministic paginationpagination
+0append-batch failed: ledger: duplicate event id: b1
Legacy schema migrationmigration
+3Crash-safe writesatomicity
+3Interrupted-write recoveryrecovery
+0Expected recover to fail
Multi-process concurrencyconcurrency
+3Checksummed compactioncompaction
+0append-batch failed: ledger: primary ledger state is missing
Export/import round triproundtrip
+0append failed: ledger: primary ledger state is missing
Replay and integrityreplay
+0append failed: ledger: primary ledger state is missing
Full regression auditaudit
+0append failed: ledger: primary ledger state is missing
Scale and performancescale
+0append-batch failed: ledger: primary ledger state is missing
Adversarial concurrent batchesstress-concurrency
+0stress batch failed: 1
Fault injection and validationvalidation
+0audit failed: ledger: idempotency metadata mismatch: validation-idem
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
- 7,633,915
- cached input tokens
- 219,648
- output tokens
- 163,963
- reasoning tokens
- 106,827
- 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
- 5ca03e09e6731c7dbea39b18
- logical identity
- dotagents-mono|gpt-5.6-luna|4|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.
- attempt 1infrastructure-invalid
DotAgents stream ended without a done event
50m · Jul 30, 2026 - attempt 2completed
completed evidence archived before campaign selection
1h 01m · 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.