Linguistic Gap Analysis: Malachi

Scope and Method

This analysis covers the entire book of Malachi (chapters 1–4, English versification) with Malachi 3:1–4 as the theological anchor. Because source and destination language are both English, “linguistic gap” here does not mean a missing target-language word for a source-language concept (the ordinary cross-language translation problem) — it means the same phenomenon documented throughout the baseline Romans package: drift within English itself, arising from (a) false-friend collisions with dominant secular/legal/pop-culture senses, (b) genuine denominational or scholarly-textual contest, (c) obsolescence, and (d) post-Christian cultural erosion or collision with a rival cultural narrative (the baseline’s fourth category). All findings below build on, and do not contradict, 08_core_glossary.md and the Malachi entries already logged in bible_term_registry.json. Baseline-locked renderings (covenant, Lord, righteousness, law, father, election, God, sin, and baseline-adjacent use of resurrection, providence) are treated as fixed inputs to this analysis, not open questions.

Chapters reviewed for completeness, with explicit note where a chapter contributes no new terms beyond what is already logged:

• Malachi 1 (1:1–14): source of message/oracle, love, election (Jacob/Esau), offering, defiled/polluted, Father, master, great King — fully covered below.
• Malachi 2 (2:1–17): source of covenant, priests, instruction/law, treachery/faithlessness, wife of your covenant, divorce, curse (2:2) — fully covered below.
• Malachi 3 (3:1–18): core passage (3:1–4) plus the chapter’s continuation — source of Lord/LORD, messenger, messenger of the covenant, LORD of Heaven’s Armies, refiner’s fire/launderer’s soap, sons of Levi, righteousness, foreigner/sojourner, rob, tithe, storehouse, windows of heaven, book of remembrance, fear the LORD, I the LORD do not change — fully covered below.
• Malachi 4 (4:1–6): source of Day of the LORD, Sun of Righteousness, furnace, Elijah, turn/return, curse (4:6), statutes and ordinances — fully covered below.
• No chapter in Malachi is without load-bearing vocabulary; all four are represented in the matrix and rankings below. This confirms full-book coverage per the PRD mandate — no chapter is silently omitted, even though Malachi 3:1–4 remains the theological and curricular anchor.

---

1. Doctrine Vocabulary Matrix

