Sanballat open letter behind Nehemiah 6
An open accusation letter attributed to Sanballat's fifth approach in Nehemiah 6.
L4 Draft articles and reviews
Sanballat open letter behind Nehemiah 6 v1 ยท Draft
An open accusation-letter source surface in Nehemiah 6.
This article describes an entity that is not directly attested as an extant recoverable letter; it is inferred from source-citation traces and should not be read as ordinary documentation of a surviving opposition document.
Epistemic status
Draft article. Nehemiah 6 directly reports an open letter and its accusation content, but the letter is not independently extant.
Summary
Nehemiah 6 says Sanballat sent a servant with an open letter and introduces accusation content as written in it. Inferpedia treats this as an opposition-correspondence source surface.
What is being inferred
The inferred entity is the open letter attributed to Sanballat's fifth approach in Nehemiah 6.
What is attested
The text attests the open letter, its delivery by a servant, and reported written accusation content.
Why infer this entity
The passage gives physical characterization, delivery context, and written-content formula.
Evidence ledger
- E1, Nehemiah 6:5: primary trace for the open letter.
- E2, Nehemiah 6:6: primary trace for written content.
- E3, Nehemiah 6:6-7: primary trace for accusation content.
Counterarguments
The open letter may be a narrative device within Nehemiah's opposition story rather than a recoverable document.
Confidence scores
Direct attestation: 60. Existence warrant: 80. Specificity: 72. Reconstruction dependence: 78. Counterevidence: 20.
What would change the score
Specialist discussion of Nehemiah memoir sources, Persian-period accusation letters, or external administrative parallels would change the score.
Why this candidate exists
Codex-native Judaism category traversal selected a directly reported open-letter trace.
L3 Evidence packet
Bible (King James), Nehemiah 6 - Indirect reference
Warrant role: Primary trace
Source authority: Primary source 80
Access level: Full text
Locator: Nehemiah 6:5
Quote: "open letter in his hand"
Paraphrase: The passage physically characterizes the message as an open letter.
Reliability: 80 - Relevance: 88
Cluster: neh6-sanballat-open-letter
Bible (King James), Nehemiah 6 - Indirect reference
Warrant role: Primary trace
Source authority: Primary source 80
Access level: Full text
Locator: Nehemiah 6:6
Quote: "Wherein was written"
Paraphrase: The accusation is framed as written content within the letter.
Reliability: 80 - Relevance: 84
Cluster: neh6-sanballat-open-letter
Bible (King James), Nehemiah 6 - Indirect reference
Warrant role: Primary trace
Source authority: Primary source 80
Access level: Full text
Locator: Nehemiah 6:6-7
Quote: "There is a king in Judah"
Paraphrase: The reported content includes an accusation about kingship in Judah.
Reliability: 80 - Relevance: 76
Cluster: neh6-sanballat-open-letter
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:343
Paraphrase: Offline judge treated existing inferon 343 (source_dependence) as support for Sanballat open letter behind Nehemiah 6. Evidence strength: source-backed prior reading already isolated a bounded missing or reconstructed entity; suitable for L2 only. The accountable path is EvidencePath 1560.
Reliability: 80 - Relevance: 66
Cluster: existing_inferon_judge_promote:0dbe9c891bb32399e6fa4ee5a17cd88a
Arguments
Existing inferon 343 supports an L2 inferred candidate for Sanballat open letter behind Nehemiah 6; 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.
A Sanballat open letter behind Nehemiah 6 is warranted as a source-backed draft entity.
The open-letter and written-content language supports a bounded source surface, while independent archival status remains uncertain.