Ars Inquirendi

AI-generated conjecture · a wager, not a finding

← All conjectures · Works' qualities & composition

Maimonides promises little

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 Mishneh Torah presents itself as pure architecture: fourteen books deduced from a plan, stripped of names and dialectic. But architecture and procedure leave different paper trails. A work drafted freely across a finished plan can promise — as will be explained in Hilkhot such-and-such — as easily as it recalls; a work composed sequentially through its own order accumulates recalls and avoids promises, because every forward promise is a drafting debt to a book that does not yet exist. The cross-reference ledger of the work is thus a fossil of how Maimonides actually moved through his own outline. Prediction: explicit internal cross-references of the recall type ('as we have explained in...') will outnumber promise-type references ('as will be explained in...') by at least three to one when signed against canonical book order, and the promises that do occur will concentrate in the first two books, Madda and Ahavah (primary clause: the three-to-one backward ratio; the verdict follows it). Exact computation: on the Sefaria-Export machine-readable Mishneh Torah, pattern-match the reference formulas, resolve targets through Sefaria's citation links, and sign each reference by canonical order. Kill: the Sefaria open-data export of the Mishneh Torah with its citation-link tables (github.com/Sefaria/Sefaria-Export).

Prediction clause (verbatim)

Prediction: explicit internal cross-references of the recall type ('as we have explained in...') will outnumber promise-type references ('as will be explained in...') by at least three to one when signed against canonical book order, and the promises that do occur will concentrate in the first two books, Madda and Ahavah (primary clause: the three-to-one backward ratio; the verdict follows it). Exact computation: on the Sefaria-Export machine-readable Mishneh Torah, pattern-match the reference formulas, resolve targets through Sefaria's citation links, and sign each reference by canonical order.

Kill-dataset (verbatim)

Kill: the Sefaria open-data export of the Mishneh Torah with its citation-link tables (github.com/Sefaria/Sefaria-Export).

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

The Mishneh Torah's architectural self-presentation is much discussed, but the specific claim that recall-type cross-references outnumber promise-type >=3:1 (with promises concentrated in Madda/Ahavah) as a fossil of sequential composition was not located as a measured ledger.

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.