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: 1 Chronicles

English → Portuguese Language Package Extension | Destination: Portuguese

Curriculum: 1 Chronicles 1–29 (full book) Core passage: 1 Chronicles 17:1–15 Baseline authority: Romans Language Package (translation_memory.json, bible_term_registry.json, 12_ai_translation_requirements.md) — reused exactly wherever it already covers a term; never contradicted Generated: Phase 1, Step 8


0. Purpose and Method

This analysis identifies where standard, pan-Lusophone Portuguese (Almeida-tradition register) lacks precise equivalents for 1 Chronicles’ theological vocabulary, where existing Portuguese terms are crowded by rival meanings from Brazil’s dominant religious landscape (popular Catholic piety, Kardecist Spiritism, Afro-Brazilian Candomblé/Umbanda), and where transliteration rather than translation is the safer strategy. It is built directly on the term inventory already established in 08_core_glossary.md and bible_term_registry.json (prior outputs) and organizes that inventory by the five curriculum doctrines, then surfaces cross-cutting gap patterns those term-by-term entries do not make visible on their own.

Coverage spans the entire book, chapter 1 to chapter 29. Chapters or ranges that contribute no vocabulary beyond what is already fixed in the term registry are noted explicitly in Section 5 as reviewed, not omitted.


1. Doctrine Vocabulary Matrix

1.1 Genealogy and the Continuity of God’s People (chs. 1–9, 29)

ElementAvailable Portuguese TermsWeaknessesRecommended Strategy
toledot (genealogy as theology)genealogia, geraçõesPortuguese has no single word that carries the Hebrew toledot’s dual sense of “historical record” AND “generative theological claim.” “Genealogia” reads to a modern reader as antiquarian list-making.Render “genealogia”/“gerações” per context, but require a standing translator’s-preface note (not per-verse) framing chs. 1–9 as a theological argument for unbroken covenant continuity, not filler.
bekhor / bekhorah (firstborn, birthright)primogênito, direito de primogenituraStandard equivalents exist, but Portuguese “primogênito” carries no automatic connotation of “forfeitable status,” so 5:1–2’s reversal (Reuben → Joseph, kingship → Judah) can read as a genealogical curiosity rather than a doctrine of sovereign election.Pair every occurrence in the Reuben/Judah material with the same doctrinal handling as the baseline’s election entry; route to theologian review.
gerim ve-toshavim (sojourners/strangers, 29:15)peregrinos, forasteiros, estrangeirosNo single-word gap, but this exact phrase sits in a crowded semantic neighborhood — see Section 2.3 below (reincarnation collision).Fixed rendering “peregrinos e forasteiros”; mandatory contrastive note against reincarnation.
galah/golah (exile)exílio, cativeiroNo lexical gap. Risk is theological flattening: readers may treat 9:1’s “after the exile” as a mere historical timestamp rather than the hinge proving covenant survival through judgment.Retain “exílio”/“cativeiro”; supply a contextual framing note at 9:1, not a lexical change.

1.2 The Davidic Covenant Reaffirmed (ch. 17 core; also chs. 11, 22, 28, 29)