Doctrine	Available English Terms	Weaknesses in Current Usage	Recommended Strategy
God’s Unchanging Love for His People	love; Father; “I the LORD do not change”; election (Jacob/Esau)	“Love” is saturated with romantic and consumer senses (“falling in love,” “I love this song”), inviting a sentimental/conditional misreading of covenant-electing love; “unchanging” reads as stagnation to growth-mindset audiences; “Father” carries pastoral-sensitivity risk for readers with painful father figures; “election” is almost totally captured by the political-voting sense.	Present the four terms as one connected argument, not isolated vocabulary items: God’s love in 1:2 is defined by prior, unconditional choice (election), which is why it does not change (3:6), and this is the ground for filial address (Father) in 1:6. Apply the baseline’s Critical clarification for “election” verbatim (do not draft a fresh gloss). Reframe “unchanging” explicitly as reliability and promise-keeping, not resistance to growth, to work against growth-mindset cultural defaults.
Corrupt Worship and a Broken Covenant	offering; defiled/polluted; priests; covenant; instruction/law; master; great King	”Offering” narrows to the collection plate; “priests” is coded to Catholic/Anglican clergy and additionally freighted with clergy-abuse-scandal stigma; “master” collides with American chattel-slavery connotation; “covenant” is chiefly a real-estate/contract-law term for most readers; “great King” risks fantasy-genre dilution.	Use “worship” as the umbrella concept, with “offering” explicitly named as only one component under indictment (Malachi also indicts priestly teaching and personal honor, not giving alone). Explicitly date and distinguish the Levitical priestly office from later Christian clergy offices before using “priests.” Pair “master” with “father” as two sides of one relationship (intimate + authoritative) rather than leaning on “master” alone, to soften the slavery-association collision without erasing the term. Reuse baseline “covenant” rendering exactly; do not substitute “contract” or “agreement.”
Faithfulness in Tithing and Marriage	tithe; storehouse; windows of heaven; rob; wife of your covenant; divorce; treachery/faithlessness	”Tithe” carries prosperity-gospel/televangelist-fundraising baggage for both secular and churched readers; “rob” narrows to a financial-crime frame, losing the relational-betrayal sense; “divorce” (2:16) has genuine textual/translation variance across published English Bibles; “wife of your covenant” collides with contemporary contract-style, no-fault-divorce marriage discourse.	Explicitly distinguish Malachi’s tithe (a covenant obligation tied to communal provision for Levites, the Temple, and the poor) from prosperity-gospel fundraising rhetoric before teaching 3:8–10. Present the 2:16 divorce-verse textual range transparently (ESV-style “the man who divorces” vs. KJV-style “the LORD… hateth putting away”) rather than silently adopting one reading. Use “covenant” consistently across both the priestly-covenant (2:4–8) and marriage-covenant (2:14) material so learners see one unified argument, not two unrelated topics.
The Coming Messenger and the Day of the Lord	messenger; messenger of the covenant; Lord/LORD; LORD of Heaven’s Armies; refiner’s fire / launderer’s soap; sons of Levi; Sun of Righteousness; furnace; Elijah; Day of the LORD	Highest-concentration risk zone in the whole book. “Messenger” is trivialized by messaging-app branding and risks category confusion with “angel”; the Lord/LORD typographic distinction (adon vs. YHWH) is invisible in speech and easily missed even in print; “Day of the LORD” collides with disaster-movie apocalypticism and “Judgment Day” pop-culture framing; “Sun of Righteousness” risks an astrology-adjacent misreading if the English hymnic Sun/Son pun is mistaken for a claim about the Hebrew text.	This doctrine requires the heaviest editorial scaffolding in the curriculum. Mandatory: (1) explicitly name and distinguish the two “messenger” figures of 3:1 rather than silently merging them; (2) explicitly state, on first use, that “the Lord” (adon) and “the LORD” (YHWH) are two different Hebrew words rendered by near-identical English words, and that this distinction is invisible in audio/spoken delivery and must be stated aloud, not merely typeset; (3) state the Day of the LORD as a real, personal, morally decisive divine act, explicitly distinguished from disaster-film and “Judgment Day” franchise tropes; (4) flag the Sun/Son pun as an English-language hymnic tradition (Wesley), not a Hebrew wordplay.
The Call to Repentance before the Great Day	turn/return; fear the LORD; foreigner/sojourner; curse; book of remembrance	”Turn/return” competes with therapeutic self-improvement vocabulary (“growth,” “healing”); “fear” defaults to anxiety/terror in contemporary usage; “foreigner/sojourner” collides with today’s polarized immigration-policy discourse; “curse” is diluted by fantasy-fiction/superstition registers and collapses two distinct Hebrew words (cherem, me’erah) into one English term.	Restore “turn/return” as a decisive moral reorientation toward God, explicitly distinguished from generic self-improvement language, without denying that repentance also brings relief and renewal. Distinguish “fear the LORD” from terror/intimidation and restore it to reverent, relational awe (parallel to the baseline’s treatment of “holy”). State the biblical ger category (a protected resident-foreigner owed covenant justice) without importing or resolving a contemporary immigration-policy position. Accept the English collapse of cherem/me’erah into “curse,” but flag the collapse explicitly and gloss contextually which sense (formal covenant sanction vs. spoken malediction) is active at each occurrence.

---

2. Missing Vocabulary vs. Crowded Semantic Neighborhoods

2a. Missing Vocabulary (concepts English has no single adequate word for)

