Log in

or use your email

Search the Library

Keyword search across Doctrine Analysis, Core Glossary, Comparative Theology, and Regional Analysis. Mention a language name for the best results — e.g. "remnant burmese" or "what glossary terms conflict for burmese."

Type at least 2 characters to search.

Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Stay informed Get our weekly newsletter. Never sold or shared, unsubscribe anytime.

Let us serve you Church leaders and ministry networks seeking translated curriculum Join our team Volunteers interested in reviewing translations
Download Translation Skill

Linguistic Gap Analysis

Linguistic Gap Analysis: Daniel

English → Arabic Language Package Extension | Curriculum: Daniel

Generated: Phase 1, Step 8 Companion documents: analysis/07_semantic_analysis.md (produced in parallel), analysis/08_core_glossary.md (downstream), baseline translation_memory.json, baseline bible_term_registry.json, baseline doctrine_risk_registry.json Core passage: Daniel 7:9-14 (the Ancient of Days and the Son of Man) Scope: Full book, Daniel 1–12


Purpose

This document performs the linguistic gap analysis required before glossary construction (Step 08) and doctrine risk registry extension. It identifies, for each doctrine in scope:

  1. What Arabic vocabulary is already available (from the baseline Romans package, from the Van Dyck/NAV Christian Arabic Bible tradition, or from general MSA) and where that vocabulary is adequate, strained, or absent.
  2. Where semantic neighborhoods are crowded (multiple candidate Arabic terms compete, each carrying different doctrinal risk) and need explicit “fencing” — boundary-setting notes that rule out the wrong neighbor.
  3. Where vocabulary is genuinely missing — no existing Arabic term (Christian or Islamic) cleanly carries the required sense, requiring either a compound coinage or an established but currently under-specified term to be given a fixed technical sense.
  4. Where transliteration is preferable to paraphrase, and why.
  5. A ranked list of the highest-risk ambiguities specific to this curriculum, to drive Phase 2 review routing priority.

This analysis does not contradict the baseline; every term the baseline fixes for Romans remains fixed here. The task is to map the additional terrain Daniel’s apocalyptic-court-narrative genre requires that Romans’ epistolary genre did not.


1. Doctrine Vocabulary Matrix

For each of the six curriculum doctrines: the available Arabic term(s), their weaknesses, and the recommended strategy. “Available terms” includes both baseline-inherited vocabulary and native Arabic/Islamic-register candidates considered and rejected.

1.1 God’s Sovereignty over Kings and Kingdoms

Available Arabic Term(s)WeaknessRecommended Strategy
مُلك (mulk, “sovereignty/dominion”)This is the Qur’an’s own vocabulary for God’s kingship (e.g., Q3:26 “تُؤتِي الْمُلْكَ مَن تَشَاءُ” — “You give the mulk to whom You will,” almost verbatim to Daniel 4:17,25,32). Using it verbatim would make Daniel’s sovereignty doctrine read as a bare restatement of a Qur’anic verse rather than a distinct redemptive-historical claim.Fence, don’t adopt. Use ملكوت (never مُلك) for God’s/Son of Man’s eternal kingdom (per baseline kingdom_of_god), and مملكة for the temporal empires. Retain “يُعطي الملكوت لمن يشاء” as the fixed rendering of the recurring clause — close enough to be recognizable as a bridge, distinct enough not to be a citation.
سلطان (sultan, “authority/dominion”)Correct denotatively for שׇׁלְטָן/sholtan, but carries strong connotations of the historical Islamic political title (Ottoman Sultan), risking a reading of the Son of Man’s dominion as one more (if greater) human-style sultanate.Use with mandatory qualifier. Always pair سلطان with أبدي/دائم (“eternal/everlasting”) or a clause marking transcendence at 7:14, 7:27; do not let it stand alone in Christologically load-bearing verses.
العناية الإلهية (providence)Adequate as inherited from baseline; no independent Daniel-specific weakness, but risk is elevated by the mulk/qadar proximity issue above (§1.1 row 1) and by folk fatalism generally (see baseline election/providence notes).Reuse exactly; reinforce with explicit redemptive-trajectory framing at every occurrence (per baseline strategy).
رئيس / أمير (ra’is/amir, “prince/ruler”) for “Prince of Persia,” “Prince of the host”Adequate; أمير in particular carries some contemporary political-title baggage (cf. “Emir”) that could read anachronistically.Prefer رئيس over أمير for the angelic “princes” (10:13,20; 8:11) to avoid contemporary political-title resonance; reserve أمير, if used at all, for human political rulers only.

