'Proof indigestion' describes a pipeline-stage imbalance: AI has largely solved proof generation and machine verification (Lean), so the constraint shifts downstream to human-readable exposition and ingestion. Verification capacity scaling faster than comprehension capacity is what creates the backlog, not generation quality.
If you only optimize the automated stage of a pipeline, you move the bottleneck to the un-instrumented human stage and accumulate unusable output. Engineers should instrument the consumption stage (review, reading, integration) with the same rigor as the generation stage.
Any AI pipeline where automated generation/validation outruns human review (code, tests, docs, incident reports, datasets) develops a queue of technically valid but undigested artifacts; the value bottleneck relocates to exposition and canonicalization.
We are now getting this very unprecedented traffic jam or what I call proof indigestion.
AI generates valid proofs faster than humans can read, explain, or publish them.
AI creates a traffic jam of unverified and un-understood proofs known as 'proof indigestion.'