Concept	Hebrew	Gap	Recommended Handling
Dual “sent one” (human prophetic messenger and the category that also covers angelic beings)	מַלְאָךְ (mal’ak)	English actually splits one Hebrew word into two separate words (“messenger” / “angel”), forcing the translator/curriculum author to choose one and thereby lose the deliberate ambiguity the Hebrew author may be exploiting in Malachi 3:1. This is a “reverse gap” — not a missing word, but a missing shared word.	Do not silently pick “messenger” and move on. State explicitly that this is the same word elsewhere rendered “angel,” and that Malachi 3:1’s own New Testament fulfillment (Matthew 11:10) identifies this particular messenger as a human prophetic forerunner (John the Baptist), not a supernatural being, closing the ambiguity deliberately rather than leaving it open by accident.
Two distinct titles for God collapsed into one visual/aural English word pair	אָדוֹן (adon) vs. יְהוָה (YHWH), both conventionally rendered “Lord”/“LORD”	English typographic convention (capital “Lord” vs. small-caps “LORD”) is the only marker distinguishing these two titles, and that marker is entirely invisible in spoken delivery, audio Bibles, or any oral teaching setting — arguably a more severe gap than most false-friend risks in this registry, since it fails even readers who are paying close attention.	Do not rely on typography alone. Any spoken or audio-facing content must verbally flag the distinction (“the Hebrew here uses two different words, both usually printed in English as some form of ‘Lord’…”). This is a structural requirement, not optional stylistic flourish.
Covenant-loyalty love (the “chesed” concept, adjacent to but not the specific word used in Malachi 1:2)	(contextually implied by the doctrine, though Malachi 1:2 itself uses אָהַב/ahav, not חֶסֶד/chesed)	English has no single word combining “steadfast,” “loyal,” and “affectionate” in one term the way chesed does across the Old Testament; “love” alone under-specifies, “loyalty” over-legalizes, “faithfulness” under-emotionalizes.	Where the curriculum draws on the broader “unchanging love” doctrine (which resonates with chesed elsewhere in the Old Testament even though Malachi’s own word is ahav), use the compound phrase “unfailing covenant love” rather than any single word, and note this is a deliberate compound built to cover a gap, not a formal technical term.
Two distinct Hebrew “curse” words collapsed into one English word	חֵרֶם (cherem — formal covenant destruction-sanction/ban) vs. מְאֵרָה (me’erah — a pronounced malediction)	English “curse” covers both a solemn covenant legal sanction and an ordinary spoken malediction; there is no natural single-word English distinction, and inventing two artificial English terms would depart from established Bible-translation tradition.	Accept the collapse (do not coin new vocabulary), but gloss contextually at each occurrence: 2:2 and 4:6 lean toward the formal covenant-sanction sense; 3:9 leans toward the “you are under a curse” pronounced-consequence sense. Flag the collapse once, early, rather than repeating the caveat at every occurrence.
A single word for “robbing God” that carries both financial-technical and relational-betrayal weight simultaneously	קָבַע (qava)	“Rob” alone reads as a financial-crime term to contemporary ears; there is no English word that inherently carries both “you have broken the law” and “you have wounded a relationship” at once the way Malachi 3:8-9’s rhetorical question does.	Retain “rob” (it is vivid and rightly provocative) but immediately pair it with an explicit relational reframe: this is an offense against a person, not merely a shortfall in an account.

2b. Crowded Semantic Neighborhoods Needing Fencing

These are cases where English does have a usable word, but that word’s semantic space is crowded by dominant competing senses strong enough to hijack a reader’s first impression. Each requires active “fencing” — explicit boundary-setting language — rather than a bare gloss.

