Talmud Yerushalmi Shevuot fragment witness split

Epistemic status

Inferred L3 evidence-packet article.

This article describes an entity that is not directly attested. It is an inference from the evidence listed below.

Summary

Source-specific child ledger for the Shevuot fragment and Leiden Codex witness problem.

What is being inferred

What this witness-ledger article infers is one specific binding-fragment witness to Talmud Yerushalmi Shevuot, split out from the broader Jerusalem Talmud witness-family ledger as its own trackable node: the claim is that this particular fragment is a distinct, independently catalogued piece of evidence for the tractate's transmission, not a restatement of the manuscript already covered by the wider witness-ledger article.

What is attested

• Evidence 2178 records: The article supports a specific Yerushalmi Shevuot fragment witness route.
• Evidence 2179 records: The catalog supports witness control for the broader Yerushalmi textual route.
• Evidence 4138 records: Offline judge treated existing inferon 295 (source_dependence) as support for Talmud Yerushalmi Shevuot fragment witness split. Evidence strength: bounded but below-publication structural/source inferon; sufficient for L2 review, not for article promotion. The accountable path is EvidencePath 1512.

Why infer this entity

The article on the newly discovered binding fragment (Evidence 2178) is the primary support, describing a specific Yerushalmi Shevuot fragment witness route that is concrete and locatable rather than a general statement about the Jerusalem Talmud's overall witness landscape. The Leiden Codex detailed record (Evidence 2179) supplies witness-level catalogue control for the broader Yerushalmi textual route this fragment sits alongside, allowing the fragment to be positioned relative to the one known complete manuscript without conflating the two. This is a deliberately narrow, two-item packet: because the broader witness-family claim is already made elsewhere, the claim made specifically here is limited to this fragment's existence and its status as a distinguishable, catalogued node in that family, not a restatement of the family-wide claim. The packet carries no counterevidence item; nothing disputes the fragment's authenticity or relevance, and that absence is recorded honestly as a limit on independent testing.

Evidence ledger

• Evidence 2178: A Newly Discovered Binding Fragment of Talmud Yerushalmi Shevuot, article metadata. The article supports a specific Yerushalmi Shevuot fragment witness route. Role: Supporting evidence.
• Evidence 2179: Detailed Record for Talmud Yerushalmi Leiden Codex, catalog record. The catalog supports witness control for the broader Yerushalmi textual route. Role: Bibliographic control.
• Evidence 4138: Offline existing-inferon judge ledger control source, existing_inferon_judge_promote:inferon:295. Offline judge treated existing inferon 295 (source_dependence) as support for Talmud Yerushalmi Shevuot fragment witness split. Evidence strength: bounded but below-publication structural/source inferon; sufficient for L2 review, not for article promotion. The accountable path is EvidencePath 1512. Role: Noetic interpretation.

Counterarguments

• The packet contains no separate counterevidence item; this absence does not remove the need for challenge.

Confidence scores

• Direct attestation: 15
• Existence warrant: 74
• Specificity confidence: 58
• Reconstruction dependence: 70
• Counterevidence pressure: 0

What would change the score

• A direct attestation would move this out of the inferred catalogue.
• Stronger independent evidence would raise the warrant or specificity.
• Better counterevidence would lower the warrant or force retirement.