# Contributing a measurement

*Effective 2026-08-26. Referenced by METHODOLOGY §11. This file is the whole protocol;
there is no account, no telemetry, and no tooling you must adopt.*

Every throughput number on gpudeck.com to date comes from **one disclosed fleet**. The
record gets stronger with each additional fleet — but only if heterogeneity stays
visible. A second fleet is published as a **second fleet**, under its own identifier,
beside the first. Nothing is ever averaged across fleets, and a workload's cells from
different fleets are never merged into one number.

## What a contribution is

One JSON file of daily goodput cells from hardware you operate, measured the way
METHODOLOGY §5–§8 measures: attempts, completions, and occupied GPU-hours per
(day, workload, GPU model), over stated 24-hour intervals.

```json
{
  "fleet_id": "short-stable-handle-you-choose",
  "disclosure": "one paragraph: hardware, cooling, driver family, how the fleet earns",
  "cells": [
    {
      "observation_date": "2026-08-25",
      "workflow": "workload id from class-aliases.csv, or a new one you define",
      "gpu": "NVIDIA GeForce RTX 4090",
      "physical_gpu_count": 2,
      "attempts": 41,
      "completions": 38,
      "cancellations": 3,
      "occupied_gpu_hours": 47.5,
      "measurement_interval": "PT24H"
    }
  ]
}
```

## The floor (same rules the first fleet obeys)

- **Replication:** at least 2 physical cards of the model and at least 30 attempts in
  the window, or the cell ships suppressed-and-disclosed, never silently.
- **Ratios and goodput only.** No earnings figures, no absolute revenue, no worker
  identifiers, no payment addresses or lane material. If it can identify a machine, it stays home.
- **Dated intervals.** Every cell names its 24-hour window; missed days are absent,
  never interpolated.
- **Disclosure over polish.** Confounds (mixed cooling, throttling, shared hosts) go in
  the `disclosure` paragraph. A disclosed confound is publishable; a hidden one is the
  only thing that gets a contribution refused.

## How to submit

Until the generator source is public, submissions travel by mail:
**deck@gpudeck.com**, subject `DATA CONTRIBUTION <fleet_id>`, the JSON attached.
You will get back, before anything publishes: the validation result, exactly how the
cells will appear, and the dated METHODOLOGY entry that will record the addition.

## What happens to it

- Published under your `fleet_id`, labelled as its own fleet, in the same open CSVs.
- Your cells get the same suppression rules, the same checksums in
  `manifest.json`, and the same append-only catalogue treatment.
- Withdrawal: mail from the same address; the cells leave the current vintage and the
  removal is noted in METHODOLOGY. Past frozen issues are immutable and keep what they
  published — that is what an edition is.

*This protocol is CC BY 4.0 like everything in this directory.*