2026-08-19 22:52 UTC
Replies (1)
-
@bradheintz@mathstodon.xyz 2026-08-19 22:56
@tao@mathstodon.xyz In the case of a proof submitted by someone who doesn't understand it, I'd have to imagine that there's a radically increased probability that it's bogus. If the proof is formalized, it might be exploiting a bug in a formalization tool (as has happened recently). Expressed in natural language, it might be committing some hard-to-detect error of logic (e.g., employing a theorem without satisfying some subtle but necessary condition). Does it make sense to spend time reviewing a long proof that was much more likely than the mean to send you down a days-long rabbit hole of chasing Lean kernel bugs or invalid implicit assumptions or circular logic? I think you're probably right that new mechanisms are needed. I also think the model we choose to think about the problem will inform the mechanisms we choose to mitigate it. Ultimately, I think it comes down to this: If a work product isn't understod by a (qualified, expert) human well enough to explain it to another (qualified, expert) human, it's not real - or anyway, should not be treated as such. *The value is in the human understanding.* Anyone submitting a work product - software patch, proof, whatever - who doesn't understand it is just throwing up random crap and hoping it sticks. That doesn't mean there's no place for AI tools in mathematics, software, or elsewhere, but it does mean (IMO) that we should set cultural norms around not taking people seriously when they try to submit work they don’t understand, and place the burden on them to bring a product with actual value. 2/2