Inferpedia - an encyclopedia of the missing
L2 Candidate Inferred source Drafted Priority 71

Chronicle of Moses extract layer behind Midrash Wayosha

A Chronicle of Moses extract/source layer inferred inside the composite Midrash Wayosha Exodus Song exposition.

L4 Draft articles and reviews

Chronicle of Moses extract layer behind Midrash Wayosha v1 ยท Draft
Draft Warrant 71 Attestation 44 Specificity 66

A source layer inside a composite Exodus Song midrash.

This is a visible L4 draft/review article, not an L5 published Inferpedia article. The publication state is part of the audit trail.

This article describes an entity that is not directly attested as a complete independent Chronicle of Moses layer within Midrash Wayosha; it is inferred from source-composite notices about Wayosha's use of Chronicle of Moses material.

Epistemic status

Draft article. The source-layer notice is source-backed, but the layer is narrow and attribution-sensitive.

Summary

Jewish Encyclopedia describes Midrash Wayosha as a later haggadic exposition on Exodus 14:30-15:18. It says entire sections are taken from Tanhuma and that the midrash also contains extracts from the Chronicle of Moses. It also warns that later attribution to Midrash Abkir is doubtful. Inferpedia treats the Chronicle of Moses material as a draft inferred-source layer inside the composite Wayosha tradition.

What is being inferred

The inferred entity is a Chronicle of Moses extract layer behind a passage of Midrash Wayosha.

What is attested

The source attests Wayosha's Exodus Song setting, Tanhuma borrowing, Chronicle of Moses extracts, agreement with Yalkut, and doubtful Abkir attribution.

Why infer this entity

When an encyclopedia notice identifies extracts from one work embedded in another composite midrash, the embedded source layer is useful for navigation and source control, even if it is narrow.

Evidence ledger

  • E1, Jewish Encyclopedia: context for Midrash Wayosha as the container.
  • E2, Jewish Encyclopedia: context for the Exodus Song scope.
  • E3, Jewish Encyclopedia: supporting trace for Tanhuma borrowing.
  • E4, Jewish Encyclopedia: supporting trace for Chronicle of Moses extracts.
  • E5, Jewish Encyclopedia: counterevidence against simple Abkir attribution.

Counterarguments

This is not a lost-work claim about Wayosha itself. It may cover only a limited passage, and the exact relationship among Chronicle of Moses, Yalkut, Tanhuma, and Abkir needs edition-level comparison.

Confidence scores

Direct attestation: 44. Existence warrant: 71. Specificity: 66. Reconstruction dependence: 90. Counterevidence: 40.

What would change the score

A synoptic edition of Wayosha, Chronicle of Moses, Yalkut, Tanhuma, and Abkir would raise specificity. Evidence that the Chronicle notice is only a late misattribution would lower the score.

Why this candidate exists

Codex-native Judaism category traversal selected a smaller midrash whose source composition includes identifiable Chronicle of Moses and Tanhuma extraction layers.

L3 Evidence packet

Jewish Encyclopedia, Midrashim, Smaller - Indirect reference

Warrant role: Lead context

Source authority: Encyclopedia summary 70

Access level: Full text

Locator: Jewish Encyclopedia, Midrashim, Smaller

Quote: "Midrash Wayosha"

Paraphrase: The entry identifies the containing midrash.

Reliability: 70 - Relevance: 70

Cluster: wayosha-chronicle

Jewish Encyclopedia, Midrashim, Smaller - Indirect reference

Warrant role: Lead context

Source authority: Encyclopedia summary 70

Access level: Full text

Locator: Jewish Encyclopedia, Midrashim, Smaller

Quote: "based on Ex. xiv. 30-xv. 18"

Paraphrase: The source locates the containing exposition in Exodus Song material.

Reliability: 70 - Relevance: 68

Cluster: wayosha-chronicle

Jewish Encyclopedia, Midrashim, Smaller - Shared wording

Warrant role: Supporting evidence

Source authority: Encyclopedia summary 70

Access level: Full text

Locator: Jewish Encyclopedia, Midrashim, Smaller

Quote: "Entire sections are taken verbatim from the Tanhuma"

Paraphrase: The source describes a source-composite structure.

Reliability: 70 - Relevance: 76

Cluster: wayosha-chronicle

Jewish Encyclopedia, Midrashim, Smaller - Shared wording

Warrant role: Supporting evidence

Source authority: Encyclopedia summary 70

Access level: Full text

Locator: Jewish Encyclopedia, Midrashim, Smaller

Quote: "extracts from the Chronicle of Moses"

Paraphrase: The source explicitly identifies Chronicle of Moses extracts inside Wayosha.

Reliability: 70 - Relevance: 90

Cluster: wayosha-chronicle

Jewish Encyclopedia, Midrashim, Smaller - Negative evidence

Warrant role: Counterevidence

Source authority: Encyclopedia summary 70

Access level: Full text

Locator: Jewish Encyclopedia, Midrashim, Smaller

Quote: "doubtful whether this haggadah ever occurred in that work"

Paraphrase: The source warns that later Abkir attribution may be wrong.

Reliability: 70 - Relevance: 86

Cluster: wayosha-chronicle

Offline existing-inferon judge ledger control source - Network gap

Warrant role: Noetic interpretation

Source authority: Noetic model prior 50

Access level: No external text

Locator: existing_inferon_judge_promote:inferon:423

Paraphrase: Offline judge treated existing inferon 423 (source_dependence) as support for Chronicle of Moses extract layer behind Midrash Wayosha. Evidence strength: source-backed prior reading already isolated a bounded missing or reconstructed entity; suitable for L2 only. The accountable path is EvidencePath 1640.

Reliability: 71 - Relevance: 66

Cluster: existing_inferon_judge_promote:c9169c3669d9f27784eda4d7c0bdb1f0

Arguments

Abductive - warrant 71

Existing inferon 423 supports an L2 inferred candidate for Chronicle of Moses extract layer behind Midrash Wayosha; this remains below publication and is not direct attestation.

AI-assessed L2 Quotient triage: AI judge warrant assessment for L2 Quotient triage; existing AI-created evidence remains below publication.

Textual stemmatic - warrant 71

A Chronicle of Moses extract layer behind Midrash Wayosha is warranted as a source-backed draft inferred-source entity.

The Chronicle extract signal is explicit but narrow; the source layer should remain limited to the composite passage and attribution problem.