Overall gap: No true vocabulary gap here — the risk is a crowded neighborhood between Qur’anic mulk-language and the baseline’s ملكوت/مملكة split. This is a fencing problem, not a missing-word problem, already addressed by the Step-08 glossary’s strategy decision (§D.1-2 of 08_core_glossary.md) and reaffirmed here.


1.2 Faithfulness under Persecution

Available Arabic Term(s)WeaknessRecommended Strategy
الشهادة / الشهيد (shahada/shahid, “martyrdom/martyr”)Not used in Daniel’s narrative (no character dies for faith in the canonical text — the three young men and Daniel are all delivered), but this vocabulary sits immediately adjacent to the doctrine and will be reached for by teachers drawing application. الشهيد in Islamic usage denotes a battlefield/violent-death martyr with paradise guaranteed by that death itself, a merit-earning framework absent from Daniel and from NT theology of suffering.Explicitly avoid and flag in teaching notes: Daniel’s protagonists are models of faithful refusal under threat of death, not martyrs who die. If NT martyrdom material is cross-referenced (e.g., in application questions), distinguish Christian martyrdom (a consequence of faithfulness, not a merit-earning act) from Islamic shahada explicitly.
يتنجّس / يتدنّس (defile oneself, 1:8)Adequate; already vetted in Step-08 glossary against ritual-purity (wudu) framing.Reuse exactly as fixed.
الصمود / الثبات (steadfastness, perseverance — generic MSA)No baseline precedent; broadly safe but theologically thin on its own (could describe any stoic endurance, religious or secular).Use as supporting vocabulary in teaching prose (not as a fixed glossary term), always anchored explicitly to trust in God (الإيمان) as the reason for steadfastness, per Daniel 3:17-18 and 6:23.
التمثال (idolatrous image, ch.3)Adequate; already fixed in registry.Reuse exactly.

Overall gap: No missing vocabulary. The risk is entirely in adjacent-neighborhood contamination from shahada/shahid vocabulary that will be culturally close-at-hand for any Arabic speaker discussing costly faithfulness, even though the text itself never uses martyrdom vocabulary. This must be fenced in teaching notes rather than in the glossary per se, since the term itself never occurs in-text but will recur in derived pedagogical material.


1.3 The Son of Man and Messianic Kingship

This is the doctrine with the highest concentration of Critical-risk gaps, converging directly on the core passage (Dan 7:9-14).

Available Arabic Term(s)WeaknessRecommended Strategy
ابن الإنسان (Ibn al-Insān, “Son of Man”)Correct and already the fixed Gospel-tradition rendering of Jesus’s self-title — but Daniel’s Aramaic כְּבַר אֱנָשׁ is explicitly comparative (“like/as a son of man,” not a bare title at this stage of revelation). A flat ابن الإنسان without the comparative particle would silently convert Daniel’s veiled vision-language into the fully disclosed Gospel title before the text itself does so.Retain comparative marker at 7:13: “واحدٌ كابن إنسان” or “شبه ابن إنسان” (“one like a son of man”), with a footnote establishing continuity to the fixed Gospel title. Only in cross-referenced NT material does the bare title ابن الإنسان stand alone.
المسيح (al-Masih)Adequate and already fixed (baseline + 9:25-26); no independent Daniel-specific weakness beyond the baseline’s general Qur’anic-loading caution.Reuse exactly; leverage 9:26 apologetically as pre-Christian, pre-Qur’anic testimony to a suffering Messiah.
يعبد (worship, cultic) vs. يخدم (serve)See baseline registry worship_serve_cultic — this is the decisive lexical crux of the whole doctrine at 7:14.Fixed: يعبدونه only, never يخدمونه. No permitted deviation (see §D.3 of Step-08 glossary).
القديم الأيام (Ancient of Days)Adequate Van Dyck-established rendering; genuine positive bridge to Islamic qidam (the divine attribute of having-no-beginning), but the bridge is a double-edged one: familiarity could domesticate the confrontational claim of v.14 (a co-enthroned figure receiving what tawhid reserves for Allah alone).Reuse exactly; every occurrence must be paired with explicit teaching-note reinforcement of the deity-claim implication, not left to stand as comfortable shared vocabulary alone.
سلطان (see §1.1)Same crowded-neighborhood issue as above, intensified here because it is applied directly to the Son of Man himself (7:14), the single most theologically load-bearing occurrence in the book.Same qualifier strategy as §1.1, applied with maximum rigor at 7:14 specifically — mandatory theologian sign-off, no unqualified سلطان in this verse.
المجد (glory)Adequate, already fixed; genuinely useful cross-book bridge (same term used for Christ’s glory in Romans, now shown applied to the Son of Man in Daniel six centuries earlier).Reuse exactly; surface the cross-book parallel explicitly in teaching notes as apologetic material.
سحاب السماء (clouds of heaven)No lexical weakness; the risk is purely in under-teaching the implicit theophany claim (clouds as exclusively God’s mode of appearing elsewhere in Scripture).Reuse baseline registry entry clouds_of_heaven; mandatory teaching-note cross-reference to Matthew 24:30/26:64.
العروش (thrones, plural, 7:9)Genuine ambiguity risk: a plural “thrones” around a singular Ancient of Days could, if mishandled in paraphrase, read as suggesting multiple co-equal deities — precisely the shirk accusation Trinitarian doctrine must not appear to validate from the wrong angle (i.e., polytheism, not Trinity).Footnote required at first occurrence: the attendant thrones constitute a heavenly council/court, not rival sovereigns; the Ancient of Days alone is enthroned as Sovereign.

