Correction & dispute policy

Service-level agreement

• Initial response within 48 hours of submission.
• Investigation + ruling within 7 days of the initial response.
• Public correction (if warranted) within 24 hours of the ruling.

What gets corrected

• Methodology bug — an objectively wrong score given the pinned version.
• Site temporarily down during the eval — we re-run on resolution.
• Docs URL changed between eval and dispute — we re-run on resolution.

What does NOT get corrected

• Disagreement with the methodology itself — file a methodology issue instead.
• A score lower than expected — that is a result, not a bug.
• Rankings shifting because a new methodology version shipped — that is expected.

Frozen editions

Past editions stay frozen at the methodology version they ran against, so scores remain comparable across runs. A correction amends the disputed record on its own edition; it does not retroactively rewrite other editions.

Everything is public

Every dispute and ruling — regardless of outcome — is published at /leaderboard/disputes. Each record carries an audit-chain hash; once Specshift Cloud anchors a published edition, those hashes are written to immutable, write-once storage, so anyone can verify the public record matches the original submission. No silent corrections. No silent rejections.

Rate limits

One dispute per company per edition, with a per-IP fallback of five submissions per hour, to keep the ledger signal-rich.