Workbench mass
Living archive of runs, packs, and artefacts.
How claims are made. How the lab is run. Not product SKUs. Scale numbers below are locked Workbench claims only.
The evidence engine behind Zero Overshoot and cross-domain runs. Packs, ledgers, protocols, custody material. Marketing slogans do not outrank CSVs.
Living archive of runs, packs, and artefacts.
Traces, ledgers, configs, notes — chain of custody material.
Multi-angle pressure, not five cherry-picked sets.
Pre-declared protocols. Adversarial packs. Domain maps. Locked CSVs and decision summaries that outrank lab slogans. Reproduction paths for serious partners via audit materials.
Not a public product SKU. Not a dashboard for hire. Not permission to invent win rates outside locked packs. Not a substitute for named surfaces on a hardware pilot.
Failures are first-class data. Inversion when aggregates flatter. “What we didn’t do” is mandatory: dead ends, rejected designs, scopes refused, tests skipped and why.
Lab operators only in this phase. Partners get audit materials and gsrf-bench paths — not a Workbench license checkout.
Every public number is a subset of private custody. The path is fixed before spin — not rewritten after the plot looks good.
Six allowlisted public / synthetic / public-benchmark plots only — not the experiment archive. Captions include framing. Deep packs stay on zeroovershoot.com/evidence and evidence packs.
Request Audit Pack ZO evidence Evidence packs
Shared lab methodology (loop, trust signals, bounded claims): Method.
Internal control plane for evidence gates and refuse-to-claim rules on our builds — not a product, not a feature catalogue, and not for sale. Partners buy Zero Overshoot + audit materials, not Hub.
Five real-life datasets is not enough. Work is incomplete until pressure-tested from many angles.