Ars Inquirendi

← All conjectures · Jewish book cultures

The midrash that skips Genesis

Status: Already answered

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 conjecture imagined by a language model — drawn from its trained weights and held to falsifiability, novelty, and plausibility, not to any one method: it may join two or more fields, or none. 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 tannaitic halakhic midrashim - the school-texts that expound the legal verses of the Torah clause by clause - cover the Torah with a conspicuous hole. There is a Mekhilta on Exodus, a Sifra on Leviticus, and a Sifre on Numbers and on Deuteronomy, but no tannaitic halakhic midrash on Genesis, and even within the covered books the exposition clusters on legal pericopes and thins across narrative. The reason is generic: this literature exists to derive and anchor law, and Genesis contains almost none, so the school that produced verse-by-verse halakhic midrash had little occasion to treat it. The result is a coverage map dictated by legal density rather than by the biblical text's extent. Mechanism: the genre is a function machine keyed to legal verses; where the input (commandments) is sparse the output (midrash) is near zero, and no amount of narrative recruits it. This is loss of a particular kind - not a book worn away but a book-shaped absence where the genre never engaged. Prediction restated: mapping the tannaitic halakhic-midrash corpus onto the Torah in Sefaria, Genesis receives essentially no coverage while the four later books do, and within them the treated verses concentrate in legal sections at a rate far above the narrative baseline.

Prediction clause (verbatim)

Prediction: mapping Sefaria's tannaitic halakhic midrashim (Mekhilta de-Rabbi Yishmael, Sifra, Sifrei Bamidbar, Sifrei Devarim) to their Torah verse-anchors, the count of distinct Genesis verses that receive halakhic-midrashic comment will be under 2% of Genesis verses (effectively zero), while Exodus-through-Deuteronomy coverage is an order of magnitude higher, and within the covered books the per-verse comment density in legal pericopes will exceed the narrative baseline by at least a factor of five - primary clause: Genesis distinct-verse coverage < 0.02; the verdict follows it. The test resolves from Sefaria's verse links and voids only if the midrashim lack verse-anchoring.

Kill-dataset (verbatim)

Kill: Sefaria's open halakhic-midrash corpora (Mekhilta de-Rabbi Yishmael, Sifra, Sifrei Bamidbar, Sifrei Devarim) with their Torah verse-links - count distinct verses commented per biblical book, and per pericope-type, against the full verse-count of each book.

Browse the registry: Digitized texts →

How this item is catalogued

Catalogue tags are curatorial metadata that make the conjecture findable. They are not findings, not a novelty verdict, and naming a source family is not a promise that the data exist or are accessible. Each dimension below says whether it was assigned, reviewed with none applying, uncertain, or not yet reviewed, and who recorded it.

Place & era tags — Assigned
Levant & Near East; Iron Age & Antiquity Tagged by claude-fable-5
Dating — Phenomenon
Dated c. 100 CE – 300 CE Tannaitic halakhic midrashim (Mekhilta de-Rabbi Yishmael, Sifra, Sifrei) redacted in the tannaitic-to-early-amoraic period, standardly 2nd-3rd century CE. Tagged by claude-sonnet-5 + claude-fable-5 (gate)
Subject — Assigned
Institutions, law & bureaucracy; Philosophy, theology & the schools a legal-exegetical genre's textual coverage tracking legal content, skipping non-legal narrative Tagged by claude-sonnet-5
Finer subject topic — Assigned
Midrash The object is the tannaitic halakhic midrash corpus and where it engages the Torah, squarely the midrash page. Tagged by claude-opus-5 draft (requested max effort) adjudicated by claude-fable-5-1 driver, lane 1da5; runtime not independently attested
Claim level — Assigned
Record claim The prediction is the verse coverage of the tannaitic halakhic midrashim across the Torah, a property of that literature's own extent. Tagged by claude-opus-5 draft (requested max effort) adjudicated by claude-fable-5-1 driver, lane 1da5; runtime not independently attested
Method — Reviewed — none applies
Registered statistic: a distinct-verse coverage share for Genesis and a per-verse comment-density ratio between legal and narrative pericopes. Tagged by claude-opus-5 draft (requested max effort) adjudicated by claude-fable-5-1 driver, lane 1da5; runtime not independently attested
Evidence source — Assigned
Digitized texts Kill test maps Sefaria's halakhic-midrash corpora to their Torah verse-anchors and counts distinct commented verses per book and pericope type. Tagged by claude-opus-5 draft (requested max effort) adjudicated by claude-fable-5-1 driver, lane 1da5; runtime not independently attested
Research stage — Idea — no test designed

On Inferpedia

This conjecture is linked to the following pages on Inferpedia, an encyclopedia of the missing — working atlas pages, some still early scaffolding.

Provenance

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

Fresh blind generation by claude-fable-5, 2026-07-17, Jewish text-culture wave instrument-anchored on the open Sefaria corpus and its cross-reference link data, with standard critical editions as controls: every kill names a real corpus and a countable operation (coverage maps, citation-formula counts, link-orphan shares, digest-fraction, recension divergence, citation-decay), thresholds far from 1 with explicit coverage guards distinguishing what Sefaria holds from what existed. Ground is CITATION-GEOMETRIC and disjoint from the 2026-07-10 w19 Jewish wave, which was material-culture-of-loss (colophons, parchment, genizah, masora, binding fragments): no material-culture re-posing here. Two candidates were dropped after a grep of all fresh packets: a Tosafot-density-by-tractate survival item (pre-empted by w02-philosophy #18, which already correlates per-folio Tosafot density with manuscript survival), and a piyyut liturgy-vs-anthology survival item (pre-empted by w01-literature #28 'Liturgy out-survives fame', keyed to Davidson's Thesaurus). The Mishneh Torah item here tests EXTERNAL source-attribution erasure vs the Tur (loss of source-geometry), deliberately distinct from minds-w02 #25, which tests the code's INTERNAL recall/promise cross-references. Two items are marked Kill (not yet built) where the deciding corpus (Kohut's Arukh apparatus; Lewin's parallel Iggeret recensions) is not yet digitized.

Novelty / leakage triage

already answered in the literature

The corpus map is the standard datum the mission's leak-alert names: tannaitic halakhic midrash exists for Exodus (Mekhilta), Leviticus (Sifra), Numbers and Deuteronomy (Sifre), and none for Genesis, with the same generic explanation (Genesis contains almost no law) given in Strack-Stemberger and in Kahana's authoritative survey of the halakhic midrashim. Since the four works' verse-anchors lie in their own biblical books by construction, Genesis anchor-coverage under 2% is guaranteed without counting anything - the primary clause, from which the verdict follows, is answered by the printed corpus map. Only the secondary legal-versus-narrative density factor would require new tabulation.

Sources cited by the triage
  • H. L. Strack & G. Stemberger, Introduction to the Talmud and Midrash (2nd ed., 1996), chapter on the halakhic midrashim
  • M. I. Kahana, 'The Halakhic Midrashim', in S. Safrai et al. (eds.), The Literature of the Sages, Part 2 (Assen: Van Gorcum, 2006)
  • J. N. Epstein, Mevo'ot le-Sifrut ha-Tannaim (Jerusalem, 1957)

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.