Measured harness ledgerPublic result
Claude Opus 5Space Flight Stage 2 — Landfall — Claude Opus 5 Max
Extend the Stage 1 space-flight project with a seamless orbit-to-surface round trip, explorable terrain, takeoff, landing, and a fixed character asset using one frozen follow-on request.
Max reasoningHeadline result
- Workflow cost
- $133.83
- Wall-clock
- 2h 31m 33.5s wall-clock
- Processed tokens
- 207.64M processed
- Record state
- partial_token_timing_source_build_ledger
Public summary
Claude Opus 5 Max partial_token_timing_source_build_ledger ledger: 2h 31m 33.5s wall-clock, 207.64M processed, and $133.83 Claude API list-price equivalent, not an itemized Claude Code charge.
Run identity and stack
- Result ID: space-flight-game-threejs-stage-2-landfall-opus-5-max
- Technical model: claude-opus-5
- Provider: Anthropic Claude Code
- Stack: Anthropic Claude Code
- Stack: Technical model/configuration: claude-opus-5
- Stack: Three.js Stage 2 workflow
- Stack: Harness v1 Landfall prompt
Cost basis
- All-5-minute cache-write alternative: $129.37.
Primary artifact integrity
- Kind: vite-threejs-stage-2-landfall-source-and-production-build-entry-point
- Path: artifacts/space-flight-game-threejs-stage-2-landfall-opus-5-max/source/src/main.js
- SHA-256: e316707a0c57e3a2cdb6079f40ff978e6aa8a184d1880ab6231671fc40072702
Recorded caveats
- Wall-clock is end-to-end workflow latency, including tools, browser automation, builds, and idle time; it is not model-only compute.
- Output tokens include hidden reasoning, generated code, and tool-call JSON, not only visible prose.
- Cache-read tokens are discounted, so total processed tokens overstate cost.
- The archived Vite build passes, but no independent full-loop browser acceptance run, local FPS/transition-hitch receipt, final capture, or blind evaluation is archived.
- The one-hour cache-write assumption is explicitly reported by the source receipt but cannot be independently reconstructed from the sanitized token totals.
Visible evidence gaps
- independent uninterrupted landing-to-orbit acceptance run
- local FPS and transition-hitch receipt with hardware details
- final viewport or browser capture
- blind-evaluation record
Public result only
This result keeps its public summary and evidence, but it does not currently have a matching Builder test with prompts, projects, Harness workflows or skills.