Overall gap: This doctrine has the sharpest true vocabulary gap in the curriculum: Arabic (like English) has no single lexeme that simultaneously (a) preserves the vision’s own tentative comparative register at 7:13, and (b) maintains an unbroken lexical bridge to the fully disclosed Gospel title. The resolution is a fixed compound formula (كابن إنسان / شبه ابن إنسان) rather than either a bare title or a paraphrase — a linguistic decision that must be locked identically across every occurrence and cross-referenced document.


1.4 Apocalyptic Prophecy and the End Times

Available Arabic Term(s)WeaknessRecommended Strategy
آخر الزمان (time of the end)Crowded neighborhood, maximal collision: this is the exact standard term for the Islamic eschatological schema (the Hour, signs of the Hour, al-Dajjal, al-Mahdi, the return of ‘Isa). Any Arabic reader will import that entire schema by default upon encountering this phrase.No viable substitute exists without sacrificing comprehensibility (see Step-08 §D.4). Retain, but treat as mandatory-footnote vocabulary: every occurrence requires an explicit distinguishing note contrasting Daniel’s/Revelation’s schema (centered on the Son of Man’s return and vindication of the saints) with the Islamic Dajjal/Mahdi/‘Isa schema. This is the single heaviest footnote-burden term in the curriculum.
الدجّال (al-Dajjal) — considered and rejected as a gloss for “little horn” / “beast” / antichrist figuresWould be the single most damaging possible mistranslation choice in this doctrine: it would fully merge Daniel’s antichrist imagery into a specific, doctrinally elaborate Islamic end-times figure with his own biography (one-eyed, imprisoned on an island, etc.) foreign to the text.Absolute prohibition. Never use الدجّال anywhere in Daniel curriculum material, including in comparative/teaching footnotes where it must only be named (in a clearly bracketed comparative aside) never used as a translation or gloss.
القرن الصغير (little horn)Adequate as a literal rendering; no lexical weakness, but the two distinct historical referents (ch.7, ch.8) risk conflation if not tagged at every occurrence.Reuse exactly per glossary; append a chapter-tag (“القرن الصغير في الرؤيا السابعة” / ”…الثامنة”) at first occurrence in any derived teaching material spanning both chapters.
الوحش (beast)Adequate; already fenced against كائن حي/حيوان per glossary.Reuse exactly.
الرِّجْس المُخرِّب (abomination that makes desolate)No natural single Arabic word covers both “detestable/idolatrous” and “causes desolation/ruin” simultaneously; this is a constructed compound, not an inherited fixed phrase from Van Dyck tradition. Risk: translators unfamiliar with the compound may simplify to plain “نجاسة” (impurity) or “خراب” (ruin) alone, losing half the sense.Lock the full compound الرِّجْس المُخرِّب as a unit; never split or abbreviate. Apply the two-layer scaffolding (historical fulfillment under Antiochus IV, then NT reapplication) at every occurrence, per registry note.
السبعون سُبوعًا (seventy weeks/sevens)Genuine translation choice gap: literal “أسبوعًا” (weeks, i.e., seven-day weeks) versus the correct sense “سبعا سنين” (sevens of years). A reader defaulting to the everyday sense of “week” will miscalculate the entire prophetic timeline.Render السبعون سُبوعًا (using the less common but etymologically accurate سُبوع rather than أسبوع) with a mandatory explanatory gloss “أي سبعين فترة من سبع سنين” (“that is, seventy periods of seven years”) at first occurrence in every document.