ElementAvailable Portuguese TermsWeaknessesRecommended Strategy
bayit (house)casaPortuguese “casa” happily preserves the Hebrew’s triple range (dwelling/dynasty/temple) — an asset, not a gap — but this very breadth is itself a risk: a reader cannot tell from the word alone which sense is active in any given clause of 17:1–15.No lexical substitution. Require a translator note at each shift of referent within 17:1–15 (v.1 David’s palace; v.4 the temple God does NOT want David to build; v.10 dynastic house God WILL build for David; v.12 temple again). See Section 4, ranked risk #1.
beiti u-malkhuti (“my house and my kingdom,” v.14)minha casa / meu reinoNo lexical gap; the risk is purely referential — the first-person pronoun belongs to God, not David, and Portuguese pronoun morphology does not disambiguate this any more clearly than English does.Fixed rendering per registry; mandatory translator note flagging the divine (not Davidic) possessive.
chesed (steadfast love/covenant loyalty)benignidade, fidelidade leal, misericórdia, amorThis is a genuine vocabulary gap: no single Portuguese word carries chesed’s fusion of (a) binding covenant obligation, (b) unmerited initiative, and (c) enduring loyalty. “Misericórdia” loses the covenant-binding sense; “amor” loses the binding/relational sense entirely and risks a romantic or sentimental register.Use the two-term compound already fixed in the registry (“benignidade / fidelidade leal”) consistently; never substitute “misericórdia” or “amor” alone in ch. 17 or its cross-references (2 Samuel 7 parallel).
av/ben (covenantal father/son, v.13)Pai / filhoNo lexical gap, but a severe doctrinal-collision risk: this is the same lexical pair the baseline uses for Christ’s eternal Sonship (Filho de Deus).Never render v.13 with a phrase that could be confused with Filho de Deus. Use lower-case “filho,” never “Filho,” and pair with a mandatory translator note (already specified in the prior glossary/registry) distinguishing Solomon’s historical adoptive sonship from Christ’s eternal ontological Sonship. Ranked risk #3 below.
nagid (prince) vs melekh (king)príncipe vs reiPortuguese “príncipe” carries a strong modern connotation of hereditary junior royalty (heir apparent), which is the opposite of nagid’s sense (a divinely designated ruler, often not yet reigning or not from an established dynasty).Retain “príncipe” per registry (no better single-word option exists) but supply a short glossed note the first time it appears in ch. 17, distinguishing it from a modern “prince” title.
YHWH Tseva’ot (LORD of Hosts)SENHOR dos ExércitosNo gap; risk is omission/flattening under translation fatigue in Phase 2 batch processing.Enforce full phrase “SENHOR dos Exércitos” every occurrence; forbid silent contraction to plain “Senhor.”
zera’ (seed/offspring, v.11)descendênciaNo lexical gap; risk is under-translation to a merely biological/dynastic sense that forecloses the double horizon (Solomon/Christ).Render “descendência” per registry; require a standing note on the double fulfillment (immediate: Solomon; ultimate: Christ, Galatians 3:16) wherever ch. 17 is taught.
tavnit (revealed temple pattern, ch. 28)modelo, plantaNo lexical gap; the risk is conceptual collision with ongoing “channeled” revelation claims. See Section 2.2.Render “modelo”/“planta”; mandatory contrastive note against Kardecist psicografia, matching the baseline’s inspiration_of_scripture handling.

1.3 Worship and the Levitical Order (chs. 6, 9, 13, 15–16, 23–27)

ElementAvailable Portuguese TermsWeaknessesRecommended Strategy
kohen (priest)sacerdoteNo lexical gap, but a live crowded-neighborhood risk: “padre” is the reflexive first-choice word for “priest” in everyday Brazilian and Portuguese usage and denotes specifically a Roman Catholic parish priest.”Padre” is FORBIDDEN for this term (already fixed in registry). Enforce “sacerdote” without exception, including in genealogical lists (chs. 6, 9, 24).
mishpat (ordinance/prescribed procedure, 15:13)ordenança, prescriçãoNo true gap, but Portuguese “ordenança” can register as bureaucratic/military rather than liturgical.Prefer “prescrição” or “ordem prescrita” in liturgical contexts (15:13); reserve “ordenança” for more general legal/administrative uses elsewhere in the book.
machlekot (rotational divisions of service)divisões, turmas de serviço”Turmas” carries a mildly informal, school/workplace-shift connotation in Brazilian Portuguese that can trivialize the weight of chs. 23–27’s organizational theology.Prefer “divisões de serviço” as the primary rendering; reserve “turmas” only for supplementary clarifying glosses, never as the primary term in doctrinal exposition.
‘ov / ba’alat-ov (medium/necromancer, 10:13)médium, necromanteSEVERE crowded-neighborhood collision — see Section 2.1, ranked risk #2.Fixed rendering with mandatory contrastive theologian-reviewed note at every occurrence.
darash (inquire of the LORD)buscar, consultarNo lexical gap; risk is under-translation to a generic “ask,” losing the antithetical force against the preceding medium/necromancer term.Render “buscar/consultar o SENHOR,” always retaining the direct antithesis to 10:13’s condemned consultation.

1.4 Preparation for the Temple (chs. 18, 21, 22, 28–29)

