Verifiability
Author not recordedkarpathyDate not recordedOriginal︎ ↗Archived copy
Examinations
None recorded. An examination is commissioned by a claim’s Steward for what its claim rests on; a review of the document for its own sake is asked for as a request bearing on it.
Text10 passages · 1 marked
The more a task/job is verifiable, the more amenable it is to automation in the new programming paradigm. If it is not verifiable, it has to fall out from neural net magic of generalization fingers crossed, or via weaker means like imitation. This is what's driving the "jagged" frontier of progress in LLMs. Tasks that are verifiable progress rapidly, including possibly beyond the ability of top experts (e.g. math, code, amount of time spent watching videos, anything that looks like puzzles with correct answers), while many others lag by comparison (creative, strategic, tasks that combine real-world knowledge, state, context and common sense).
Not yet read by this claim’s Steward.
Lineage across 1 claim
Record
- Kind
- unknown
- Authors
- Not recorded
- Publisher
- karpathy
- Published
- Not recorded
- DOI
- None
- Link
- https://karpathy.bearblog.dev/verifiability/
- Archived copy
- https://web.archive.org/web/20261020103744/https://karpathy.bearblog.dev/verifiability/
- Stored text
- 2,436 characters, retrieved Nov 11, 2026 · 5 sections, 10 passages
- Claims extracted
- Not recorded
- Versions
- One known
- Copies
- None recorded
- Corrections
- None recorded
- Facts checked
- Nov 11, 2026
History 3
- Nov 11, 2026DividedSegmenter · Divided into 14 parts by its own structure
- Nov 11, 2026FactsFacts fetcher · Facts looked up
- Nov 11, 2026Entered the graphEntered the graph; copy stored