Dispute Process

LAST UPDATED 2026-08-08

Draft. Dispute submission below is real and working — it writes to our actual tracking system and the SLA deadline is really computed. What's still not operational: the Grading Review Board isn't a staffed body yet, and no real grades have been published, so submitting against a listing that doesn't exist yet in the real system will correctly come back as not found. See build spec §10 (Definition of Done).

§1Who reviews disputes

Grade disputes are reviewed by the aimcplist Grading Review Board — the same body that governs the grading ruleset itself. This isn't an anonymous inbox; every dispute gets a named reviewer and a resolution that's recorded against the server's public grade history.

§2Our published SLA

3 business days

to acknowledge a submitted dispute

10 business days

to resolve it — upheld or corrected

§3Two different situations, two different paths

1. You believe a finding is a false positive

Submit a dispute with your reasoning. We show evidence for every finding we publish, so point to the specific evidence and explain why it doesn't apply — e.g. code that's sandboxed, unreachable, or behaves differently than the scanner assumed. If upheld, the grade is corrected and the correction is dated in the server's public history, same as any other grade change.

2. You fixed a real, valid issue

Verified maintainers can trigger an on-demand re-scan instead of waiting for the next nightly sync — a patched flaw should update your public grade within hours, not up to a day later. This requires identity verification tied to your server's namespace, and is rate-limited to prevent abuse. It is free on every tier, including Free.

Verify as a maintainer

§4Why did my Human-Verified badge disappear?

A Human-Verified badge is locked to the exact code that was reviewed, not to the listing in general. Two independent triggers strip it automatically: a change to the tool-definition content hash (name, description, and parameters — re-checked every sync, since a rug-pull attack is defined by changed tool behavior and doesn't always bump a version number), or a major version bump where the repository maintains semver. Either one reverts the grade to Automated Only and re-queues the server for a fresh human review. A stale human review is treated as worse than no human review at all — that's deliberate, not a bug.

§5Why did my server get tagged Legacy?

When a server's adoption metrics drop it below the tracked ranking cutoff, aimcplist freezes the page instead of deleting it — the grade and evidence stay published, dated as of the freeze. Nightly scanning stops at that point, which is what the Legacy badge signals. To stop the badge flickering on and off for servers hovering right at the cutoff, a server has to sit below the line for three consecutive sync cycles before being tagged Legacy, and above it for three consecutive cycles before full monitoring resumes.

§6What we will never do

Publish an unreviewed “unsafe” verdict on a named project without evidence, or notify a maintainer after publishing a poor grade rather than before. Every finding is framed as a dated, factual observation — never an accusation.