Term	Crowding Neighbors	Fencing Strategy
messenger	Facebook/Instagram “Messenger” app; SMS/text messaging; parcel/delivery “messenger service”	State plainly this is not a communication utility but a commissioned, authoritative representative sent with delegated purpose — closer in weight to “ambassador” than “app notification.”
priests	Roman Catholic/Anglican/Orthodox ordained clergy; clergy-abuse-scandal associations; also newly noted here: role-playing-game and video-game “Priest” character classes (a live crowding risk for younger and gamer-culture readers, e.g. healer/caster archetypes in popular RPGs), which can flatten the term into a fantasy-game class label rather than a real historical Old Testament office.	Name the Levitical, hereditary, sacrifice-and-instruction office specifically, dated to Israel’s Old Testament worship system, distinct both from later ordained Christian clergy and from any fantasy-game class archetype.
master	historical American chattel slavery; (secondarily) “master bedroom” real-estate terminology debates and “master’s degree” academic usage, both low-stakes but adding noise	Anchor “master” tightly to its co-occurring “Father” in Malachi 1:6 so the term is read relationally (rightful, loving authority) rather than in isolation, where the slavery association dominates unchecked.
tithe	prosperity-gospel/televangelist fundraising appeals; MLM-adjacent “tithe 10% of your income” jokes in secular commentary	State explicitly that Malachi’s tithe is a communal-provision covenant obligation (supporting Levites, Temple, and the poor), not a fundraising technique or a faith-formula for personal financial return.
curse	fantasy-fiction “cursed items/curses” (games, films); casual “curse words” = profanity	Restore the formal covenant-sanction/malediction sense explicitly before any teaching use; note this is a legal-relational category, not a magic spell.
fear (the LORD)	clinical anxiety/phobia language; “put the fear of God into someone” (intimidation idiom)	Distinguish reverent awe from terror explicitly, on the model of the baseline’s treatment of “holy.”
Day of the LORD	disaster-movie apocalypticism; the “Judgment Day” framing widely popularized by the Terminator film franchise, a concrete and recognizable pop-culture anchor for many contemporary readers; non-Christian eschatologies (e.g., karmic cycle frameworks)	State plainly this is a real, personal, morally decisive act of the actual God of Israel in real history, not a science-fiction scenario or an impersonal cosmic reckoning mechanism.
election (Jacob/Esau)	political voting	Apply baseline Romans clarification verbatim; do not draft new language.
covenant	real-estate/HOA “restrictive covenant”; loan/contract “covenant not to compete”	Apply baseline Romans clarification verbatim.
Lord / LORD	British aristocratic titles; fantasy fiction (“Dark Lord,” “Lord of the Rings”)	Apply baseline Romans clarification verbatim, plus the Malachi-specific adon/YHWH distinction noted above.
great King	fantasy kingdoms in film, television, and games	Apply baseline “kingdom of God” clarification pattern; stress universal, real, present sovereignty over “the nations” (1:14), not an imagined realm.
Sun of Righteousness	sun-sign astrology; “solar” New Age spirituality	Flag as an English hymnic pun (Wesley), not a Hebrew wordplay; keep the passage’s healing/righteousness framing explicit against astrological misreading.
offering	”the collection plate”; sports/media metaphor “offering himself up”	Frame as one component of a broader worship-quality indictment (also including honor, teaching integrity, and marital faithfulness), not a giving-levels critique alone.
foreigner / sojourner	contemporary immigration-policy vocabulary (“alien,” “illegal,” “undocumented”)	State the biblical protected-resident category without adopting or resolving a live partisan policy debate; avoid “alien” and “immigrant” entirely as unnecessarily policy-loaded substitutes.

---

3. Transliteration vs. Paraphrase Decisions

Because source and destination language are both English, “transliteration” here concerns two related decisions: (1) whether to retain a traditional English Bible-translation phrase alongside a modern gloss (as the baseline retained “seed of David” and “Abba”), or fully modernize; and (2) whether any Hebrew loanword should be preserved untranslated for theological texture, as the baseline chose to preserve “Abba” in Romans 8:15.