ElementAvailable Portuguese TermsWeaknessesRecommended Strategy
satan (ch. 21)SatanásNo lexical gap; risk is depersonalization under cultural pressure toward “energia”/“força negativa” framings common in Brazilian folk-spiritual and New Age discourse.Fixed as “Satanás,” person-referring grammar retained (never “uma força” or “uma energia”). See Section 2.1, ranked risk #4.
menuchah (rest, applied to Solomon, 22:9)descansoNo lexical gap; minor risk of conflation with the baseline’s doctrinal peace (paz com Deus, justification).Render “descanso”; add a note distinguishing this historical/political peace-for-temple-building sense from the baseline’s soteriological “paz com Deus.”
nedavah (freewill offering)oferta voluntáriaNo gap. Minor risk: Brazilian evangelical usage sometimes collapses “oferta voluntária” into modern tithe/offering campaign rhetoric.Render “oferta voluntária”; keep exposition anchored to 29:5–9’s uncoerced, grateful character rather than fundraising technique.
lev shalem / nefesh chafetsah (whole heart / willing mind, 28:9)coração íntegro, ânimo voluntárioNo gap.Retain paired rendering; no further action needed beyond what is already fixed.

1.5 God’s Faithfulness across Generations (whole book; esp. chs. 6, 10, 16, 17, 29)

ElementAvailable Portuguese TermsWeaknessesRecommended Strategy
ma’al (unfaithfulness/covenant treason, 10:13)infidelidade, transgressãoNo lexical gap; risk is under-weighting — Portuguese “infidelidade” in everyday use skews toward marital unfaithfulness.Pair with “transgressão” or a modifier (“infidelidade para com o SENHOR”/“infidelidade ao pacto”) to keep the covenantal register clear.
devar-Elohim / chazon (word of God / prophetic vision, 17:3, 15)palavra de Deus, visãoNo lexical gap; risk is the crowded-neighborhood collision with psicografia — see Section 2.2.Fixed rendering with standing contrastive note.
va-ye’ater (God relented/was entreated, 21:26–27)Deus atendeu à súplica, Deus se compadeceuNo true gap, but naive rendering risks implying God can be manipulated by ritual technique.Frame as covenantal responsiveness to genuine repentance, consistent with (not contradicting) divine sovereignty; theologian-reviewed note recommended at 21:26–27.
save’a yamim (full of days, 29:28)cheio de dias, farto de diasNo gap.Retain “cheio de dias” as the closing formula; no further action.

2. Crowded Semantic Neighborhoods Requiring Fencing

Unlike a simple vocabulary gap (no word exists), a crowded neighborhood exists where a perfectly good Portuguese word exists but is already occupied, in Brazilian religious discourse, by a rival system’s doctrine. Fencing means: keep the word, but mandate an explicit boundary note at every occurrence.

2.1 Spiritist and folk-spiritual collisions (highest pastoral stakes)

  • médium / necromante (10:13): “Médium” is not a marginal or archaic word in Brazilian Portuguese — it is the everyday, respected term for a practicing Kardecist Spiritist, a movement with tens of millions of adherents and cultural sympathizers in Brazil. 1 Chronicles 10:13 uses this exact vocabulary to describe the sin that cost Saul the kingdom. This is the single most acute fencing requirement in the entire book. Strategy: retain “médium/necromante”; require an explicit, theologian-reviewed note at every occurrence stating that the text presents consulting the dead as covenant treason — not as a softened or merely “Old Testament-specific” prohibition disconnected from the present-day practice bearing the same Portuguese name.
  • Satanás (21:1): Brazilian folk-spiritual and New Age registers often prefer impersonal language (“energia negativa,” “força do mal”) over a personal adversary. Chronicles’ portrait is unambiguously personal. Strategy: fence with grammatically personal agreement (never “algo,” “uma força”) and a note on secondary spiritual causation under God’s sovereignty.
  • espíritos guias / mediunidade (general worship-gift risk): Although 1 Chronicles has no direct equivalent to Romans’ “dons espirituais,” the book’s rich vocabulary of Spirit-empowered service (Levitical divisions, prophetic vision, “musicians… prophesying with lyres,” 25:1) invites the same fencing the baseline already applies to spiritual_gifts and holy_spirit. Strategy: apply the baseline’s existing forbidden-substitution rules without modification; no new term needed.

