GPUDECK · SECOND FLEET · PROTOCOL FIRST
Every measured cell GPUDeck publishes comes from one operator's fleet. That is the single largest limit on the record, and it is stated in the methodology rather than hidden. A second fleet publishing under its own identifier is what turns a single-operator dataset into something replicable.
Open to the first 3 independent fleets. The honest premise: a competing operator has no obvious reason to publish data that helps buyers price them down. “Contribute to transparency” is not an exchange. So here is the actual exchange, and the limits on it.
Compensation terms are not yet set and nothing is offered here. An integration stipend and a Deck grant are under consideration; until the operator approves the amounts and the contributor agreement clears legal review, this page makes no financial offer. The rule those terms must satisfy is already fixed, and it is the important part:
A private monthly Fleet Audit: completion yield, failure/retry distribution, GPU-hour leakage, workload-specific throughput, hardware/config anomalies, data-quality gaps, and comparisons against ALREADY-PUBLIC GPUDeck evidence only. It never reveals another contributor's unpublished observations.
Contribution excludes all of it, permanently:
Fleets are never merged. Each fleet is published under its own identifier. There is no ALL FLEETS aggregate unless a separately governed multi-operator aggregate is later established, and that would be its own decision on the record.
Identity is private by default. Public label is 'INDEPENDENT FLEET <X> - OPERATOR IDENTITY VERIFIED BY GPUDECK'. A contributor may opt into 'OPERATED BY <NAME>' with a plain provenance link. No logo placement, no preferred-provider listing, no commercial prominence of any kind is granted in exchange for data.
Publication is delayed 14 days. Contributed goodput publishes on a delay so that contribution never exposes current operational position.
Passing the contribution protocol earns the contributor benefit. The contributor cannot suppress an unfavorable valid observation, rewrite methodology, or withdraw an already frozen observation merely because the result is commercially inconvenient. Corrections remain available for factual errors, and disputes go through the public register. If you believe a published figure is wrong, the dispute register is the route — the same one open to any provider.
Daily workload, GPU model, attempts, completions and occupied GPU-hours, under your own fleet identifier. Fleets are never averaged — your cells are published as yours, beside the existing fleet, never blended into it. Earnings and worker identity are not accepted and will be rejected if sent.
Submitting here does not make data part of the record. The protocol in CONTRIBUTING-DATA.md is the gate: one script, one JSON file, one pull request, no account and no telemetry. This form exists so you can ask questions first, or tell the record you intend to submit.