Corrections & disputes · resolved in public

Where the registry was wrong — and what we did about it

This reference improves by being wrong in public. Anyone can correct a data point or dispute a grade; every submission is resolved in the open, with a reason and a source, and logged here permanently. A registry that publishes its own errata, sourced, is worth more than one that never admits error.

Submit a correction or dispute a grade

One rule: bring a source. A price, a spec page, a dated screenshot, an invoice — evidence, not opinion. Submissions without a source are closed unanswered. Three tracks, each a one-minute form:

• Correction — a data point is wrong (stale price, wrong fabric field, a provider merged or shut down).
• Dispute a grade — you believe a deliverability grade is wrong, and you can point to the published spec that proves it. (Usually operators. Disclosing more is how you move up — that is the point.)
• Operator response — an official, attributed statement on your own provider record, verified from your domain.

Submit on GitHub →   No GitHub account? Reply to any issue of the Delivered Compute Report with subject "correction" / "dispute" / "operator response" and your evidence URL. Submissions are adjudicated on the weekly cycle and resolved here.

The log

Methodology is open (ASSAY-1); disputes are settled by evidence, not authority; every decision here is public and reversible. Grades describe seller disclosure, not measured performance.