The table of contents remembers a leaner epic

Status: Anticipated · untested

Status is derived only from the shepherd-authored triage/prediction data above -- community submissions and claims are a separate overlay and can never change it (see the participation panel below).

This is a proposed connection between two domains, generated by a language model. It is not an article and not evidence: it sits below the evidence/publication boundary. A quantitative prediction and a named kill-dataset are attached (when registered) so the claim stays falsifiable rather than merely evocative.

Claim (verbatim)

The Mahabharata audits itself: the Parvasamgraha (Mahabharata 1.2) states verse totals for each parvan. A stated count is a conservative relic — it fossilizes the redaction that stood in front of the counter — while the text keeps growing wherever growth is cheapest. Growth is cheapest in the didactic corpora: detachable teachings with no narrative causality to violate, where an interpolated chapter breaks nothing. The gap between stated and actual counts is therefore not noise but a growth map of the epic, and it should point straight at the instructional books. Prediction: comparing actual verse counts per parvan in the Pune critical edition with the Parvasamgraha's stated figures, the largest combined absolute excess will fall on the Santiparvan and Anusasanaparvan together, and proportional excess will rank the didactic books above the battle books (primary clause: Santi plus Anusasana take the largest combined excess of any two books; the verdict follows it). Exact computation: count verses per parvan in the machine-readable BORI critical edition text hosted by GRETIL and difference them against the Parvasamgraha figures transmitted in the same edition. Kill: the GRETIL electronic text of the Poona (BORI) critical edition of the Mahabharata together with the Parvasamgraha chapter (Mahabharata 1.2) in that edition.

Prediction clause (verbatim)

Prediction: comparing actual verse counts per parvan in the Pune critical edition with the Parvasamgraha's stated figures, the largest combined absolute excess will fall on the Santiparvan and Anusasanaparvan together, and proportional excess will rank the didactic books above the battle books (primary clause: Santi plus Anusasana take the largest combined excess of any two books; the verdict follows it). Exact computation: count verses per parvan in the machine-readable BORI critical edition text hosted by GRETIL and difference them against the Parvasamgraha figures transmitted in the same edition.

Kill-dataset (verbatim)

Kill: the GRETIL electronic text of the Poona (BORI) critical edition of the Mahabharata together with the Parvasamgraha chapter (Mahabharata 1.2) in that edition.

Nobody has run this test. The kill-data is named above. If you can run it — or you know the paper that already settles it — claim the kill or submit the prior scholarship. Kills and prior scholarship are credited here, by name, as they come in.

Provenance

Run: Fresh agent generation · model: claude-fable-5

Fresh blind generation instance of claude-fable-5, 2026-07-16, wave M02 (the works) of the Minds & Works campaign, produced from model knowledge alone under the two-file blindness protocol.

Novelty / leakage triage

anticipated in the literature — this exact test has never been run

Borderline-leaked: the discrepancy between the Parvasamgraha's stated verse totals and the actual text, and the outsized growth of the didactic Santi/Anushasana parvans, are established in Mahabharata scholarship; but the specific claim that stated-vs-actual excess is LARGEST (combined) on those two books, ranking didactic above battle books, was not located as a measured difference.

V.S. Sukthankar et al., BORI critical edition prolegomena; J. Fitzgerald on the Santiparvan

Predictions

No prediction registered yet.

Weigh in

No community feedback yet.

New here? Create an account first

Create an account or sign in and your feedback is tied to you — you can track it, get replies, and claim this conjecture so others know you’re working on it. Prefer not to? Just leave your take below as a guest — only the name you type is shown.

Add your take

Posted immediately (spam is removed). Community feedback is never an adjudicated verdict and never changes this conjecture's triage label or status above.