Linguistic Gap Analysis
Linguistic Gap Analysis: 2 Samuel for Portuguese Translation Requirements
Curriculum: 2 Samuel (full book, chapters 1–24)
Core passage: 2 Samuel 7:1-17
Destination language: Portuguese
Named doctrines: The Davidic Covenant and the Promise of an Eternal Throne; David’s Sin and Repentance; Consequences of Sin within the Covenant Family; God’s Steadfast Love despite Human Failure; The Messianic Hope Rooted in David’s Line
Baseline anchor: Romans Language Package (translation_memory.json, bible_term_registry.json, doctrine_risk_registry.json, 12_ai_translation_requirements.md)
0. Purpose and Method
This analysis identifies, in advance of glossary construction, where Portuguese lacks a ready-made lexical equivalent for a 2 Samuel theological concept (“missing vocabulary”), where Portuguese instead has too many semantically adjacent words competing for the same conceptual space (“crowded semantic neighborhoods”), and where a transliteration-versus-paraphrase decision must be made explicitly rather than left to translator improvisation. It also produces a ranked list of this curriculum’s highest-risk ambiguities, prioritized for Phase 2 review routing.
The baseline Romans Language Package was built entirely from New Testament Greek vocabulary rendered into Portuguese. 2 Samuel introduces an entirely different linguistic layer — Biblical Hebrew narrative and poetic vocabulary, including the covenant name of God, royal-court idiom, and Hebrew wordplay — for which the baseline provides no direct precedent. This gap analysis is therefore not a minor supplement to the baseline; it is the necessary bridge between a Greek-NT-only Language Package and the Hebrew-OT vocabulary this curriculum requires.
1. Doctrine Vocabulary Matrix
For each named doctrine: the available Portuguese term(s), their inherent weaknesses, and the recommended handling strategy.
1.1 The Davidic Covenant and the Promise of an Eternal Throne
| Concept | Available Portuguese term(s) | Weakness | Recommended strategy |
|---|---|---|---|
| berith (covenant) | aliança | None lexically; risk is conceptual — Portuguese “aliança” can denote a merely political/commercial pact (used that way secularly, e.g., “aliança comercial”) as readily as a sacred bond. | Reuse baseline “aliança” exactly (High risk per baseline). Every occurrence in 2 Sam 7/23 must carry contextual framing that this is God’s unilateral, sworn, unconditional bond, not a negotiated treaty between equals as in ch. 3. |
| bayit (house/dynasty/temple) | casa | Portuguese “casa” is a fine literal match but carries none of the Hebrew wordplay’s built-in signal that a single word is doing triple duty (palace / dynasty / temple). A Portuguese reader will not automatically detect the pun the way a Hebrew reader does. | Preserve “casa” identically at all three senses (do NOT vary to “palácio,” “dinastia,” “templo” for clarity). Compensate the lost wordplay-signal with a mandatory translator’s note at the first heavy concentration (7:1-13), since the wordplay is structurally load-bearing for the doctrine, not decorative. |
| mamlakah (kingdom, historical) | reino | Direct collision risk with baseline’s “reino de Deus” (universal, spiritual reign, Medium risk). A learner moving from Romans to 2 Samuel could import the wrong referent onto “reino.” | New entry. Use “reino” but require an explicit distinguishing note wherever the two curricula’s vocabulary meet: the Davidic “reino” is the earthly historical vehicle; the baseline’s “reino de Deus” is its ultimate fulfillment. Do not use two different Portuguese words to force the distinction lexically — the relationship is typological continuity, not synonym-avoidance. |
| kisse (throne) | trono | No lexical weakness — “trono” is an exact, stable, unambiguous match in Portuguese with no competing secular or rival-religious sense. | Low linguistic risk, high doctrinal stakes (Critical tier retained for doctrinal reasons, not lexical ones). Consistency of rendering matters more than word choice. |
| ad-olam (forever) | para sempre / eterno | Portuguese has two candidates that are NOT fully interchangeable: “para sempre” (adverbial, relational permanence) vs. “eterno” (adjectival, often philosophical/metaphysical “eternal” register, closer to timelessness than to unbroken succession). Hebrew ad-olam is closer to “unbroken into the distant future” than to philosophical timelessness. | Standardize on “para sempre” as the primary rendering (matches the covenant-promise register); reserve “eterno” for the compound “aliança eterna” (23:5) where a nominal-adjective construction is grammatically required. Do not treat the two as freely interchangeable stylistic variants. |
| kun/ne’eman (established, firm) | estabelecer / firme | No true Portuguese lexical gap, but the Hebrew root’s link to “Amém” is invisible in Portuguese unless taught. | Render consistently “estabelecer”/“firme”; add a teaching bridge to “Amém” (already retained untranslated per baseline) so the etymological reliability-connection is not lost entirely. |
1.2 David’s Sin and Repentance
| Concept | Available Portuguese term(s) | Weakness | Recommended strategy |
|---|---|---|---|
| chata (sin, general) | pecado | Reuse baseline exactly. Baseline already documents the Kardecist “erro corrigível” collision risk for this term generally; 2 Samuel’s confession scene (12:13) is precisely where that risk becomes acute, because David’s brief, personal, first-person confession is exactly the kind of terse statement a Kardecist reading could soften into “reconheço meu erro.” | Render “Pequei contra o SENHOR” (retaining the personal object), never abbreviate to “Cometi um erro” or “Falhei.” The prepositional phrase “contra o SENHOR” is not optional decoration; it is the clause that blocks the Kardecist misreading. |
| ra be’einei YHWH (evil in the LORD’s eyes) | mau aos olhos do SENHOR | Portuguese idiom “aos olhos de” already exists and carries the right evaluative sense, but a translator under stylistic pressure might soften it to “não foi bem visto” (colloquial, weak) or omit the divine-name anchor entirely (“foi errado”). | Fence the full formula as a fixed phrase; do not permit stylistic compression. This formula recurs across Samuel-Kings-Chronicles and must anchor future OT curricula consistently. |
| he’evir (guilt removed) | tirou / perdoou | Portuguese “perdoou” alone risks implying full consequence-free restoration, which 12:14 immediately contradicts (the child’s death remains). No single Portuguese verb captures “guilt judicially cleared AND temporal consequence retained” simultaneously. | Use “tirou o pecado” for v.13b and explicitly teach v.14 as a separate but adjoining clause — do not let “perdoou” stand alone without the paired consequence clause in the same teaching unit. |
1.3 Consequences of Sin within the Covenant Family
| Concept | Available Portuguese term(s) | Weakness | Recommended strategy |
|---|---|---|---|
| avon (iniquity) | iniquidade | ”Iniquidade” is a correct but somewhat archaic/formal Portuguese word, rarely used in ordinary speech; risk is not doctrinal collision but register — it may read as remote, “textbook” theological vocabulary to a less literate audience. | Retain “iniquidade” as the technical term distinguishing it from “pecado” (general sin), but pair its first occurrence with a plain-language gloss (“culpa que exige consequência”) to bridge the register gap without abandoning the technical distinction. |
| shevet anashim (rod of men, fatherly discipline) | vara de homens | Literal rendering risks reading in Portuguese as merely physical/corporal punishment imagery divorced from covenant relationship, especially given how “vara” can evoke folk-disciplinary imagery in Brazilian Portuguese unrelated to covenant theology. | Always pair with the explicit “fatherly, not rejecting” gloss; never present 7:14’s discipline clause without 7:15’s steadfast-love clause in the same teaching unit — the two verses are a single grammatical and theological unit that must not be separated in translation notes. |
| nevalah (disgraceful folly) | loucura hedionda / coisa vergonhosa | Neither candidate is a perfect match. “Loucura” in Portuguese primarily denotes irrationality/madness, understating the covenant-violation gravity; “vergonhosa” foregrounds shame/social disgrace but understates the moral-legal gravity (“such a thing is not done in Israel” is a covenant-order statement, not merely a social taboo). | Use “loucura hedionda” as the primary technical rendering (the adjective “hedionda” restores moral weight “loucura” alone lacks), with “tal coisa não se faz em Israel” retained as a fixed idiomatic clause rather than paraphrased. |
| cherev (sword, consequence-oracle) | espada | No lexical weakness. | Low linguistic risk; ensure consistent rendering across 12:10 and its narrative fulfillments in chs. 13, 18, 20 so the oracle-fulfillment structure remains visible to the Portuguese reader as it is to the Hebrew reader. |
1.4 God’s Steadfast Love despite Human Failure
| Concept | Available Portuguese term(s) | Weakness | Recommended strategy |
|---|---|---|---|
| chesed (steadfast love) | amor leal / benignidade / misericórdia | The single largest lexical gap in this curriculum. Portuguese has no one-word equivalent for chesed’s fusion of covenant loyalty + loving-kindness + faithfulness. Three candidates each fail differently: “benignidade” is archaic/theological-register-only and carries little contemporary relational warmth; “misericórdia” is the standard Portuguese rendering of the distinct Hebrew term rachamim (compassion/mercy) and would blur two separate Hebrew concepts into one; “amor” alone loses the covenantal-obligation component entirely. | New two-word compound term “amor leal” adopted as the standardized rendering (already fixed in the glossary and term registry). This is a constructed compensating solution, not a pre-existing idiom — flag this explicitly to Phase 2 translators as a coined technical term requiring reinforcement (repetition, teaching notes) rather than being left to stand alone as though it were self-evidently established Portuguese usage. |
| ahavah (ordinary covenant-friendship love) | amor | No weakness in isolation, but risk of bleeding into “amor leal” if translators are not disciplined about scope. | Fence “amor” (unmodified) strictly to ahavah contexts (1:26, Jonathan-David); never allow “amor” alone to substitute for “amor leal” in a chesed context, or the doctrinal backbone term dissolves into generic vocabulary. |
1.5 The Messianic Hope Rooted in David’s Line
| Concept | Available Portuguese term(s) | Weakness | Recommended strategy |
|---|---|---|---|
| mashiach (technical, eschatological) vs. meshiach YHWH (functional, royal-office) | Messias (capitalized) vs. ungido (lowercase) | Portuguese, like English, has only one root word family (ungir/ungido/Messias) for both the mundane royal-anointing sense and the fulfilled eschatological title. Unlike Hebrew, where context alone carries the distinction for a native reader, Portuguese readers habituated to hearing “Messias” primarily in its capitalized Christian-confessional sense are at higher risk of importing that sense backward onto every 2 Samuel occurrence of anointing. | Mandatory case-based split rendering: capitalized “Messias” reserved exclusively for the fulfilled NT referent; lowercase “ungido” for every 2 Samuel occurrence (Saul, David). This is a typographic solution compensating for a genuine lexical gap — Portuguese has no separate root word the way, e.g., some languages distinguish a generic “anointed one” from a proper-noun “Messiah.” |
| zera (seed/descendant) | descendência (de Davi) | No lexical weakness; risk is purely doctrinal-sequencing (near/far referent), already addressed in the glossary (A6). | Reuse baseline exactly; teach near-referent (Solomon) before far-referent (Christ) explicitly at every occurrence. |
| ben (covenant son) | filho (lowercase) | Portuguese capitalization conventions (Filho/filho) are not obligatory the way they are in, e.g., formal theological English style guides — a careless typesetting or translation pass could silently capitalize “filho” for reverential emphasis, accidentally producing a doctrinally false statement (that 2 Sam 7:14’s son IS the baseline’s capitalized “Filho de Deus”). | Explicit typographic rule: NEVER capitalize “filho” in 2 Samuel 7:14 context. Add this to the forbidden-substitution list for this curriculum (see §4 below), parallel to the baseline’s resurrection/reencarnação rule. |
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
2.1 Missing Vocabulary (Portuguese lacks a ready lexical match)
| Hebrew concept | Gap description | Compensating strategy |
|---|---|---|
| chesed | No single Portuguese word carries covenant-loyalty + loving-kindness + faithfulness simultaneously. | Coined compound “amor leal” (see §1.4). This is the curriculum’s single most significant missing-vocabulary problem and should be treated as such in Phase 2 QA — expect this term to require more back-translation checks than any other term in this Language Package. |
| bayit’s triple wordplay | Portuguese “casa” covers the semantic range but transmits none of the surface-level punning signal a Hebrew reader receives automatically. | Compensate through translator notes rather than lexical substitution (see §1.1). |
| YHWH as a distinct personal name vs. Adonai as a title | Portuguese, like English, has historically resolved this by typographic convention (SENHOR small caps vs. Senhor normal case) rather than by two different words — Portuguese possesses no separate proper-noun equivalent to the Tetragrammaton the way, e.g., some translations transliterate “Iavé/Jeová.” | Adopt the Almeida-tradition typographic convention exactly as already fixed in the term registry (B1/B2). This is a genuine missing-vocabulary case resolved by convention, not translation. |
| nagid (designated-leader, distinct from melekh) | Portuguese has no single word distinguishing “designated by divine appointment, not yet reigning” from “reigning king.” | Use a two-word gloss “príncipe” / “soberano designado,” explicitly fenced away from “vocação” (see §2.2 below) and from “rei.” |
2.2 Crowded Semantic Neighborhoods (Portuguese has too many candidate words competing for one Hebrew concept, or one Portuguese word serving too many Hebrew concepts)
| Portuguese term/neighborhood | Competing senses it must be fenced from | Fencing rule |
|---|---|---|
| ”amor” family (amor, amor leal, misericórdia, benignidade, compaixão) | chesed (covenant loyalty) vs. ahavah (ordinary love/affection) vs. rachamim (compassion/mercy, not separately tabled in this curriculum but present in the wider OT) | “Amor leal” = chesed ONLY. “Amor” (unmodified) = ahavah ONLY. “Misericórdia” reserved for rachamim/compassion contexts elsewhere in the canon, NOT used for chesed in this curriculum. This three-way fence must be stated explicitly to Phase 2 translators, since ordinary Portuguese usage does not naturally maintain it. |
| ”ungido/Messias” family | meshiach YHWH (functional royal anointing, David/Saul) vs. mashiach (fulfilled eschatological title) vs. general verb “ungir” (ritual anointing to any office — king, priest, or prophet) | Case-based fence per §1.5. Additionally, “ungir” (verb) may describe priestly or prophetic anointing elsewhere in the OT canon without implying royal-messianic status; this curriculum’s occurrences (2:4; 5:3) are royal, but future curricula (e.g., Exodus/Leviticus priestly anointing) must not automatically inherit the messianic-trajectory teaching note attached here. |
| ”justiça” family | tsedaqah (OT royal/social justice-in-governance, 8:15; covenant-loyalty-rewarded, 22:21,25) vs. the baseline’s forensic soteriological “justiça” (Romans 3-5, Critical) vs. ordinary Portuguese “justiça” (secular legal fairness) | Every 2 Samuel occurrence requires an explicit teaching flag distinguishing OT royal/relational righteousness from NT forensic imputed righteousness. Do not let the shared Portuguese word imply shared doctrinal content — this is the single highest anachronism risk in the glossary’s Section A. |
| ”salvação” family | yeshuah (OT this-worldly deliverance from enemies, ch. 22) vs. the baseline’s full soteriological “salvação” (Critical) | Teach as a real but partial anticipation, not identity and not disconnection. Do not allow “salvação” in ch. 22 to be taught as already meaning “eternal reconciliation with God” without the OT-to-NT trajectory step made explicit. |
| ”pai” / “filho” (lowercase) family | Covenantal royal adoption (2 Sam 7:14, David’s dynastic heir) vs. baseline’s capitalized “Pai”/“Filho de Deus” (Trinitarian) vs. baseline’s general believer’s adoption “filhos de Deus” (Romans 8) | Three-way fence, all sharing overlapping Portuguese vocabulary. Strict lowercase/uppercase discipline plus explicit typological-escalation teaching notes at every occurrence (see §1.5 and the forbidden-substitution list, §4). |
| “reino” family | mamlakah (OT historical, political, Davidic/Israelite kingdom) vs. baseline’s “reino de Deus” (universal, spiritual, Medium risk) | See §1.1. Fence by explicit typological-continuity notes, not by lexical substitution. |
| ”para sempre” / “eterno” family | ad-olam (covenant permanence, unbroken succession guaranteed by God) vs. philosophical/metaphysical “eterno” (timelessness) vs. (critically) any Kardecist reading of unending existence across successive reincarnations | This is the OT curriculum’s direct structural parallel to the baseline’s forbidden reencarnação/ressurreição distinction. See §4 below — treat as a forbidden-substitution-list item, not merely a style preference. |
| ”arca” (ark) | arca da aliança do SENHOR (2 Sam 6-7) vs. “arca de Noé” (Noah’s ark) — a true Portuguese homonym collision, not a theological one | Always render the full phrase “arca da aliança do SENHOR,” never the bare “arca,” in first occurrences and in any teaching-note heading, to avoid the Noah’s-ark homonym confusion for lower-literacy audiences. |
3. Transliteration vs. Paraphrase Decisions
Following the baseline’s precedent (Abba retained untransliterated and paired with “Pai”; Amém and Aleluia retained as established transliterations), this curriculum requires several fresh transliteration-vs-paraphrase decisions with no baseline precedent to draw on directly.
| Term | Decision | Rationale |
|---|---|---|
| YHWH | Neither transliterate nor translate as a new word — use the established typographic convention “SENHOR” (small caps). | Portuguese Bible tradition (Almeida and virtually all subsequent Catholic and Protestant editions) does not transliterate the Tetragrammaton as “Iavé/Jeová” in the main text; it uses the small-caps convention. Deviating from this to introduce a transliterated form would break continuity with every existing Portuguese Bible a learner might independently consult — a stronger consistency argument than in languages without a settled convention. |
| Adonai | Translate as title “Senhor” (normal case), not transliterated. | Same rationale; paired case-distinction with SENHOR is the load-bearing convention, not the Hebrew sound-form. |
| mashiach / meshiach YHWH | Translate/adapt, not transliterate — but split by capitalization (Messias / ungido). | A transliteration (“Mashiach”) would be unintelligible to the target audience and would forfeit the valuable congregational familiarity of “Messias” for the fulfilled sense. Paraphrase-with-case-distinction is superior to transliteration here. |
| chesed | Paraphrase (compound term “amor leal”), not transliterated. | No transliteration tradition exists for this term in Portuguese Bible history (unlike Abba, which the NT itself preserves untranslated in Greek transcription and Romans 8:15 explicitly retains). Since Hebrew “chesed” appears only in scholarly/seminary registers in Portuguese, transliterating it into lesson material would be opaque to the general learner; paraphrase is required. |
| ad-olam, avon, bayit, nagid, chazon, etc. | Paraphrase/translate, not transliterate. | None of these terms have entered Portuguese liturgical or devotional vocabulary the way “Abba,” “Amém,” “Aleluia,” or “Messias” have (all NT-era terms already naturalized by the baseline). Introducing Hebrew transliterations for OT common nouns would create an unfamiliar technical vocabulary layer with no existing audience recognition to draw on, unlike the baseline’s NT transliterations. |
| Selah (poetic term appearing in some Psalms-adjacent material, relevant if 2 Sam 22 is cross-taught with Psalm 18) | Not applicable within 2 Samuel 22 itself (the term does not occur in the 2 Sam 22 text as transmitted), but flagged here for cross-reference consistency if future Psalms curricula transliterate it. | Recorded for forward compatibility; no action required in this curriculum. |
General rule established for this Language Package: transliteration is reserved for terms that either (a) the New Testament itself transliterates and the baseline already retains (Abba), or (b) have independently entered mainstream Portuguese Christian devotional vocabulary regardless of denomination (Amém, Aleluia, Messias-as-proper-noun). All other Hebrew OT technical vocabulary in 2 Samuel is paraphrased/translated, with case, compounding, or explanatory notes used to carry distinctions transliteration would otherwise be asked to bear.
4. Forbidden Substitution List (2 Samuel-specific additions to the baseline’s list)
Parallel in structure and authority to the baseline’s Critical Forbidden Substitutions (12_ai_translation_requirements.md), the following must never occur in Phase 2 output for this curriculum:
- NEVER capitalize “filho” or “pai” in 2 Samuel 7:14/7:24 contexts — this would falsely equate David’s dynastic heir with the baseline’s capitalized “Filho de Deus”/“Pai” (Trinitarian sense).
- NEVER render “para sempre” (ad-olam) in a way that suggests bounded duration (“por um longo tempo,” “por muitas gerações” as a substitute rather than a gloss) — must remain unqualified permanence, and must never be explained via a cyclical/reincarnation-adjacent framing.
- NEVER use “Messias” (capitalized) for Saul, David, or any reigning 2 Samuel king — always “ungido” (lowercase) for the functional/royal sense.
- NEVER render chesed as “sorte,” “bênção genérica,” or “carma positivo acumulado” — the term must always carry covenant-relational content, and Brazilian Portuguese folk-religious readings of fortune or accumulated merit must be explicitly excluded, consistent with the baseline’s already-documented pattern for grace/salvation.
- NEVER flatten “Espírito do SENHOR” into the baseline’s fully Trinitarian “Espírito Santo” without a canonical-trajectory teaching note, and never allow it to be read as an impersonal “espírito guia.”
- NEVER use “escravo” for “servo” (eved) as a royal-office title — this is a chattel-slavery term in Portuguese and would strip the honorific covenant sense from “my servant David.”
- NEVER soften “mau aos olhos do SENHOR” (11:27) to a merely social or aesthetic judgment (“não foi bem visto,” “não ficou bem”) — full moral-covenantal seriousness must be retained.
- NEVER present 12:13’s forgiveness (“tirou o pecado”) without 12:14’s continuing consequence in the same teaching unit — this is not a forbidden word, but a forbidden isolated-clause presentation that would misrepresent the doctrine of Consequences of Sin.
5. Ranked List of Highest-Risk Ambiguities for This Curriculum
Ranked by combined doctrinal centrality and likelihood of translator/AI error, given documented Brazilian religious-landscape collision risks (Kardecist Spiritism, popular Catholic piety, syncretistic Afro-Brazilian traditions) and genuine Portuguese lexical gaps.
| Rank | Ambiguity | Why highest-risk | Mitigation already specified |
|---|---|---|---|
| 1 | chesed → “amor leal” | Genuine missing-vocabulary problem (no existing Portuguese word), central to the named doctrine “God’s Steadfast Love despite Human Failure,” and the term recurs at the doctrine’s most load-bearing verse (7:15) directly beside the “rod of discipline” clause (7:14) — a translator error here severs the entire doctrinal argument that discipline does not equal covenant termination. | §1.4, §2.2; coined compound term fixed in glossary/registry; flagged for elevated Phase 2 back-translation scrutiny. |
| 2 | mashiach vs. meshiach YHWH (Messias vs. ungido) | Direct collision with the named doctrine “The Messianic Hope Rooted in David’s Line”; the two Portuguese renderings share a root and register, making silent conflation the single most likely default-AI-behavior error in this entire Language Package (an AI system will be statistically biased toward capitalizing a christologically-loaded term it recognizes). | §1.5, §2.2, §4(3). |
| 3 | filho/Filho and pai/Pai capitalization (2 Sam 7:14) | Same collision mechanism as #2, but even higher doctrinal stakes per occurrence — a single dropped or added capital letter converts a typologically-anticipatory statement into a false direct christological claim, or conversely erases the passage’s genuine link to Christ if the typology is never taught. | §1.5, §4(1). |
| 4 | ”para sempre”/ad-olam vs. Kardecist cyclical-existence readings | Structural parallel to the baseline’s single highest-stakes forbidden substitution (resurrection/reencarnação); the Davidic covenant’s permanence claim is exactly the kind of “eternal” language a Spiritist-influenced reader could reinterpret through a reincarnation-adjacent lens if not explicitly fenced. | §1.1, §4(2). |
| 5 | tsedaqah/justiça (OT royal-relational) vs. baseline’s forensic soteriological justiça | Same Portuguese word, two different doctrinal systems (OT royal governance vs. NT justification by faith); highest risk of silent anachronism because, unlike the chesed or Messias cases, no typographic or lexical marker distinguishes the two senses at all — only a teaching note can. | §1.1 (A4 cross-ref), §2.2. |
| 6 | yeshuah/salvação (OT this-worldly deliverance) vs. baseline’s full soteriological salvação | Same mechanism as #5, slightly lower rank because the OT-to-NT trajectory here is more intuitively taught (deliverance-from-enemies naturally anticipates deliverance-from-sin) than the royal-justice/forensic-justice gap. | §1.5 (A5 cross-ref), §2.2. |
| 7 | casa (bayit) wordplay collapse | Not a doctrinal-collision risk in the Brazilian-religious-landscape sense, but a structural risk: if translators vary the Portuguese word across the three senses for stylistic clarity, the entire literary argument of 2 Samuel 7 (palace → dynasty → temple) becomes invisible, undermining the Davidic Covenant doctrine’s textual support. | §1.1, §2.1. |
| 8 | Espírito do SENHOR (23:2) vs. Espírito Santo | Ranked lower than #1-4 because it occurs only once in this curriculum (23:2), but flagged as Critical because of direct parallel to the baseline’s already-documented Candomblé/Umbanda “espírito guia” collision risk. | §1.1 (A8 cross-ref), §4(5). |
| 9 | servo (eved) vs. escravo | Ranked lower because the correct choice (“servo”) is already unambiguous once flagged; risk is purely one of an inattentive default-register slip, not a genuine ambiguity in the Hebrew or the doctrine. | §4(6). |
| 10 | SENHOR vs. Senhor typographic distinction (B1/B2) across a 24-chapter book | Ranked lowest among Critical items because the rule itself is simple and well-precedented in Portuguese Bible tradition; risk is purely one of clerical/typesetting consistency across a long text with hundreds of occurrences, not conceptual ambiguity. | §1.1, §3. |
6. Chapter Coverage Confirmation
This gap analysis addresses vocabulary and doctrine drawn from across the full book (chapters 1–24), per the terms and cross-references already itemized in 08_core_glossary.md Sections A–D. Chapters contributing no new lexical or doctrinal gap beyond what is tabled above (e.g., portions of chs. 2–4, 10, 15, 17–19 narrative material not already cited) are confirmed reviewed: their vocabulary (military, genealogical, geographic proper nouns) carries Low risk and requires no gap-analysis entry beyond standard proper-noun transliteration per the baseline’s established-form convention (§ Transliteration and Proper Name Standards, 12_ai_translation_requirements.md).
This analysis extends, and does not contradict, the baseline Romans Language Package. It supplies the linguistic-gap foundation for 07_semantic_analysis.md and 08_core_glossary.md, and must be consulted alongside bible_term_registry.json before any Phase 2 segment translation for this curriculum begins.