Overall gap: This doctrine has the single heaviest fencing burden in the curriculum (آخر الزمان) and one genuinely constructed/compound term with no prior Christian Arabic precedent to lean on (الرِّجْس المُخرِّب). Both require standing, repeated teaching-note infrastructure rather than one-time footnotes.


1.5 Prayer and Perseverance in Exile

Available Arabic Term(s)WeaknessRecommended Strategy
الصلاة (prayer)Adequate lexically, but maximally crowded neighborhood: صلاة is also the exact term for the second Pillar of Islam, a codified, fixed-times, fixed-direction, ritually-prescribed obligation (five times daily, facing the Kaaba). Daniel’s practice (three times daily, facing Jerusalem, 6:10) is structurally similar enough that the resemblance is not merely lexical but practical, raising the risk of the text being read as biblical endorsement/precedent for the Islamic Pillar structure itself.Retain الصلاة (no viable substitute — الدعاء [“supplication/petition”] is too weak for the sustained, disciplined pattern in view). Mandatory teaching note at 6:10-11 and 9:3ff: Daniel’s prayer is personal covenant-relational petition maintained voluntarily under threat, not a fixed ritual Pillar; Jerusalem-orientation reflects covenant/temple theology (1 Kings 8:44-48), not a qibla in the technical Islamic sense.
الاعتراف (confession of sin)Adequate; already fenced against sacramental confession-to-a-priest sense.Reuse exactly.
السبي (exile)Adequate; carries legitimate, welcome pastoral resonance for Arabic-speaking Christian minorities.Reuse exactly; may be positively leveraged in application material (not a risk to fence, an asset to use intentionally).
الصوم (fasting, implied 9:3; 10:2-3)Not yet in the registry. Adequate lexically — shared vocabulary with Islamic sawm/siyam (a Pillar), but far less doctrinally loaded than salat, since fasting-as-spiritual-discipline is broadly cross-religious and the NT itself commends it (Matthew 6:16-18) without controversy.Add الصوم to the registry as Medium risk; note the shared-practice bridge is safe (unlike salat) but should still specify Daniel’s fasting as an act of urgent covenant petition/mourning, not a fixed calendrical obligation (contrast Ramadan).

Overall gap: No missing vocabulary. The Prayer doctrine’s central risk is the single most practically (not just lexically) crowded neighborhood in the whole curriculum: الصلاة denotes an entire ritual system in the target culture that Daniel’s narrative structurally resembles at the level of practice (fixed times, spatial orientation), not merely at the level of word choice. This requires sustained pastoral/teaching framing beyond a footnote — recommend a dedicated teaching sidebar wherever 6:10-11 or 9:3-19 is treated in Phase 2 output.


1.6 Wisdom and Discernment from God

Available Arabic Term(s)WeaknessRecommended Strategy
الحكمة (wisdom)Adequate; positive bridge to Qur’anic ḥikma (Q2:269), already vetted.Reuse exactly per glossary (الحكمة والفهم for the paired construct).
السر (mystery/secret)Crowded neighborhood with Sufi سِرّ (perpetual esoteric gnosis for initiates within a batin/esoteric hierarchy).Already fenced in glossary; reinforce that Daniel’s raz is time-bound and fully disclosed, the opposite epistemic structure from Sufi sirr.
التفسير (interpretation)Adequate; already fenced against تأويل’s Sufi/Shi’i esoteric-hermeneutics connotation.Reuse exactly.
الحكماء المتبصّرون (those who are wise/discerning, 12:3,10)This is a constructed compound, not a single inherited Arabic Bible term — المتبصّرون (“those who perceive/discern deeply”) is added to الحكماء to capture ha-maskilim’s active, causative sense (“those who cause understanding/give insight to others”), which الحكماء alone (simple “wise ones”) under-translates.Lock the compound; do not allow simplification to bare الحكماء in any derived material, since that would lose the crucial “leads many to righteousness” (teaching/discipling) component of 12:3.
الفطنة / البصيرة (discernment — generic MSA alternatives considered)Both are viable generic Arabic words for discernment/insight, but neither is yet anchored to any fixed Bible-translation precedent for this doctrine.Not adopted as primary terms; reserved as descriptive vocabulary in teaching prose only, never as the fixed glossary rendering (avoid proliferating near-synonyms across documents).