Term	Decision	Rationale
מַשָּׂא (massa)	Paraphrase: use “message” (NLT default) for published material; retain the older literal “burden” only as a teaching-note aside, not as the primary rendering.	”Burden” is more literal but risks reading as emotional weight/hardship rather than a solemn divine commission; “message” is the established site-wide NLT default and avoids the “oracle” false-friend risk (Delphic/tech-brand collision) already logged in the glossary.
יְהוָה צְבָאוֹת (YHWH tseva’ot)	Paraphrase, NLT default: “LORD of Heaven’s Armies,” with the traditional English liturgical phrase “LORD of hosts” retained in teaching notes for readers of older translations and hymnody. Reject the rare transliteration option “Sabaoth” (as in the “Holy, Holy, Holy” hymn’s “Lord God of Sabaoth”) as too obscure and liturgically narrow for a general contemporary audience.	Matches the site-wide NLT citation rule; “hosts/armies” language needs active recovery of its military-sovereignty force regardless of which English rendering is used.
הָאָדוֹן vs. יְהוָה within 3:1	No transliteration option exists in English orthography. Decision: rely on explicit verbal/written clarification (see §2a above), not on typographic convention (Lord/LORD) alone, since that convention is invisible in speech.	This is the single most structurally fragile point in the whole book for an English-only destination language; typography cannot carry the doctrinal weight alone.
מַלְאָךְ (mal’ak)	Full English rendering, no transliteration: “messenger,” with mandatory explicit clarification distinguishing it from both “angel” and the messaging-app sense.	No plausible transliteration benefit; the risk is conceptual/cultural crowding, not obscurity, so a loanword would not help.
מַלְאַךְ הַבְּרִית (mal’akh habberit)	Full phrase retained: “messenger of the covenant,” never shortened to “the messenger” alone in any context discussing 3:1, to avoid silently collapsing two possibly distinct figures into one.	Consistency requirement; shortening the phrase would erase the very distinction the term registry flags as Critical.
אֵלִיָּה (Eliyah)	Retain standard fixed English Bible-tradition spelling “Elijah”; no new decision required.	Already stable across centuries of English Bible translation; flag only the Elijah/Elisha confusion risk and the secularized-given-name dilution, not a spelling question.
מַעֲשֵׂר (ma’aser)	Retain the established English loan-derived term “tithe”; reject flattening to “a tenth” (too vague, loses covenant-obligation force) or “giving” (too generic, loses the specific 10% category).	”Tithe” is the term with the strongest established Bible-translation-tradition weight, despite its negative prosperity-gospel association, which is better handled by explicit contextual fencing (§2b) than by word substitution.
שֶׁמֶשׁ צְדָקָה (shemesh tsedaqah)	Retain the traditional English phrase “Sun of Righteousness” for continuity with English hymnody (Wesley’s “Hark! The Herald Angels Sing”), paired with an explicit disclaimer that the Sun/Son homophone is an English-language pun, not a feature of the Hebrew text.	Modernizing away from this phrase (e.g., to “the healing sun of justice”) would sacrifice a genuinely valuable point of contact with the existing English hymnic tradition for no compensating clarity gain.
חֵרֶם / מְאֵרָה (cherem / me’erah)	Accept the English collapse into one word, “curse”; do not coin two artificial English terms.	Inventing new vocabulary would depart from established English Bible-translation convention and create unnecessary friction; contextual glossing is sufficient and more consistent with pipeline norms.
גֵּר (ger)	Use “foreigner” as the primary modern-register term, with “sojourner” retained parenthetically for cross-reference to older translations. Reject “alien” (sci-fi and legal-status baggage) and “immigrant”/“migrant” (live contemporary policy loading).	Minimizes accidental importation of an unrelated, currently live political debate into a fixed ancient legal-covenantal category.
חֻקִּים וּמִשְׁפָּטִים (chuqim umishpatim)	Retain the traditional legal-pair phrase “statutes and ordinances”, but require immediate reconnection to covenant instruction in any teaching use; reject flattening to “rules” (too casual) or “laws” alone (redundant with torah, already in use for 2:6-9).	Preserves solemnity and technical precision while flagging the municipal/zoning-code dilution risk already logged in the term registry.

General finding on loanword retention: unlike the baseline Romans package, which found genuine warrant to preserve one Hebrew/Aramaic loanword untranslated (“Abba,” for its irreducible filial intimacy), this analysis finds no comparable case in Malachi. No Hebrew term examined above carries a comparably untranslatable texture that would justify introducing a new unglossed loanword into English-language teaching material. All Malachi-specific terms are best served by full English rendering plus explicit contextual fencing, not transliteration.

---

4. Ranked List of This Letter’s Highest-Risk Ambiguities

Ranked by combined severity (dominant competing-sense strength × doctrinal centrality × likelihood of confident misreading rather than a flagged comprehension gap), per the baseline’s own false-friend-over-obsolescence weighting principle.

1. Lord/LORD (adon vs. YHWH) collapse — Malachi 3:1 — Critical. The single highest-severity ambiguity in the letter: two distinct Hebrew titles rendered near-identically in English, with the only surviving distinction (capitalization) invisible in speech. Directly affects the core passage. Mitigation: mandatory verbal/written clarification, never typography alone.

2. Messenger / messenger of the covenant two-figure ambiguity — Malachi 3:1 — Critical. Compounds a trivialized modern word (“messenger” = app) with a real exegetical question (one figure or two?) at the exact center of the core passage. Mitigation: explicit naming of both figures; never silently merge or silently shorten.

3. Day of the LORD vs. secular apocalypticism — Malachi 3:2; 4:1,5 — Critical. Contemporary disaster-film and “Judgment Day” franchise tropes are a strong, ready-made, confidently-held competing frame. Mitigation: state as real, personal, historical divine action, explicitly distinguished from cinematic doomsday tropes.

4. Election (Jacob/Esau) vs. political voting — Malachi 1:2-3 — Critical. Inherits the baseline’s Critical rating exactly, and Malachi is the direct Old Testament source text behind Romans 9, raising the stakes of getting this consistent across curricula. Mitigation: apply the identical baseline clarification verbatim.

