Measured harness ledgerPublic result
Grok 4.6High-voxel-density Shrine Village diorama — Grok 4.6 xhigh
Create a complete inspectable Blender voxel diorama of a shrine village at a fixed 0.05-unit voxel resolution through the Blender MCP workflow.
xhigh reasoningHeadline result
- Workflow cost
- $2.68
- Wall-clock
- 20m 22.040s wall-clock
- Processed tokens
- 4.22M processed
- Record state
- partial_one_shot_token_timing_and_artifact_ledger
Public summary
Grok 4.6 xhigh partial_one_shot_token_timing_and_artifact_ledger ledger: 20m 22.040s wall-clock, 4.22M processed, and $2.68 Provider-recorded usage estimate, not a subscription cash-charge invoice.
Run identity and stack
- Result ID: shrine-village-grok-4.6-xhigh
- Technical model: Grok 4.6
- Provider: xAI Grok Build
- Client: Grok 1.0.3
- Stack: xAI Grok Build
- Stack: Grok 1.0.3
- Stack: Technical model/configuration: Grok 4.6
- Stack: Blender MCP
- Stack: 0.05-unit voxel grid
- Stack: Inspectable .blend artifact
Cost basis
- The exact billed alias grok-4.6-build has no official public catalog price, so no API-equivalent cost is inferred.
Primary artifact integrity
- Kind: blender-scene
- Path: artifacts/shrine-village-grok-4.6-xhigh/shrine_village.blend
- SHA-256: ed29c48adca76783a320025f575f0146e74e785f238a38b18beb97dfb201a657
Recorded caveats
- Wall-clock is end-to-end latency, not model-only compute; it includes tool time and idle intervals.
- Generated output includes visible output and reasoning output as provider-reported.
- Cache reads are discounted in provider billing, so total processed tokens overstate cost.
- The $2.68 figure is the source ledger's provider-recorded usage estimate, not an inferred API-equivalent rate or a subscription cash charge.
- The receipt reports aggregate tool counts only; it does not publish a tool-by-tool transcript.
- The final scene and supplied preview are archived; Blender was unavailable during intake, so the scene was not independently reopened or rerendered.
- The builder declares Blender Eevee, an orthographic isometric camera, and 1920x1080 output, while the supplied PNG is 1920x1440. The discrepancy is recorded but not resolved during archival.
- No render-hardware receipt, initial/optimized local FPS pair, RTX Pro 6000 1080p60 final capture, or blind evaluation is archived.
Visible evidence gaps
- Blender version and render-hardware receipt
- independent Blender scene inspection and rerender
- reconciliation of builder-declared and supplied-capture resolutions
- initial local FPS
- optimized local FPS
- RTX Pro 6000 1080p60 final 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.