Overall gap: No missing vocabulary beyond one constructed compound (الحكماء المتبصّرون), already resolved. This is the lowest-risk doctrine in the curriculum linguistically, though pastorally significant.


2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2.1 Genuinely Missing Vocabulary (no adequate existing Arabic term; compound/constructed rendering required)

ConceptWhy Nothing Existing FitsConstructed Solution
Abomination that makes desolate (8:13; 9:27; 11:31; 12:11)No single word carries both “cultically detestable” and “causes ruin/desolation”الرِّجْس المُخرِّب (locked compound)
Son of Man, comparative register (7:13, first disclosure)ابن الإنسان alone loses the vision’s own “like/as” qualifier; a bare title would over-disclose ahead of the textكابن إنسان / شبه ابن إنسان (locked comparative formula)
Those who are wise/discerning, causative sense (12:3,10)الحكماء alone loses ha-maskilim’s active “gives understanding to others” componentالحكماء المتبصّرون (locked compound)
Seventy weeks/sevens as a year-unit (9:24-27)أسبوع defaults to a literal seven-day week in contemporary usageالسبعون سُبوعًا + mandatory gloss “سبعين فترة من سبع سنين”
Weighed in the balances, as one-time political verdict (5:27)وُزِن في الموازين is lexically available but has no existing non-mīzān precedent in Arabic religious registers — the phrase itself doesn’t preexist outside the Islamic soteriological frameRetain the phrase but treat it as requiring constructed contextual fencing (see §2.2) rather than a different word choice — there is no alternative vocabulary, only a different frame that must be taught alongside it

2.2 Crowded Semantic Neighborhoods Requiring Fencing (adequate vocabulary exists, but competing referents in the destination culture create doctrinal risk)

Arabic TermCompeting Referent in Destination CultureFencing Required
مُلك / يُعطي الملكوت لمن يشاءQur’an 3:26’s near-identical “تُؤتِي الْمُلْكَ مَن تَشَاءُ”Reserve مُلك for teaching-note comparative discussion only; never use it as the fixed Daniel translation. Use ملكوت/مملكة split instead (already resolved).
سلطانIslamic/Ottoman political title SultanMandatory eternal/transcendent qualifier whenever applied to the Son of Man (7:14,27); never left bare in Christologically load-bearing verses.
آخر الزمانThe full Islamic eschatological schema (Hour, Dajjal, Mahdi, returning ‘Isa)No substitute exists; mandatory distinguishing teaching note at every occurrence (heaviest fencing burden in the curriculum).
الصلاةIslamic salat (Second Pillar; fixed times/direction)Mandatory contrast note wherever Daniel’s prayer practice is described in structural detail (6:10-11; 9:3ff).
وُزِن في الموازينIslamic mīzān (individual deeds-weighing at Judgment, a live soteriological category)Mandatory note: one-time historical-political verdict on a single pagan king, never a personal-salvation deeds-weighing proof text.
الشهادة / الشهيد (adjacent, not in-text)Islamic martyrdom theology (violent death itself as merit-earning, paradise-guaranteeing)Prohibit use in Daniel material; flag for exclusion in any derived application/devotional content on faithfulness under persecution.
القديم الأيامIslamic divine attribute qidam (eternity without beginning)Positive bridge permitted, but must be paired with explicit reinforcement of the confrontational deity-claim of v.14, not left as comfort-only vocabulary.
الشركة-adjacent root concerns (inherited from baseline, still relevant wherever “fellowship of saints” language appears in Daniel-based small-group material)ش-ر-ك root resonance with shirkSame baseline caution applies; avoid pairing الشركة with vocabulary suggesting “partnership with God” in Daniel-derived fellowship material.
ابن الآلهة / روح الآلهة القديسة (pagan idioms, 3:25; 4:8-18; 5:11-14)The fixed Trinitarian titles ابن الله / الروح القدسAbsolute prohibition on cross-use; this is the most severe possible glossary violation risk in the book (manufacturing false pagan Trinitarian testimony) — see §3 ranked list, item 1.