2.2 Revelation-claim collisions

  • palavra de Deus, visão, modelo/planta (tavnit): Kardecism’s foundational claim to ongoing revelation through psicografia (mediums transcribing messages from the dead) is a live, mainstream rival claim in Brazil, not a fringe belief. 1 Chronicles supplies three separate moments of bounded, once-given, named-recipient revelation (Nathan’s oracle, ch. 17; the temple pattern given to David “by the Spirit,” ch. 28) that are especially exposed to being read as one instance among many ongoing channels. Strategy: fence all three with the same contrastive note already required by the baseline’s inspiration_of_scripture doctrine; do not treat this as three separate problems needing three separate solutions.

2.3 Reincarnation-adjacent collisions

  • peregrinos e forasteiros (29:15), “like a shadow”: David’s confession of human transience could, without fencing, be assimilated to the Kardecist doctrine of the soul’s journey across a long sequence of successive earthly lives — a doctrine for which “peregrino” (pilgrim/wanderer) is culturally resonant vocabulary in Spiritist devotional writing. Strategy: fence with an explicit note that the text describes one life’s brevity before an eternal God, not a spirit’s passage through many lives.
  • ressurreição / reencarnação: 1 Chronicles itself contains no resurrection narrative, but ch. 17’s messianic throne “forever” (v. 12, 14) is the OT seedbed for NT resurrection-and-eternal-reign theology (cf. Luke 1:32–33). Strategy: no lexical decision needed within this book, but flag the ch. 17 throne material for continuity with the baseline’s resurrection forbidden-substitution rule when this curriculum is taught alongside NT material.

2.4 Catholic-piety-adjacent collisions

  • casa (bayit) as dynasty vs. institutional “Casa de Deus”: Popular Catholic usage of “Casa de Deus” typically denotes a physical church building. Ch. 17’s wordplay depends on “casa” shifting between palace, temple, AND dynasty within the space of fifteen verses. Strategy: no lexical substitution (see Section 1.2); fence by requiring a translator’s referent-tracking note.
  • sacerdote vs. padre: already fenced in the prior glossary/registry; reaffirmed here as a standing rule for every priestly reference across chs. 6, 9, 15–16, 23–27.
  • santos (typological cross-reference use only): 1 Chronicles does not use this term in its own text as a doctrinal category, but any Phase 2 homiletic material connecting the book’s Levites/genealogies to NT “sainthood” language must apply the baseline’s existing Critical-risk fencing without modification.

3. Missing Vocabulary (True Gaps, No Adequate Single Term)

Hebrew conceptWhy Portuguese lacks a clean equivalentResolution
chesedNo single word fuses “unmerited,” “covenant-binding,” and “enduring loyalty” the way chesed does; every candidate Portuguese word loses one of the three components.Retain the fixed two-term compound “benignidade / fidelidade leal”; never reduce to one word in doctrinal exposition.
toledot as theological device”Genealogia” names the literary form but not its theological freight (covenant continuity through crisis).Supply structural framing in front matter/teaching notes rather than forcing a new coined term into the running text.
nagid”Príncipe” is the nearest available word but imports unwanted modern-hereditary connotations nagid does not carry.Retain “príncipe” with a first-occurrence glossing note; no better option exists in standard Portuguese.
bekhorah as forfeitable covenant status”Direito de primogenitura” names the legal/social institution but not its theological instability (forfeitable by divine sovereign choice, not merely by human misconduct as in Reuben’s case per Genesis 49:4, nor solely by merit as Kardecist frameworks would assume).Retain the phrase; carry the doctrinal weight in the theologian-reviewed note, not in the lexical choice.
tavnit as bounded, historically located revelationPortuguese “modelo”/“planta” are architecturally accurate but theologically silent on the once-for-all, non-repeatable nature of the revelation event.Carry the doctrinal weight in the mandatory contrastive note (Section 2.2), not in the word choice.

No entirely un-renderable term (i.e., requiring wholesale transliteration of a common noun rather than a proper name) was identified in this book. This is a lighter transliteration burden than some other curricula in this pipeline, because 1 Chronicles’ distinctive vocabulary (house, covenant, anoint, holy, priest) is already substantially covered by existing Portuguese Bible-translation tradition and by the baseline Romans Language Package.