5. Covenant’s double application (priestly + marital) — Malachi 2:4-8, 2:14; 3:1 — High/Critical. Baseline-locked term, but Malachi uniquely stacks two applications in one book, and readers are unlikely to intuit unaided that marriage is being called a “covenant” in the same theological register as Israel’s covenant with God. Mitigation: make the double application explicit; do not assume it is self-evident.

6. Tithe vs. prosperity-gospel fundraising rhetoric — Malachi 3:8-10 — High. A term that is simultaneously obsolescent (unfamiliar to secular readers) and false-friend-prone (familiar to churched readers in a distorted, transactional sense) — an unusually double-edged risk profile. Mitigation: explicit contrast with prosperity-gospel framing before teaching the passage.

7. Divorce — genuine textual/translation variance — Malachi 2:16 — High. Unlike most entries here, this is not primarily an English-drift risk but a real scholarly-textual difficulty reflected in differing published English Bible translations. Mitigation: present the range transparently; do not silently pick one reading.

8. Priests — clergy-abuse stigma + fantasy/gaming-class crowding — Malachi 1:6-2:9 — High. A term now carrying two independent negative associations (institutional scandal; RPG/game-class fictionalization) neither of which existed when the term was first used. Mitigation: explicit historical anchoring to the Old Testament Levitical office.

9. Fear the LORD vs. terror/anxiety — Malachi 3:16 — High. Contemporary “fear” defaults overwhelmingly to a clinical or intimidation sense. Mitigation: explicit reverent-awe reframing, parallel to the baseline’s “holy” treatment.

10. Turn/return vs. therapeutic self-improvement language — Malachi 3:7; 4:6 — High. A subtler risk than outright false-friend drift: the competing sense is not wrong so much as morally lighter than Malachi intends. Mitigation: restore decisive moral reorientation language without denying repentance’s genuine relief and renewal.

11. Sun of Righteousness — English pun vs. astrology crowding — Malachi 4:2 — High. Risk is subtle because the Sun/Son pun is a genuine, valuable English hymnic asset that could be mistaken for an exegetical claim if not flagged as English-specific wordplay. Mitigation: explicit hymn-tradition attribution, explicit disclaimer re: the Hebrew text.

12. Curse (cherem/me’erah collapse) vs. fantasy/superstition register — Malachi 2:2; 3:9; 4:6 — Medium-High. Lower severity than the above because the fantasy-genre collision, while real, is less likely to produce confident doctrinal misreading than to produce a flattened, less serious impression. Mitigation: contextual sense-glossing at each occurrence per §2a.

13. Foreigner/sojourner vs. immigration-policy discourse — Malachi 3:5 — High. Ranked lower than doctrines 1-11 because the collision, while politically charged, is less likely to produce outright doctrinal error than to produce reader distraction or defensive reading. Mitigation: state the biblical category neutrally, without adopting a contemporary policy position.

14. Master vs. slavery-era connotation — Malachi 1:6 — High. Requires sensitive framing but is comparatively contained to a single verse-pair rather than recurring across the book. Mitigation: pair with “Father” to relationally anchor the term.

15. Offering vs. collection-plate narrowing — Malachi 1:7-14; 3:3-4 — Medium. Lowest-ranked High/Medium item: the competing sense (giving money) is at least adjacent to, not wholly unrelated to, the biblical concept, so the risk is one of narrowing rather than outright category error. Mitigation: explicit broadening to the full worship-quality indictment.

---

5. Compliance and Forward Handoff Notes

• All findings above are consistent with, and do not alter, the risk tiers already recorded in 08_core_glossary.md and bible_term_registry.json.
• Baseline-locked terms (covenant, Lord, righteousness, law, father, election, baseline-adjacent God, sin, resurrection, providence) are treated here strictly as fixed inputs; no alternative rendering is proposed for any of them anywhere in this document.
• The Lord/LORD typographic-collapse finding (§4, rank 1) and the dual-messenger finding (§4, rank 2) should be flagged for Phase 2 Step 16/17 as requiring not just theologian review but explicit format-level requirements (audio/spoken-content scripts must state the distinction aloud; print content cannot rely on capitalization alone).
• No new Hebrew loanword transliteration is recommended anywhere in this letter (§3, general finding); all Malachi-specific terms proceed to translation_memory.json update as fully English renderings with contextual fencing, matching the pattern already established for the majority of baseline Romans terms.