3. Transliteration vs. Paraphrase Decisions

Following the baseline’s precedent (retaining “Abba” transliterated in Romans 8:15 rather than translating it away), Daniel contains several genuinely untranslatable or high-value-retained source-language items. Decision rule applied: transliterate when the term’s foreignness/sound itself carries interpretive weight (e.g., a riddle, a name, a divine pronouncement meant to be heard as strange); paraphrase/translate fully when the term is a normal descriptive phrase whose meaning, not its sound, is the point.

ItemDecisionRationale
מְנֵא מְנֵא תְּקֵל וּפַרְסִין (Mene Mene Tekel Upharsin, 5:25-28)Transliterate, then gloss immediately: مَنا، مَنا، تَقيل، وفَرْسين — “أي: مَعدود، مَعدود، موزون، مقسوم”The narrative’s own suspense depends on the words being initially unintelligible to Belshazzar’s wise men before Daniel supplies the interpretation; translating it outright into plain Arabic from the first mention would destroy this structure. Direct parallel to the “Abba” precedent.
כְּבַר אֱנָשׁ (kevar enash, “Son of Man”)Paraphrase (comparative formula), not transliterationThis is a title/description, not a foreign sound-object; the interpretive weight is in the comparative grammar (a likeness, not yet a name), which a transliteration would not convey at all.
עַתִּיק יוֹמִין (Ancient of Days)Paraphrase (established Van Dyck rendering)Long-fixed in the Christian Arabic tradition; transliterating the Aramaic would sever this from centuries of reception history for no benefit.
דָּת דִּי מָדַי וּפָרַס (law of the Medes and Persians)Paraphrase, deliberately generic (قانون مادي وفارسي)The specific historical-legal content (irrevocability under Persian court custom) is what matters; a transliteration would add nothing and a loaded Arabic legal term (الناموس/الشريعة) would actively mislead.
שָׁבֻעִים שִׁבְעִים (seventy sevens)Paraphrase with explanatory gloss, not transliterationThe numerical-symbolic content, not the Hebrew sound, carries the doctrinal weight.
Proper names (Nebuchadnezzar, Belshazzar, Darius, Cyrus, Shadrach/Meshach/Abednego, Gabriel, Michael)Transliterate using established Arabic Bible forms (نبوخذنصّر، بيلشاصر، داريوس، قورش، شدرخ/ميشخ/عبدنغو، جبرائيل، ميخائيل)Standard Bible-translation practice; no established alternative rendering exists or should be sought, matching the baseline’s treatment of “David,” “Isaiah,” etc.
רָז (raz, mystery)Paraphrase (السر), not transliterationRaz is a common-noun concept fully expressible in Arabic; nothing is gained by transliterating a Persian loanword already absorbed into biblical Aramaic, and doing so would create an unnecessary new technical term needing its own explanation.

4. Ranked List of Highest-Risk Ambiguities

