Trust · how we handle mistakes
Correction policy
Mistakes happen. When they do, we acknowledge them, fix them, and leave a paper trail. This page explains how to report a correction, how we classify it, and the response time you should expect.
1 · How to report a correction
The fastest path is email toinfo@versalspace.comwith the URL of the page and a short description of the issue. If you're citing a primary source, attaching the source link or document is the single most helpful thing you can do.
2 · How we classify corrections
Every report is tagged into one of four classes. The class determines our response time.
| Class | Examples | Response time |
|---|---|---|
| Critical | Wrong launch outcome, fatal status flip, misattributed mission patch with rights implication. | ≤ 4 UTC hours |
| High | Wrong payload mass, wrong agency, wrong rocket linkage, wrong launchpad. | ≤ 1 UTC business day |
| Medium | Spelling, date precision, missing translation, broken external link. | ≤ 3 UTC business days |
| Editorial | Tone, framing, optional context, suggested addition. | Reviewed at next editorial pass |
3 · What you'll see after a correction
- The page is updated immediately when verification is complete.
- Critical and High corrections get a short editor note documenting what changed and when.
- The page's `updated_at` timestamp moves to the moment of the fix.
- If a correction overturns a previously published article statement, we add a "Correction" callout at the top of that article.
4 · What we will not do
- We do not silently rewrite history. Articles and detail pages keep their public correction trail.
- We do not delete content because a source asked us to. Removal requires a legal or rights reason.
- We do not take payment to make a correction or to suppress one.
5 · Appeals
If you disagree with the resolution of a correction, write toinfo@versalspace.comwith the report ID and a short statement of the disagreement. The editorial lead replies within three UTC business days. The decision after appeal is final.