What we stand for
The cost of producing a confident claim has collapsed to zero. Models, marketers and gurus generate fluent certainty faster than anyone can check it. Checking is now the scarce thing, so checking is the whole job.
Make verification cheaper than the bullshit.
The rules, and what makes each one true
A principle nothing checks is decoration. So every rule below carries its own receipt: the gate that proves it, or an honest admission that nothing does. We ask readers to audit our verdicts. This is the same offer, applied to us.
Every verdict links its sources, and those links are checked for liveness before we publish. A claim without receipts is an opinion.
HOW IT IS PROVED: verify-issue.py checks every receipt resolves and every quote is verbatim. site-provenance-check.py fails the ship on any number anywhere on the site that has no source behind it.
Confidence, polish and reach are not evidence. The smoother the claim, the harder we check it.
HOW IT IS PROVED: Editorial judgement. No gate can measure this one, and we will not pretend otherwise. What we do gate is the consequence: a smooth claim still has to survive rules 1 and 3.
Every verdict states what evidence would reverse it. If we cannot say what would prove us wrong, we do not publish.
HOW IT IS PROVED: mission-gate.py fails the ship on any story with no falsifiability line. Six stories from the project's first three days predate this rule and are named in content/mission-debt.json. That list may only shrink.
When we are wrong we say so at the volume of the original claim. The record is dated and never silently edited.
HOW IT IS PROVED: redteam-gate.py fails the ship once a prediction's own stated deadline passes with no resolution recorded. Corrections are added alongside the original text, never over it.
We are skeptics, not cynics. When a claim survives the evidence we stamp that as loudly as when it fails.
HOW IT IS PROVED: The four rulings carry equal visual weight by construction: all four verdict colours sit at identical perceptual lightness, so nothing shouts louder than VERIFIED by design.
The goal is not that you trust us. It is that you get harder to fool. Every issue shows the trick, not just the verdict.
HOW IT IS PROVED: Every story names the spin mechanism it used, from the fixed vocabulary in content/mechanism-labels.json, and backfill-mechanisms.py fails the ship if a story's mechanism drifts from it.
Where we currently fall short
Rule 4 says corrections are loud. That applies to our own rules too, so the exceptions are published rather than buried. 6 stories from the first three days of this project predate rule 3 and carry no falsifiability line. The gate blocks any new one, and this list may only shrink.
- openai-astra-ten-math-proofs 2026-08-04
- openai-friar-july-arr-topped-q2 2026-08-04
- openai-unprecedented-cyber-incident-hugging-face 2026-08-04
- amd-su-data-center-doubled-q2-2026 2026-08-06
- hinton-routine-intellectual-labor-jobs-ai4-2026 2026-08-06
- qwen3-8-max-most-capable-claim 2026-08-06
Pipeline rules
Owner directive, 2026-09-08. The routes are disabled by the leading underscore on src/pages/_films and _films.astro, which Astro does not route. Content is retained, not served.
HOW IT IS PROVED: mission-gate.py fails the ship if any film page is built or any served page links to /films.
See the methodology for how a claim becomes a verdict, and the verification dashboardfor how we police ourselves.
