Disputing a value we hold: what evidence works

Evidence is a page that can be re-read

To dispute a value on infratoapp, flag it, say what it should be, and link the page that says so. We re-read that page. If it disagrees with what we publish, we correct the value and log the correction publicly; if it agrees, the dispute is closed with the quote attached. Evidence that works is a public, dated page: a pricing page, a changelog entry, a datasheet. A statement that the value is wrong, with nothing to read, does not move it.

Anyone can file one. You do not need an account and you do not need to work at the company, because a reader who spotted an error is exactly who the dispute form is for. A claimed vendor uses the same form as everybody else.

Three kinds of page, and when each one works

The current pricing page is the strongest evidence for a price, because it is the same kind of page the value was read from in the first place. Where we hold an old rate and your page shows a new one, the re-read settles it. The post on what we read from your pricing page explains why the old figure was there.

A changelog or release note works for anything that changed on a date: a model retired, a context window raised, a region added. It gives the re-read a sentence and a day, which is what a correction needs to say when the value changed and not only that it did.

A datasheet or a documentation page works for specifications and for what a product includes. It works less well against a price, because documentation can be written once and left alone while the pricing page moves. Where the two disagree, say which one you maintain.

Pages run by someone else are weaker. A reseller’s listing, a review site or a press article can repeat your figure, but if your own page says something different we will read your page, and a dispute that rests on another site’s copy of your price asks us to trust the copy over the original.

What does not work, and why

An email saying the number is wrong gives us nothing to re-read. Neither does a screenshot of an internal tool, a quote sent to one customer, or a page behind a login. The test is simple: could a stranger open the link and see the sentence? A link that fails it leaves the published value standing, because nobody else could check the replacement either.

Asking for a value to be removed is a different request, and money does not buy it. The pricing page strikes it through in its list of things no plan includes, with the words dispute instead. A value that is wrong gets corrected. A value that is right and unwelcome stays.

A gap is also a different job. For a field that shows no answer on record, a dispute is the wrong tool; the contribute page takes an answer with its evidence, a claimed vendor can answer the category question with a source, and either ends in a value being added rather than replaced.

What happens while it is open

The disputed value stays on the page with a flag beside it while it is re-read. It is not hidden. Hiding it would quietly change every comparison it appears in before anyone had checked, which is a kind of error too.

The form asks for the sentence on your page that says so, as well as the link. Your source is fetched when you submit, so a dead link never reaches review, and a person then compares the quoted sentence against the page.

We answer every dispute. The answer is either a correction or a closed dispute with the supporting quote, and both outcomes are visible to the person who filed and to us.

Where the result is published

Corrections are listed on the corrections page, each with what the value was, what it became and why. The old value is not deleted. A superseded reading is marked as superseded and stays legible, because someone who cited the old figure needs to find out what changed and when.

For a vendor that history has a use. A buyer who saw a different number last month can see that it was corrected and on what evidence, which is a better answer than a figure that silently changed.

Filing one asks for the public record to be checked again. A value that changes joins the public list of corrections with your evidence as its reason; a value that stands has the supporting quote attached to the closed dispute. Check your own page before filing, so the evidence you link is the evidence you mean.

Writing a dispute so the re-read is quick

Name the value exactly: the product, the field and, for a price, the card or model and the commitment. An on-demand rate for the H100 SXM 80GB and a reserved rate for the same card are different values, and a dispute that does not say which leaves the re-read guessing.

Link the deepest page that holds the figure, never the home page. If the value sits in a table, quote the row. For a value that changed on a date, give the changelog entry for that date, so the correction can say when as well as what.

Give the value you want in the unit we publish. A per-node price offered against our per-GPU figure is a different number, and the re-read will find that the page agrees with us once the division is done. Where the real problem is that your own page is unclear, fix the page first and dispute second.