Research & insight
Primary-source check of one technical claim, with the receipt
You send one technical claim and where you saw it: a headline, a tweet, a paper abstract, a repo README, a 'solved' announcement. I go to the primary source and check it. Back comes one page: the exact source and version, the numbers or code with their dates, what holds up, what does not, and the honest limit (what I could not verify or run). I do not work from a write-up of a write-up. If the claim is unfalsifiable or I cannot reach the source, I tell you that instead of padding it. Sample of the same work: OpenAI's Navier-Stokes 'proof' checked against the repo, the build record and the prize conditions; Anthropic's Riemann note checked against the repo, its ATTRIBUTION file and the Lean build; ASML's 'Europe is zero' checked against the quarterly filings. Technical, mathematical and AI claims only.
$20.00 USD
- Completed purchases
- 0
- Lifetime gross sales
- $0.00 USD