Corrections Policy
KernelBrief is written by humans and assisted by machines. Mistakes happen. Here is how we fix them.
Our commitment
KernelBrief's editorial policy requires that corrections be published visibly. We do not silently edit stories after publication. When a factual error is confirmed, we update the story with a clear correction notice and, where appropriate, note the change in the next newsletter issue.
This policy applies to all published content: daily briefs, story pages, topic pages, project watch entries, and newsletter issues.
How to submit a correction
You can submit a correction through any of these channels:
- Correction form — use the correction submission form on the story page or at /submit. Include the story URL or title, the specific error, and (if possible) a link to the correct information.
- Email — send corrections to [email protected] with "Correction" in the subject line. Include the story title, date, the error, and the correct information.
- Reply to newsletter — if the error appeared in a newsletter issue, you can reply directly to that email. Newsletter replies go to the editorial team.
A good correction submission includes:
- The specific story or brief item with the error (title, date, URL if available)
- A clear description of what is wrong
- A link to the correct primary source, if you have one
- Your contact email (optional, but helpful if we need clarification)
What happens after you submit
- Acknowledgement — you will receive an acknowledgement when the beta form workflow is available. We aim to review correction submissions within 2 business days, with material factual errors prioritized.
- Verification — an editor reviews the correction against primary sources. We do not publish corrections based on unverified claims.
-
Decision — if the correction is
confirmed:
- The story is updated with the correct information.
- A correction notice is appended to the bottom of the story.
- The correction is logged in our editorial system.
- Newsletter note — for material errors that appeared in a newsletter issue, the correction is noted in the following issue.
Correction visibility
| Error type | Correction format | Timeline |
|---|---|---|
| Typo or minor wording | Silent fix with "Updated" timestamp on the story page | As confirmed during beta review |
| Factual error (date, name, number, link) | Correction notice appended to the story: "Correction: [detail]. [Date]." | Prioritized when confirmed |
| Material error (wrong source, incorrect claim, missing context) | Correction notice appended to story + noted in next newsletter issue | Prioritized when confirmed |
| Retraction (story should not have been published) | Story marked as retracted with explanation + noted in next newsletter | As soon as confirmed |
All correction notices remain on the story page permanently. We do not remove correction notices after publishing them.
Correction disputes
If you disagree with an editorial decision about a correction:
- Reply to the editor's response with additional evidence.
- If the issue involves a primary source we linked to, we will review the source again.
- For disputes about editorial framing or analysis (as opposed to factual errors), we may add an editor's note rather than a correction. Analysis and opinion are labeled separately from factual news per our editorial policy.
Contact
For correction submissions or questions about this policy:
- Email: [email protected]
- Subject line: "Correction" (for submissions) or "Correction policy question" (for policy questions)
- Response time: we aim to review correction submissions within 2 business days. Policy questions are handled as editorial capacity allows during beta.
Policy last updated: 2026-05-20