DD-010

TreasureBench (DD-010; historical identifier DiscoveryBench)

TreasureBench is the formal public suite for the versioned exact golden benchmark with enforced protocol information boundaries; frozen DiscoveryBench identifiers and all five quarantined Agents v1 pilots remain unchanged, while AO-0011 completes a wholly fresh 500-pairing v5 engineering pilot under forward-only provider-outcome policy v3 and unchanged protocol-validity policy v2 without publishing task-level performance or creating scientific evidence.

Completed finite studyChecked independently

The question

Can a versioned benchmark exactly reproduce the project's validated bounded fixtures while enforcing protocol information capabilities and reporting task-level metric vectors without collapsing them into an unexplained score?

What we found

What this result covers

Checked independently. The formal evidence wording and registry state remain available below.

Technical details
Study phase
complete-bounded-study
Registry status
complete-v1-v3-with-five-agents-v1-pilots-quarantined-and-ao0011-fresh-v5-engineering-complete-under-policies-v2-v3
Evidence status
v1-v2-preserved-v3-independently-reproduced-exact-matrix; original-agents-v1-pilot-permanently-quarantined; repair-confirmation-v1-quarantined-at-terminal-public-canary; AO-0004-R4-provider-schema-and-semantic-contract-engineering-conformance-passed; repair-confirmation-v2-quarantined-at-custody-after-two-passing-public-canaries-with-zero-private-runs; AO-0007-one-use-custody-diagnostic-and-prospective-live-mode-conformance-passed; repair-confirmation-v3-quarantined-during-fixed-full-batch-with-provider-phase-closed-3576-object-lock-and-no-unseal; AO-0009-one-use-aggregate-r2-diagnostic-authenticated-450-fixed-batch-traces; AO-0010-forward-only-protocol-validity-policy-v2-frozen-and-repair-confirmation-v4-quarantined-at-private-prefix-provider-terminal-missing-with-provider-phase-closed-150-object-lock-and-no-unseal; AO-0011-forward-only-provider-outcome-policy-v3-and-fresh-v5-engineering-complete-with-500-terminal-pairings-496-protocol-valid-4-protocol-invalid-zero-provider-missing-zero-contract-safety-no-circuit-breaker-provider-phase-closed-4067-object-lock-and-post-lock-verification; AO-0012-R4-owner-authorization-consumed-at-pre-ingress-hard-stop-and-never-reusable; AO-0012-R5-owner-authorization-consumed-after-credential-ingress-at-control-plane-secret-deletion-ambiguity-hard-stop-before-pod-model-endpoint-inference-or-billing; AO-0012-R6b-owner-authorization-consumed-at-one-query-inventory-ambiguity-with-no-deletion-inference-or-spend-and-current-empty-secrets-tab-qualified-owner-observation-only; AO-0012-R7-owner-authorization-consumed-at-fresh-account-inventory-boundary-with-zero-resource-mutation-model-inference-billing-or-spend; no-closeout-is-performance-or-scientific-evidence

Reproducible evidence

Files and data

What comes next

Preserve the R7 inventory-boundary hard stop and consumed authorization; require a fresh explicit owner decision before any local repair gate, provider query, or live retry; keep PR