Ranked by combined severity (doctrinal centrality × probability of accidental mistranslation) for this curriculum, to drive Phase 2 review-routing priority. All items below require mandatory human theologian review per the escalation rules established in the baseline 12_ai_translation_requirements.md, extended here.

  1. يعبدونه vs. يخدمونه at Daniel 7:14. The single decisive lexical proof of the Son of Man’s deity; a single wrong verb choice by an inattentive translator or downstream editor would silently erase the entire doctrinal payload of the core passage. Zero tolerance for deviation.

  2. ابن الآلهة / روح الآلهة القديسة vs. ابن الله / الروح القدس (3:25; 4:8-18; 5:11-14). Highest-consequence cross-contamination risk in the book: confusing a pagan king’s polytheistic idiom with the curriculum’s own fixed Trinitarian titles would manufacture false textual “evidence” for Trinitarian doctrine from a pagan mouth, discrediting the genuine argument built elsewhere from Daniel 7 and the NT.

  3. The comparative register of “Son of Man” at 7:13 vs. the fully disclosed Gospel title. Collapsing كابن إنسان into a bare ابن الإنسان erases the text’s own progressive-revelation structure and risks a theologian’s/native-reviewer’s objection that the rendering “reads Christology into the text” rather than “draws Christology out of the text” — a defensible-vs-indefensible distinction that hinges entirely on this one grammatical marker.

  4. مُلك/سلطان proximity to Qur’an 3:26 and the mulk/qadar semantic field, especially at 4:17,25,32 and 7:14,27. The single highest-frequency recurring risk in the book (the “gives the kingdom to whom he wills” clause repeats three times, and سلطان/dominion language recurs at least seven times in ch.7 alone), each occurrence requiring the ملكوت/مملكة discipline and the eternal-qualifier discipline respectively.

  5. آخر الزمان’s total overlap with the Islamic end-times schema (12:4,9,13; thematically ch.7-8, 11). Not a single-verse risk but a curriculum-wide framing risk: without consistent, repeated distinguishing notes, the entire apocalyptic doctrine risks being absorbed wholesale into a Dajjal/Mahdi/‘Isa reading by any reader with standard Islamic religious education.

  6. وُزِن في الموازين (5:27) and its mīzān proximity. A single, narratively vivid, highly memorable phrase with maximal soteriological-collision potential if ever cited outside its narrow historical-political context (e.g., in an application question implying personal deeds-weighing).

  7. الصلاة’s structural (not just lexical) resemblance to salat at 6:10-11 and 9:3-19. Elevated above a typical Medium-risk term because the resemblance operates at the level of depicted practice (fixed times, spatial orientation) as well as vocabulary, making it uniquely liable to be read as scriptural endorsement of the Islamic ritual pattern itself.

  8. The two distinct “little horn” referents (7:8,20-25 vs. 8:9-12) and their proximity to al-Dajjal. Both a within-text conflation risk (historical Antiochus vs. future eschatological figure) and an across-religion conflation risk (biblical antichrist imagery vs. the fully elaborated Islamic Dajjal figure); compounding two distinct ambiguity types in one term cluster.

  9. الرِّجْس المُخرِّب’s two-layer fulfillment structure (8:13; 9:27; 11:31; 12:11). High risk not from a competing referent but from referent absence if the mandatory two-layer scaffolding (Antiochus IV, then Matthew 24:15) is dropped in any single occurrence, leaving the phrase doctrinally orphaned.

  10. القديم الأيام’s comfortable qidam-bridge softening the confrontational claim of 7:13-14. Lower urgency than items 1-9 because the term itself is doctrinally safe and well-established, but flagged because its very familiarity is what creates risk — translators and reviewers may treat it as fully resolved vocabulary and fail to attach the mandatory deity-claim teaching note, precisely because nothing about the word itself signals danger.


5. Summary and Handoff

  • No doctrine in this curriculum lacks translatable vocabulary outright. Every gap identified is either (a) a crowded neighborhood requiring fencing, or (b) a genuinely missing precise sense requiring a locked constructed compound — never a case requiring wholesale semantic substitution or doctrinal compromise.
  • The core passage (Daniel 7:9-14) concentrates the single highest density of Critical-risk ambiguities in the entire book (items 1, 3, 4, 10 above all cluster here), consistent with its role as curriculum theological anchor.
  • آخر الزمان and الصلاة carry the heaviest ongoing, curriculum-wide fencing burden (items 5 and 7), requiring standing teaching-note infrastructure rather than one-time footnotes, and should be flagged for template-level (not just per-verse) treatment in Phase 2.
  • This analysis feeds directly into analysis/08_core_glossary.md’s term list and strategy decisions (§D therein) and into the doctrine risk registry extension; no term fixed here contradicts either downstream artifact.

This document extends, and does not contradict, the baseline Romans translation_memory.json, bible_term_registry.json, and doctrine_risk_registry.json. All gap-analysis conclusions here are inputs to, not replacements for, the Step-08 glossary and the doctrine risk registry extension.

Library content is free and openly licensed under CC BY-NC-SA 4.0 — share and adapt it for non-commercial use, with attribution to tri-bible.ai.

Give feedback

How would you rate this page?

0 / 500 words