4. Transliteration vs. Paraphrase Decisions

ItemDecisionRationale
Proper names throughout genealogies (chs. 1–9)Transliterate using established Almeida-tradition forms (e.g., Adão, Sete, Enos, Matusalém, Abraão, Isaque, Jacó/Israel, Judá, Davi, Salomão)Consistency with the baseline’s proper-name policy and with existing Portuguese Bible tradition; avoid inventing new transliteration conventions for names already fixed by centuries of Portuguese Bible translation.
Ornan (21:15ff.) vs. Araunah (2 Samuel 24, parallel account)Retain “Ornã” for 1 Chronicles occurrences per its own Hebrew spelling (אָרְנָן/עׇרְנָן); do not silently harmonize to “Araúna”Preserve the Chronicles text’s own form; add a cross-reference note (not a text change) linking to the 2 Samuel parallel for readers who notice the name difference.
YHWH Tseva’otParaphrase, not transliteration: “SENHOR dos Exércitos”Already established Almeida-tradition rendering; transliterating “Tseva’ot” would be unintelligible and inconsistent with the whole-Bible convention this Language Package must not contradict.
Abba (cf. baseline Romans 8:15)Not applicable within 1 Chronicles itself; no occurrence in this bookNoted for completeness; no decision required here.
éfode (linen ephod, 15:27)Transliterate as “éfode”Standard, already-lexicalized Portuguese Bible loanword; no vernacular equivalent exists or is needed.
Selá / musical/liturgical terms (e.g., “com harpas,” “címbalos,” instrument names in chs. 15–16, 25)Translate descriptively (harpas, saltérios, címbalos, trombetas) rather than transliterateThese have stable, non-controversial Portuguese equivalents already used across Bible translation tradition; transliteration would be unnecessary and would reduce comprehension.
médium / necromante (10:13)Translate, not transliterate — but fence heavily (see Section 2.1)The Hebrew (‘ov) has a clear, well-established Portuguese doctrinal equivalent; the risk is not lexical unavailability but semantic occupation by a rival living religious system. Transliterating the Hebrew would evade rather than confront the collision this curriculum must address directly.
tavnit (temple pattern)Translate as “modelo/planta,” not transliterateA functional architectural/theological equivalent exists; transliteration would obscure rather than clarify the doctrine.

General rule for this curriculum: transliteration is reserved for proper names and a small closed set of already-lexicalized technical/liturgical loanwords (éfode, Amém, Aleluia — the latter two per baseline). All theological common-noun vocabulary is translated using existing Portuguese Bible tradition, with doctrinal precision carried by mandatory contrastive translator notes rather than by coining new words or importing untranslated Hebrew terms into the running text.


5. Ranked List of This Book’s Highest-Risk Ambiguities

  1. bayit / “casa” triple wordplay (17:1, 4, 10, 12) — Critical. The single word carrying palace/temple/dynasty across fifteen verses is the textual anchor of the Davidic Covenant Reaffirmed doctrine; losing referent-tracking here damages the core passage itself, not a peripheral one.
  2. médium/necromante (10:13) — Critical. Direct, live collision with a mainstream contemporary Brazilian religious practice bearing the identical Portuguese name; the doctrinal stakes (covenant treason costing Saul the kingdom) are maximal.
  3. Covenantal father/son — Pai/filho vs. Filho de Deus (17:13) — Critical. Touches the same Christological ground as the baseline’s highest-risk Sonship doctrine; conflating the two either denies Christ’s unique eternal Sonship or denies this verse’s own historical Solomonic referent.
  4. Satanás as personal agent vs. impersonal force (21:1) — Critical. Brazilian folk-spiritual/New Age discourse offers a ready depersonalizing misreading; the doctrine of a personal adversary alongside genuine human responsibility is easily lost.
  5. chesed / “benignidade” vs. merit-based favor (17:13) — High. The gap between covenant-loyalty love and any merit-accumulation framework (Tridentine or Kardecist) must be actively maintained; no single Portuguese word does this work automatically.
  6. tavnit / revealed temple pattern vs. ongoing mediumistic revelation claims (ch. 28) — High. A bounded, once-given revelation event is structurally vulnerable to being read as one instance of an open, repeatable channel.
  7. firstborn/birthright reversal (5:1–2) vs. moralized “merit of effort” — High. Risk of readers supplying either a Kardecist merit-across-lifetimes frame or a simple morality-tale frame (“Reuben lost it by bad behavior”) in place of the text’s own sovereign-election claim.
  8. zera’/“descendência” (17:11) collapsed to biological/dynastic sense only — High. Losing the double horizon (Solomon now, Christ ultimately) flattens the core passage’s forward-reaching theological force.
  9. gerim ve-toshavim / “peregrinos e forasteiros” (29:15) vs. reincarnation framing — High. A memento mori about one life’s brevity is textually adjacent to language Spiritist devotional writing has also claimed.
  10. YHWH Tseva’ot flattened to plain “Senhor” (17:7) — Medium-High. A likely translation-fatigue error in batch processing (Phase 2) rather than a conceptual gap, but it erases the deliberate emphasis on divine sovereign power undergirding the covenant oracle that follows immediately.

