BuilderBuilder
Supplemental workflow

CAD-002 robot arm

Supplemental workflow · 3 measured runs across 1 target. Each entry is a single recorded attempt; repeat-run reliability is not established.

Inspect the run ledgers← All collections
CAD-002 robot arm public evidence
CAD-002 robot arm public evidence
3Measured runs
1Frozen targets
3Model families
3Configurations
Collection scope

Recorded evidence, without a synthetic score.

Runs share the same frozen target and prompt within each test, with disclosed provider-specific stacks. Costs are recorded estimates as labelled in each ledger, not subscription invoices.

Targets

  • CAD-002 Robot Arm

Model coverage

  • Claude Opus 5.5 · High
  • Claude Sonnet 5.5 · High
  • GPT-6.1 Sol · Max

Evidence available

  • 3 runs without a prompt hash
  • Prompt hash was not published
  • Exact prompt file path was not published

Still missing

  • No released Builder project, harness package, or skill download.
  • Prompt hash was not recorded on these ledgers.
  • Exact prompt file path was not published with this test.
  • CAD-002 is supplemental and is not part of the turbofan test.
  • Repeat-run reliability evidence is not established.
Public receipts

3 measured run ledgers

Open any row for its recorded workflow cost, timing, token usage, stack disclosure, artifact integrity, and explicit evidence gaps.

01Claude Opus 5.5High reasoning · CAD-002 Robot Armscored_complete · Prompt hash unavailable$9.49 API-equivalent estimaterecorded estimate29m 47sEnd-to-end workflowOpen 02Claude Sonnet 5.5High reasoning · CAD-002 Robot Armscored_incomplete · Prompt hash unavailable$8.89 API-equivalent estimaterecorded estimate23m 04sEnd-to-end workflowOpen 03GPT-6.1 SolMax reasoning · CAD-002 Robot Armscored_complete · Prompt hash unavailableAPI-equivalent range $2.75–$5.19recorded estimate53m 48sEnd-to-end workflowOpen
Prompt provenance

Exact prompt receipts

A path is shown only when the published record includes the prompt hash that identifies it. Campaign evidence and projections keep the hash gap visible.

Prompt identity not recorded

Prompt hash was not published.

Exact prompt file path was not published.

Separate records

Related records with unknown prompt provenance

These published records stay separate from the prompt receipts above. Unknown provenance is why they are listed here.

No separate unattached records are published for this collection.

Limits

Evidence and material gaps

  • No unaided Astra CAD-002 ledger was found.