If a measurement of yours is wrong, this is where you say so.
We measure servers that did not ask to be measured. That is only defensible if the people we measure can push back, at no cost, and be heard. So this desk exists before the naming does, not after somebody complains.
A correction is appended. Nothing is removed, including our mistakes.
Send this to contact@the-horizons-innovation.com
None of it is mandatory except the first line. The more of it you fill in, the faster this goes, and the less we have to guess about what you meant.
Subject: Re-measurement request Endpoint or page: https://your-server.example/mcp, or the URL of the report Which measurement: the date, or the record_sha256 you are disputing What you say is wrong: one sentence is enough What you say is right: optional How you measured it: optional. a command we can run is the fastest route Publish my name? yes / no. default is no
If you are disputing a count in a published report, opening an issue on the survey repository is better than email, because the working is public there and other people can check it too.
Five steps, and none of them are a conversation you have to win
It is measured again
Same machine, same five conditions, read only, no tool calls. Nobody reviews your argument. The instrument answers, not a person who can be persuaded or annoyed.
Both results are published
The new one, and the one you disputed, with their dates and their hashes. Side by side.
The entry is appended below and to the JSON
What was disputed, what we found, and whether you were right. Including the times you were right and we were wrong.
If a report carried the wrong number, the report is corrected in place
A correction block goes above the number, dated. The original text stays underneath. It is not rewritten to look like it was always right.
If we cannot reproduce your result, that is published too
Along with what we ran, so you can tell us where we are still measuring it differently. A disagreement that stays visible is more useful than a silence.
Every correction ever requested
This section is empty on 2026-08-19 because nobody has asked, not because nothing has been wrong. Three of our own counts were wrong before the one we published, and that is written on the report itself rather than hidden here.
This page lives in a public git repository, so an entry cannot be quietly removed later. If you want to check that nothing has been taken out, read the file's history rather than the file.
What asking here cannot get you
- ✗It is not a removal desk. There is no way to have a row taken down, and there is no code that could do it. A row that is not green stays visible, ours included.
- ✗It is not a way to buy a different verdict. This is free precisely so that nobody can argue the outcome was paid for.
- ✗It is not a right of reply we can refuse to print. If you say a measurement is wrong and we disagree, your position gets published alongside ours, and readers can decide.
測定が違うと思われたときの窓口です。無料で、今後も無料です。ご自身のサーバーでなくても構いません。公開した数字がおかしいという指摘も同じ窓口です。
やること。測り直して、新しい結果を、指摘された古い結果の隣に並べて公開します。古い記録は消しません。消す手続きを作っていないからです。元の記録は record_sha256 をそのまま保持するので、それを引用した人が後から確かめられます。
返答までの日数はお約束しません。専任の窓口が無いので、守れない数字を書きません。約束するのは「何が起きるか」であって「いつ」ではありません。
送り先は contact@the-horizons-innovation.com。件名に「再測定の依頼」と書いてください。対象のエンドポイントかページ、どの測定（日付か record_sha256）、どこが違うと思われるか。この3つがあれば足ります。