Linguistic Gap Analysis
Linguistic Gap Analysis: Nehemiah (English → Arabic)
Purpose and Method
PRD Phase 1 Step 8 requires a structured account of where Arabic vocabulary fails Nehemiah — either because no adequate term exists (a gap) or because the available term is already occupied by a competing, doctrinally incompatible sense in the dominant Islamic religious register (a crowded neighborhood requiring deliberate “fencing” through context, paraphrase, or explanatory scaffolding). This analysis builds directly on the Nehemiah-specific bible_term_registry.json and analysis/08_core_glossary.md, and inherits every methodological convention and every reused rendering from the baseline Romans Language Package without exception. It does not re-derive risk tiers already fixed by the baseline (الناموس, الله, الرب, مقدس, العهد, إسرائيل, الخطية, نبي/نبوءة, الشكر, داود); it isolates the new linguistic terrain Nehemiah introduces and analyzes it by the same method.
Nehemiah’s linguistic profile differs from Romans in one structurally important way: Romans’ hardest terms collide with Islamic soteriological and christological vocabulary (justification, sonship, incarnation). Nehemiah’s hardest terms collide with Islamic devotional-practice vocabulary — prayer posture, fasting calendar, recitation, remembrance ritual, congregational assembly. The risk in Romans is doctrinal substitution; the risk in Nehemiah is more often ritual re-mapping, where a reader unconsciously overlays an Islamic devotional procedure onto a narrative scene that is doing something different. This shapes every recommendation below.
Section 1 — Doctrine Vocabulary Matrix
For each of the six curriculum doctrines: the available Arabic term(s), their structural weaknesses against the doctrine’s actual content, and the recommended translation strategy.
1.1 Prayer and Dependence on God in Leadership
| Element | Detail |
|---|---|
| Key terms | prayer (الصلاة), dependence on God (الاعتماد على الله), hand of God (يد الله), servant (عبد/عبدك), remember me (اذكرني يا إلهي) |
| Available Arabic vocabulary | الصلاة is the only viable term for “prayer” in the Christian Bible tradition; there is no competing Christian alternative. للاعتماد على الله vs. التوكل على الله are both grammatically available for “reliance/dependence.” |
| Weakness | الصلاة’s dominant contemporary referent for the majority of Arabic readers (Muslim-background or living in Muslim-majority contexts) is the five fixed, ritually-choreographed daily ṣalāt. Nehemiah’s prayers are the opposite pattern: spontaneous (2:4, “so I prayed” — mid-conversation, unscheduled), occasion-specific, and content-rich (rehearsing named covenant promises, 1:8-9), sometimes only a few words long. التوكل carries an even sharper problem: it is a named, technical Islamic virtue (trust in Allah’s decree, often paired with fatalistic resignation to outcome) that risks flattening Nehemiah’s active, planning, guard-setting dependence (4:9: “we prayed… and set a guard”) into passive quietism. |
| Recommended strategy | Retain الصلاة (no viable substitute exists) but require a structural teaching note at first occurrence (1:4) distinguishing spontaneous, occasion-bound petition from fixed liturgical obligation. For “dependence,” retain الاعتماد على الله (per the Nehemiah registry) and explicitly avoid التوكل على الله; anchor every occurrence to a named covenant promise or a named practical action (4:9’s prayer-plus-guard pairing is the paradigm teaching text) so dependence reads as active covenant trust, not passive fatalism. |
1.2 Rebuilding the Wall as Restoration of God’s People
| Element | Detail |
|---|---|
| Key terms | build/rebuild (بنى/إعادة البناء), wall (سور), gate (باب), the work (العمل), the holy city (المدينة المقدسة), dedication (تدشين/تكريس) |
| Available Arabic vocabulary | Construction and civic-infrastructure vocabulary is unproblematic and shared across all Arabic registers. |
| Weakness | The vocabulary itself has almost no collision risk (Section 2 below treats this as largely a non-gap doctrine). The one serious exception is المدينة المقدسة (“the holy city,” 11:1,18), which inevitably activates القُدس (Al-Quds), Jerusalem’s Arabic-Islamic proper name and one of Islam’s three holiest sites, compounded by the term’s live, contemporary political charge. |
| Recommended strategy | Use plain construction vocabulary throughout without hedging — this is a doctrine where translation should feel unremarkable linguistically so the theological weight lands on the narrative (God completing the work through ordinary human labor, 6:16), not on vocabulary anxiety. Reserve deliberate pastoral fencing exclusively for المدينة المقدسة (see Section 3) rather than diluting it with a euphemism; the covenant-historical claim must still be stated plainly. |
1.3 The Word of God Read, Understood, and Obeyed
| Element | Detail |
|---|---|
| Key terms | read (قرأ/تلا), the reading (القراءة), understand (فهم), helped understand (ساعدوا… على الفهم), gave the sense (بوضوح وتفسير), bowed/prostrated (انحنوا وسجدوا), assembly (الجماعة), it is written (كما هو مكتوب) |
| Available Arabic vocabulary | All lexically available and etymologically legitimate — قرأ is a normal Arabic verb “to read” independent of any religious tradition, in continuous use in the pre-Islamic and Christian Arabic Bible tradition. |
| Weakness | This is the single densest cluster of crowded-neighborhood risk in the entire book. قرأ/القراءة are one root-step from القرآن itself (lit. “the recitation”); الجماعة is the standard word for a ṣalāt congregation; سجد is the exact technical term for Islamic sujūd. A reader can walk through Nehemiah 8 encountering: a congregation (الجماعة) gathering, a scroll being read aloud (قرأ) for hours, the hearers prostrating (سجد) — and reconstruct, term by term, something structurally identical to a mosque scene, even though the passage’s own emphasis (repeated فهم, five times in twelve verses) is doing something Quranic recitation practice does not require: universal comprehension as the stated purpose of the reading, not simply correct oral transmission. |
| Recommended strategy | Do not avoid the accurate cognate vocabulary — there is no substitute, and avoiding it would itself be a mistranslation. Instead, let the passage’s own emphasis do the fencing: every occurrence of قرأ in ch. 8 must be translated in visible proximity to its paired فهم/تفسير clause (v.8’s “gave the sense, so that the people understood the reading” is the load-bearing sentence of the whole chapter and must never be trimmed for economy). This is a case where the source text itself already supplies the theological correction; the translator’s job is to preserve that internal argument’s visibility, not to add external apologetic material into the verse itself (reserve that for teaching notes). |
1.4 Confession and Covenant Renewal
| Element | Detail |
|---|---|
| Key terms | confession (الاعتراف بالخطايا), fasting (الصوم), rebelled/stiffened neck (تمردوا/صلّبوا رقابهم), compassionate and gracious (رحيم وحنون), seal (ختم), tithe (العُشر), separated (انفصل/فصل) |
| Available Arabic vocabulary | Individually available, but the genre — extended corporate, multi-generational, liturgically rehearsed national confession (ch. 9) — has no ready-made Arabic devotional analog to draw the translator toward; Islamic tawbah is structured as an individual, direct, unmediated transaction. |
| Weakness | Two distinct weaknesses stack here. First, a missing-genre gap: there is no set Arabic devotional-liturgical vocabulary for corporate historical confession comparable to what exists for individual repentance, so translators may default to individualizing language that loses ch. 9’s corporate, generational scope. Second, a crowded-neighborhood gap on both الصوم (Ramadan’s fixed pillar) and ختم (echoing khatam an-nabiyyin, “Seal of the Prophets”). |
| Recommended strategy | For the missing-genre gap: preserve first-person-plural and generational-scope grammar faithfully from the Hebrew (ch. 9’s repeated “our fathers… we”) rather than smoothing it into first-person-singular devotional Arabic prose patterns common in personal-piety literature. For الصوم and ختم: retain the accurate terms (no substitute exists) but require a one-line disambiguating gloss at first occurrence of each — الصوم as “occasional, crisis-driven abstention,” ختم as “ratifying this specific covenant document,” not a finality-of-revelation claim. |
1.5 The Joy of the Lord as Strength
| Element | Detail |
|---|---|
| Key terms | joy of the LORD (فرح الرب), strength (قوتكم), great rejoicing (فرح عظيم), send portions (أرسلوا حصصًا) |
| Available Arabic vocabulary | فرح is unproblematic, broadly shared vocabulary across Arabic religious registers with no direct Islamic-technical competing sense. |
| Weakness | The risk here is not lexical collision but a conceptual-neighbor risk: Arabic religious literature (particularly Sufi-influenced popular piety) has a well-developed vocabulary for mystical ecstatic states (e.g., وجد, wajd) attained through ritual practice (dhikr, sama’). فرح الرب could be pastorally absorbed into that category — joy as an attained spiritual state pursued for its own sake — rather than 8:10’s actual structure: joy as the settled result of having heard, understood, and been assured of forgiveness through God’s word (v.9-10 is explicitly a response to weeping over conviction of sin, resolved by assurance, not induced by ritual technique). |
| Recommended strategy | Retain فرح الرب exactly (established Van Dyck-tradition rendering; no viable alternative). Fence the concept, not the word: teaching material accompanying 8:10 must state the causal chain explicitly — reading → understanding → confession/assurance → joy — so فرح الرب is anchored as fruit of the Word rightly heard, structurally parallel to (and worth cross-referencing against) the baseline’s caution on السلام in Romans 5:1, which draws the identical distinction between relationally-secured peace and self-generated tranquility. |
1.6 Opposition and Perseverance in God’s Work
| Element | Detail |
|---|---|
| Key terms | mockery (استهزاء/سخرية), guard/watch (حرس/حراسة), fear/do not fear (خوف/لا تخافوا), fear of God (مخافة الله), falsehood (كذب/افتراء), false prophecy (نبوءة كاذبة), interest/usury (الربا), brother/kinsman (أخ) |
| Available Arabic vocabulary | Nearly all terms are common, cross-register Arabic vocabulary with strong genuine points of contact (الربا is the Qur’an’s own prohibited-usury term; أخ maps usefully onto ukhuwwah/brotherhood ethics). |
| Weakness | The only structural risk is conflating two distinct “fear” categories that happen to share overlapping vocabulary fields in English translation tradition: dread of enemies (خوف, negative, to be rejected — 4:14) versus reverent covenant fear of God (مخافة الله, positive, to be cultivated — 5:9,15). Because both are called “fear” in English, careless Arabic rendering could blur Nehemiah’s own sharp distinction between the two. مخافة الله additionally parallels taqwa, understood in Islamic ethics as an independently meritorious, reward-accumulating virtue rather than (as here) a fruit of an already-secured covenant relationship. |
| Recommended strategy | Keep خوف/لا تخافوا and مخافة الله as two visibly distinct lexical families (never render both with the same root in a way that could blur them) and use 4:14’s own logic (remember the great and awesome God, and you need not fear men) as the teaching anchor showing the two fears are not merely different intensities but different objects entirely. For مخافة الله’s taqwa-parallel: root it explicitly in ch. 5’s narrative (Nehemiah’s own restraint from exploiting the poor, flowing from a God who has already redeemed Israel) rather than presenting it as a stand-alone virtue accruing standing before an as-yet-undetermined judgment. |
Section 2 — Missing Vocabulary vs. Crowded Semantic Neighborhoods
Nehemiah’s linguistic risk profile splits cleanly into two different failure modes, and they require opposite translation strategies. Confusing the two — applying a fencing strategy to a genuine gap, or hunting for new vocabulary where the problem is really crowding — is itself a translation risk.
2.1 Missing Vocabulary (no ready Arabic equivalent — requires compound phrase or paraphrase)
| Concept | Why Arabic lacks a ready single-word equivalent | Recommended construction |
|---|---|---|
| Dependence on God (thematic, no single Hebrew lexeme either) | The closest single Arabic word (التوكل) is already claimed by a specific, technical, competing Islamic theological framework (see 2.2). A genuinely new-to-this-context compound is needed. | الاعتماد على الله — retain as fixed compound; never abbreviate to a single word in running text. |
| Corporate, multi-generational national confession as a genre (ch. 9) | No dedicated Arabic devotional-liturgical noun for this genre exists distinct from individual repentance vocabulary. | Preserve as a descriptive clause rather than seeking a single noun: الاعتراف الجماعي بخطايا الأجيال (“the corporate confession of the generations’ sins”) at structurally important points (9:2-3 opening), rather than compressing to الاعتراف alone. |
| ”Gave the sense” / meforash-sekhel (8:8) — explanation that conveys interpreted meaning, not merely audible clarity | Arabic has words for “clearly” (بوضوح) and “explained” (فسّر) separately, but no single term capturing “read-plus-interpreted-so-that-meaning-landed” as one idea. | Retain the compound بوضوح وتفسير (المعنى) — resist the temptation to collapse to a single adverb, since the doctrinal point of the verse depends on holding both clarity-of-delivery and interpretive-explanation together. |
| ”Remember me, O my God, for good” refrain’s specific self-referential, personal-covenant-audit sense (13:14,22,29,31) | Generic اذكرني (“remember me”) does not by itself carry the refrain’s covenant-ledger connotation (an appeal to God’s own record-keeping of covenant faithfulness, not a request for mere recollection). | Retain the fuller compound اذكرني يا إلهي (للخير) at every occurrence rather than shortening to اذكرني alone, to keep the “for good/favorably” qualifier that anchors the appeal to covenant faithfulness rather than bare memory. |
2.2 Crowded Semantic Neighborhoods (term exists and is accurate, but its dominant contemporary association actively competes — requires fencing, not replacement)
| Term | Occupying Neighbor | Severity | Fencing strategy |
|---|---|---|---|
| قرأ / القراءة (read/the reading) | القرآن (al-Qur’ān, “the recitation”) — same root, one derivational step away | Critical | Never let a قرأ clause stand without its comprehension pairing (فهم) in the same sentence or immediately adjacent clause; see 1.3 above. |
| الصلاة (prayer) | ṣalāt, Islam’s five fixed daily ritual prayers | High | Emphasize spontaneity and occasion-specificity in surrounding narrative framing at every major prayer scene (1:4-11; 2:4; 4:9; 9:5-37). |
| الصوم (fasting) | Ramadan, obligatory month-long fast, a Pillar of Islam | High | Gloss as occasional/crisis-driven at first occurrence (1:4); do not let it stand unqualified. |
| سجد / انحنوا وسجدوا (bowed/prostrated) | sujūd, the technical posture of Islamic ritual prayer | High | Frame explicitly in 8:6 as spontaneous response to hearing God’s word and the corporate “Amen,” not a liturgical sequence. |
| الجماعة (assembly/gathered) | jamā’ah, the congregation for congregational ṣalāt | Medium | Context (Scripture-hearing setting, not prayer-direction/qibla language) should disambiguate; supply an explicit teaching note at 8:1-2. |
| اذكرني / تذكروا (remember me / remember, exhortation) | dhikr, ritual repetitive remembrance practice | Critical (13:14 refrain) / Medium (4:14 exhortation) | State the reversed direction of address explicitly at 13:14: the human petitions God to remember, not a human ritual act of remembering God. |
| ختم (seal/sealed) | khatam an-nabiyyin, “Seal of the Prophets,” Muhammad’s finality claim | Medium | One-line gloss at 9:38/10:1: this seals one specific document, not a claim about revelation’s finality. |
| المدينة المقدسة (the holy city) | al-Quds, Jerusalem’s Islamic sacred-geography title, plus contemporary political conflict | High | Deliberate pastoral framing distinguishing 11:1’s covenant-historical claim from later Islamic sacred-geography claims and present-day politics; do not silently soften the phrase. |
| قربان (offering, incl. wood-offering) | Levitical sacrifice / Eastern Christian Eucharistic al-Qurban al-Muqaddas / Islamic Eid qurbani — three distinct live referents sharing one root | Medium | Specify referent explicitly every time: “قربان (الحطب)” for 10:34/13:31’s altar-wood supply system specifically. |
| العُشر (tithe) | zakāt, a Pillar of Islam with a different formula (≈2.5% of qualifying wealth) and basis | Medium | Anchor to the specific Levitical/temple-support system; do not let it read as a zakat equivalent. |
| الربا (interest/usury) | Qur’an’s own explicit prohibition (Q2:275) | Low (positive bridge) | Genuine shared ground; keep covenant-brotherhood basis explicit rather than a fiqh legal category. |
| مخافة الله (fear of God) | taqwa, a Qur’anic virtue independently accruing merit | High | Root explicitly in prior covenant relationship (ch. 5), not stand-alone merit. |
| الوالي (governor) | وَلِيّ (wali, “patron/saint”) — shared root, unrelated sense here | Low | Context (civil office) sufficiently disambiguates; no active fencing required beyond consistency. |
Interpretive principle: in every Critical/High row above, the correct strategy is never to reach for a different Arabic word — the listed term is, in each case, the linguistically correct and often the only available rendering. The gap is never lexical; it is that the correct word already has a full, well-formed, competing meaning installed in the reader’s mind by a different tradition. The remedy is contextual fencing (explicit teaching notes, deliberate narrative framing, and — where the source text itself supplies it, as in 8:8’s own explanation-clause — simply preserving what the text already does).
Section 3 — Transliteration vs. Paraphrase Decisions
Nehemiah contains far fewer bare transliteration candidates than Romans (no Aramaic Abba-class terms), but several decisions must still be fixed before Phase 2 segment translation begins.
| Item | Decision | Rationale |
|---|---|---|
| Nehemiah (personal name) | Transliterate: نحميا (Naḥamyā) | Established Van Dyck/NAV form; no alternative needed. |
| Ezra (personal name) | Transliterate: عزرا (‘Ezrā) | Established form; note Ezra also functions in Islamic tradition as a figure of some (contested) identification with Uzair (Q9:30) — do not import that association; keep strictly to the Nehemiah narrative’s scribe-priest office. |
| Susa, Elephantine, and Persian court-office proper nouns (1:1,11) | Transliterate using standard historical-geographic Arabic forms already established in Arabic Old Testament tradition (e.g., شوشن for Susa) | Consistency with existing Arabic OT translation tradition avoids introducing novel geographic forms mid-curriculum. |
| Feast of Booths / Sukkot (8:14-18) | Paraphrase using the established descriptive rendering عيد المظال (“Feast of Shelters/Booths”), not a transliteration of Sukkot | عيد is a safe, shared generic festival word; a transliterated “Sukkot” would introduce an unfamiliar loanword with no established Christian Arabic Bible precedent, unlike، e.g., “Hallelujah.” Follow existing Van Dyck-tradition rendering. |
| Hallelujah / Amen equivalents, if present in liturgical refrains (cf. 8:6’s “Amen, Amen”) | Retain transliterated آمين per baseline convention | Baseline (12_ai_translation_requirements.md) already fixes آمين and هللويا as retained transliterations; Nehemiah 8:6’s doubled “Amen, Amen” should render as آمين، آمين with no substitution. |
| Selah-class liturgical markers | Not present in Nehemiah; no decision needed | Noted for completeness — avoid importing Psalms-translation conventions where the source text does not require them. |
| ma’oz (מָעוֹז, “strength/stronghold,” 8:10) | Paraphrase, not transliterate: قوتكم (primary), with حصنكم available as a contextual gloss, never as the primary rendering | Established Arabic Bible tradition already resolves this to “strength” as primary sense (per baseline glossary); transliteration is not appropriate for a common Hebrew noun with a clear semantic (not proper-noun) function. |
| ḥesed (חֶסֶד) | Paraphrase as fixed compound المحبة الثابتة, not transliterated and not single-word رحمة | Per baseline “grace” methodology: a single common Arabic word cannot carry the unilateral covenant-loyalty sense; a compound is required, and the compound must be held constant everywhere ḥesed occurs in Nehemiah (1:5; 9:17,32). |
| raḥum ve-ḥannun (רַחוּם וְחַנּוּן, 9:17,31) | Paraphrase using existing Arabic divine-attribute cognates: رحيم وحنون — deliberately reuse vocabulary that already exists in the target language’s shared religious register, rather than avoiding it | Unlike ḥesed, this is a case where genuine shared cognate vocabulary exists (as with الله itself) and avoidance would be linguistically artificial; the fencing need here is not lexical substitution but explicit covenant-historical anchoring (see Section 1.4 and glossary entry). |
| Feast/festival names generally (Passover, Weeks, Booths — 8:14; cf. 10:33) | Use established Arabic OT festival vocabulary consistently across the curriculum, not ad hoc description | Prevents each occurrence from being independently re-translated with drifting vocabulary. |
General rule applied throughout: transliteration is reserved for proper nouns and for the small closed set of universally-retained liturgical exclamations already fixed by the baseline (آمين, هللويا). Every common-noun theological concept — even where Hebrew has no exact one-word Arabic match — is resolved by a fixed compound paraphrase, held constant at every occurrence, rather than either a novel coinage or a borrowed foreign term. This matches the baseline’s own resolution pattern for terms like “imputed righteousness” (البر المحسوب) and “obedience of faith” (طاعة الإيمان).
Section 4 — Ranked List of Highest-Risk Ambiguities for Nehemiah
Ranked by combined weight of (a) doctrine risk tier, (b) collision severity with dominant Islamic vocabulary, and (c) frequency/centrality within the core passage (Nehemiah 8:1-12) and the book as a whole.
-
قرأ / القراءة (read / the reading) — Critical. Root-adjacent to al-Qur’ān itself; concentrated exactly in the core passage (8:3,8,18); the single highest-density collision risk in the book because it sits at the intersection of the book’s structural keyword and the curriculum’s core doctrine (The Word of God Read, Understood, and Obeyed).
-
سجد / انحنوا وسجدوا (bowed/prostrated) — Critical. Exact technical cognate of Islamic sujūd; occurs at the emotional and theological climax of the core passage (8:6), immediately following the doubled “Amen, Amen” — a moment readers are most likely to visually/kinesthetically map onto a familiar ritual posture.
-
اذكرني يا إلهي (للخير) — the “remember me” refrain — Critical. Direction-of-address inversion relative to dhikr; recurs four times (13:14,22,29,31) as Nehemiah’s personal theological signature, making a single missed fencing note at first occurrence propagate across the book’s conclusion.
-
الاعتماد على الله (dependence on God) — Critical. Governs the entire book’s leadership theology; its natural-language alternative (التوكل) is a live, named, technical competing virtue, so the risk is not occasional but constant and pervasive across every leadership decision Nehemiah narrates (2:4-8; 4:9; 4:14; 6:9).
-
رحيم وحنون (compassionate and gracious) — Critical. Genuine cognate overlap with Allah’s most prominent names in Islamic theology; positioned at the theological center of the ch. 9 confession, where a failure to anchor it covenant-historically could make the entire national confession read as generic Islamic theology proper rather than a specifically Trinitarian, covenant-keeping God’s self-revelation.
-
المدينة المقدسة (the holy city) — High. Lower frequency (only 11:1,18) but exceptionally high real-world stakes given contemporary political sensitivity; a mishandled rendering risks derailing an entire teaching session into contemporary politics rather than covenant history.
-
الصلاة (prayer) — High. Pervasive across the whole book (1:4-11; 2:4; 4:9; 9:5-37); risk is diffuse rather than concentrated, but the sheer frequency means an unfenced first occurrence (1:4) will color every subsequent prayer scene.
-
الصوم (fasting) — High. Concentrated at two key structural points (1:4; 9:1) bracketing the book’s confession material; moderate frequency but high specific-practice collision (Ramadan).
-
الجماعة (gathered assembly) — Medium-High. High frequency across communal scenes (8:1-2 and throughout chs. 9-10) but generally well-disambiguated by surrounding Scripture-hearing context; risk is real but more easily contained than items 1-8.
-
فهم / يفهم (understand) — High (positive risk direction). Included here not as a collision risk but as the primary mitigation resource for items 1 and 2 above — its five-fold repetition in ch. 8 is the text’s own built-in fencing mechanism, so translators must resist any impulse to vary its rendering for stylistic economy; consistency here is what neutralizes the top two risks on this list.
Section 5 — Chapter Coverage Confirmation
| Chapters | Linguistic gap issues surfaced | Status |
|---|---|---|
| 1–2 | Prayer/dependence crowding (الصلاة, الاعتماد على الله), fasting, hand of God idiom, exile/captivity anchoring | Reviewed |
| 3 | Gate-name consistency (low risk, construction vocabulary) | Reviewed — no new gap beyond Section 1.2 |
| 4–6 | Fear/fear-of-God bifurcation, remember-exhortation dhikr-adjacency (lower severity than ch.13 refrain), usury positive bridge, false-prophecy handling | Reviewed |
| 7 | Administrative vocabulary only; no new gap-class issues | Reviewed |
| 8 (core, 1-12) | Full concentration of the top four ranked risks (قرأ/القراءة, سجد, الجماعة, فهم); anchor passage for Section 1.3 and Section 2.2 fencing strategy | Reviewed in full |
| 8 (13-18) | Feast of Booths transliteration-vs-paraphrase decision | Reviewed |
| 9 | ḥesed compound decision, raḥum ve-ḥannun cognate-reuse decision, corporate-confession missing-genre gap | Reviewed |
| 10 | Seal/khatam adjacency, tithe/zakat adjacency, qurban three-way adjacency | Reviewed |
| 11 | The holy city / al-Quds political-sensitivity risk (ranked #6) | Reviewed |
| 12 | Dedication anachronism caution (Hanukkah), thanksgiving/David reused terms — no new gap class | Reviewed |
| 13 | ”Remember me” refrain (ranked #3), separated/defiled ethnic-exclusivism framing risk | Reviewed |
Every chapter of Nehemiah has been reviewed for linguistic-gap and crowded-neighborhood risk; no chapter was silently omitted. This analysis, together with analysis/08_core_glossary.md and the Nehemiah bible_term_registry.json, should be loaded before finalizing the Nehemiah doctrine_risk_registry.json and before any Phase 2 segment translation begins.