6. Full-Book Chapter Coverage Log

Every chapter of 1 Chronicles has been reviewed for this gap analysis. Chapters not separately tabled above contribute no vocabulary beyond what is already captured in Sections 1–5 or in the prior Core Glossary/Term Registry, and are logged here explicitly rather than silently omitted:

  • Chs. 1–9 (genealogies): Covered under Section 1.1 (toledot, firstborn/birthright, tribe, inheritance, exile, Levite, priest, cities of refuge, singers, gatekeepers, service). No further gaps beyond those tabled.
  • Ch. 10 (death of Saul): Covered under Sections 1.5 and 2.1 (medium/necromancer, inquire, unfaithfulness). Highest-priority chapter in this analysis outside the core passage.
  • Chs. 11–12 (David’s mighty men, covenant with Israel’s elders): Uses baseline “aliança” (11:3) and “homens valentes”/“príncipe” vocabulary already tabled; “coração unido” (12:38, one heart united) noted in the registry — no new gap.
  • Ch. 13 (death of Uzza): Establishes the negative case study for “holy”/“santo” resolved positively in ch. 15; no new vocabulary beyond the existing holy entry.
  • Ch. 14 (David’s house, family, and victories): No new theological vocabulary; standard narrative and proper-name content covered by transliteration policy (Section 4).
  • Chs. 15–16 (ark procession, Levitical order, David’s psalm): Covered under Section 1.3 (poles, ordinance, praise, continually, divisions) and Section 1.5 (thanksgiving, blessed the LORD).
  • Ch. 17 (core passage): Covered exhaustively in Section 1.2 and ranked risks 1, 3, 5, 8 above.
  • Chs. 18–20 (wars and dedication of spoils): “Dedicate/consecrate” (18:11) covered under Section 1.4; remaining content is narrative/military with no new doctrinal vocabulary.
  • Ch. 21 (census, plague, threshing floor): Covered under Sections 1.4 and 2.1 (Satan, census/count, plague, God relented, threshing floor).
  • Ch. 22 (David’s charge, temple preparation begins): Covered under Section 1.4 (prepare, rest, for the name, be strong and courageous).
  • Chs. 23–27 (Levitical, priestly, and military divisions): Covered under Section 1.3 (divisions, treasuries); no new gaps beyond machlekot fencing already noted.
  • Ch. 28 (David’s charge to Solomon, temple pattern): Covered under Sections 1.2 and 2.2 (tavnit, whole heart, willing mind).
  • Ch. 29 (offerings, David’s prayer and death): Covered under Sections 1.4, 1.5, and 2.3 (freewill offering, sojourners and strangers, full of days, blessed the LORD).

No chapter was found to require vocabulary decisions beyond those already documented in this analysis and in the prior Core Glossary (08_core_glossary.md) and Term Registry (bible_term_registry.json) outputs.


This analysis extends, and does not contradict, the baseline Romans Language Package. All fixed renderings cited above are drawn from translation_memory.json, bible_term_registry.json (Romans baseline and 1 Chronicles extension), and 08_core_glossary.md. Recommended notes and fencing requirements in this document should be carried forward into the doctrine risk registry extension and the Phase 2 AI translation requirements update for this curriculum.

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