Linguistic Gap Analysis
Linguistic Gap Analysis: Titus (English → Urdu)
0. Purpose and Method
This document executes PRD Phase 1 Step 8 for the book of Titus. It does not re-derive terms already fixed by the baseline Romans/Galatians Language Package or by the Titus-specific glossary and registry already produced (08_core_glossary.md, Titus bible_term_registry.json); it audits that vocabulary set for structural gaps, semantic overcrowding, and transliteration-vs-paraphrase tradeoffs, and it produces a ranked risk list to steer Phase 2 review routing.
Titus compresses an unusually dense cluster of Critical-risk material — the sharpest unqualified salvation-by-grace statement in this curriculum (3:5), the most explicit Granville-Sharp deity-of-Christ construction (2:13), the only regeneration/new-birth vocabulary in this pipeline (3:5), and three separate purity-vocabulary roots (1:15; 2:5; 3:5) — into three short chapters. This document’s central finding is that Titus’s linguistic risk is not primarily about missing words (most doctrines here have adequate, even abundant, Urdu vocabulary) but about semantic overcrowding: several of Titus’s key terms sit inside Urdu semantic fields already densely populated by specific, load-bearing Islamic theological or legal technical vocabulary, such that the correct Urdu word still requires active fencing to prevent readers supplying the neighboring Islamic concept by default.
Full-book coverage: this analysis spans Titus 1:1–3:15. The core passage (2:11–3:8) receives the deepest treatment, consistent with its status as the theological anchor of the curriculum, but no chapter is silently skipped.
1. Doctrine Vocabulary Matrix
For each of the seven curriculum doctrines, this matrix records: the available Urdu term(s), their specific weaknesses in this context, and the recommended handling strategy. All recommended terms are already fixed in the Titus translation_memory/bible_term_registry entries; this matrix explains why, for Phase 2 reviewers who need the reasoning, not just the output.
1.1 Grace That Trains for Godly Living (Titus 2:11-12; 1:1)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| فضل (grace, REUSE) | None on its own; risk is downstream, in what follows it (تربیت, دینداری) | Retain exactly; anchor every occurrence of تربیت/دینداری back to فضل as the acting agent |
| تربیت دیتا ہے (trains, NEW) | تربیت is a major term in Islamic pedagogical discourse (tarbiyah as a whole formation-system administered under religious law/authority); risks reversing Paul’s causal order — “grace trains” heard as “training earns/maintains grace” | Retain تربیت دیتا ہے but require an explicit note at first occurrence: grace is the source and agent of training, not a duty grace imposes for the believer to then earn standing by fulfilling |
| دینداری (godliness, NEW) | دین denotes a comprehensive religious system in Urdu/Arabic use (“Dīn-e-Islam”); دینداری risks being heard as “faithful adherence to one’s religious system” rather than Paul’s narrower “reverent, grace-produced devotion to God” | Retain per established Urdu Bible Society usage, but mandatory clarifying gloss at first occurrence in every document; خدا ترسی flagged as a lower-risk fallback for reviewer discretion, not adopted as primary |
| بے دینی (ungodliness, NEW) | Same دین-root risk in reverse: could be heard as “irreligious/without a religious identity” rather than “irreverent toward the true God” | Same clarifying-gloss requirement as دینداری |
Verdict: adequate vocabulary exists; the risk is entirely in causal-order and comprehensiveness framing, not word availability. No new coinage needed.
1.2 Qualifications for Elders (Titus 1:5-9)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| کلیسیا کا بزرگ (elder, NEW) | بزرگ alone is a major South Asian Sufi devotional term for a revered holy man, frequently shrine-associated (“بزرگانِ دین”) — structurally the same collision the baseline already flags for ولی/saints | Mandatory qualifier کلیسیا کا at every occurrence, never بزرگ alone |
| نگران (overseer, NEW) | Adequate; distinct from نگہبان (reserved for Galatians’ paidagogos) and from a transliterated بشپ (implies later, unintended episcopal hierarchy) | Retain نگران; teach explicitly as the same office as کلیسیا کا بزرگ, not a separate rank |
| ایک ہی بیوی کا خاندان رکھنے والا (husband of one wife, NEW) | No direct lexical gap, but real cultural friction: Islamic law permits up to four wives (Qur’an 4:3); an unframed rendering risks being heard as a polemical statement about marriage law generally | Frame strictly as a church-office qualification, never a general marriage-law contrast; mandatory theologian pastoral-framing review |
| راست (righteous character, NEW), پرہیزگار/خدا ترس (holy/devout, NEW), ضبطِ نفس (self-controlled, REUSE) | Multiple near-synonymous virtue terms across 1:6-8 risk collapsing into one another in translation, losing Paul’s deliberately layered qualification-list structure | Preserve lexical distinctness per term (see §3 below on purity/virtue crowding) rather than harmonizing to a single Urdu virtue-word |
Verdict: no missing vocabulary; the risk is entirely in fencing بزرگ against its Sufi devotional-elite sense and framing the polygamy-adjacent qualification pastorally.
1.3 Sound Doctrine and Good Works (Titus 1:9, 13, 16; 2:1, 7-8, 10, 14; 3:1, 8, 14)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| صحت بخش تعلیم (sound doctrine, NEW) | Candidate alternative صحیح تعلیم is rejected: صحیح is a precise Islamic hadith-science term (a “sahih” hadith is authenticated through a verified transmission chain — a whole scholarly discipline, ʿilm al-ḥadīth); using it imports an authentication-methodology frame foreign to Paul’s own health/disease metaphor | Retain صحت بخش تعلیم consistently; never substitute صحیح تعلیم |
| نیک کام (good works, NEW/standing) | Not itself ambiguous, but doctrinally load-bearing: Titus uses this exact phrase six times (1:16; 2:7, 14; 3:1, 8, 14), always as fruit, never as salvation’s basis (3:5 excludes works from that role explicitly) | No lexical change needed; require a standing book-level contextual rule (see §4, Ranked Risk #2) rather than a new term |
| نیک کاموں میں سرگرم (zealous for good works, NEW) | Same basis/fruit risk, intensified by سرگرم’s redirection from its Galatians 1:14 sense (misdirected pre-conversion zeal) to a positive sense here | Retain; flag the sense-shift explicitly for reviewers moving between Galatians and Titus materials |
Verdict: adequate vocabulary; the risk is a pattern-level doctrinal discipline problem (basis vs. fruit), not a term-selection problem. See §4 for this analysis’s single highest-frequency risk item.
1.4 Salvation by Grace not Works (Titus 3:4-7, culminating 3:5’s unqualified denial)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| نجات (salvation, REUSE) | Structural, not lexical: نجات is genuinely shared vocabulary across two soteriological mechanisms (mīzān deeds-weighing vs. Christ’s finished atonement) — see baseline salvation entry | Retain; every doctrinally load-bearing occurrence requires explicit contrastive teaching, intensified in Titus by six concentrated Savior-title occurrences |
| ہمارے کیے ہوئے راستبازی کے کاموں کی وجہ سے نہیں (not by works done in righteousness, NEW) | This is Titus’s unqualified version of the doctrine — unlike Galatians’ works_of_the_law (narrowly Mosaic-Torah-anchored), 3:5 excludes ANY human righteous deed, with no qualifier at all | No softer or narrower rendering is available or desirable; the text itself is unqualified and must be translated as such — the risk is pastoral-framing (see §4 Ranked Risk #1), not lexical gap |
| رحمت (mercy, NEW) | رحمت is the central Islamic divine-attribute term (al-Raḥmān, al-Raḥīm); genuinely shared ground per baseline guidance, but the mechanism (mercy reaching sinners through Christ’s washing/renewal, not deeds-weighing) must be taught, not assumed | Retain per baseline’s own permission for general-mercy contexts; pair with explicit mechanism-teaching at 3:5 |
| فضل (grace, REUSE), راستباز ٹھہرایا جانا (justified, REUSE), وارث (heir, REUSE) | None individually weak; risk is their unusually tight grammatical linkage in 3:7 (grace → justification → heirship) which must survive translation as a single argument, not three loosely connected clauses | Preserve Greek clause structure as closely as Urdu syntax allows; flag for theologian review as a linked unit, not verse-by-verse |
Verdict: no vocabulary gap. This is the book’s highest doctrinal stakes cluster, but the Urdu lexicon is fully adequate; the entire risk is in preserving the text’s own unqualified force and its precise grammatical linkage, not in finding better words.
1.5 Regeneration by the Holy Spirit (Titus 3:5)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| نئی پیدائش (regeneration, NEW) | Matches established Urdu evangelical “born again” usage; low lexical risk on its own | Retain; this is the seed term for a doctrine appearing nowhere else in this curriculum’s baseline, so treat as a genuinely new Critical-risk entry requiring full theologian sign-off |
| نئی پیدائش کا دھلاؤ (washing of regeneration, NEW) | Highest-priority forbidden-substitution gap newly introduced by this book: غسل (the specific Islamic ritual-ablution term for the major purification rite, e.g. after specific impurity-states or before certain worship, and for washing the dead) is the single most natural-sounding candidate word a translator unfamiliar with this Language Package might reach for, and it must never be used | Use the periphrastic نئی پیدائش کا دھلاؤ, never a single-word غسل-family rendering; mandatory explicit note distinguishing this from a ritual-purification rite |
| تجدید (renewal, NEW) | تجدید carries specific South Asian Islamic revivalist-movement resonance (a mujaddid is a recognized historical “renewer” of correct religious practice, e.g. Ahmad Sirhindi, “Mujaddid Alf-i Thani”); risks being read as a communal reform-movement term rather than personal inward renewal | Retain per established usage but require a clarifying note at first occurrence distinguishing personal Spirit-renewal from a communal revivalist-movement sense |
| روح القدس (Holy Spirit, REUSE) | Standing baseline Jibreel-identification risk, unchanged | Retain baseline note requirement |
Verdict: this is the one doctrine in Titus with a genuine forbidden-substitution gap that did not exist anywhere in the Romans/Galatians baseline — غسل must be added to this book’s forbidden list. Otherwise adequately served by existing/newly coined vocabulary.
1.6 Submission to Authority (Titus 2:5, 9; 3:1)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| تابع ہونا (submit, NEW) | Adequate, but must compete against the much more idiomatically frequent اطاعت کرنا | Retain تابع ہونا as the uniform rendering across all three relational contexts (wives 2:5; slaves 2:9; citizens 3:1) |
| اطاعت (candidate, REJECTED) | اطاعت is a precisely defined Islamic political-theological term — obedience to Allah, the Messenger, and “those in authority” (ulī’l-amr, Qur’an 4:59) as a specific classical doctrine of religiously mandated political submission; using it at 3:1 risks presenting Paul’s missionally-motivated civic instruction as an endorsement of that specific Quranic doctrine | Forbidden substitution, book-specific addition to the standing baseline forbidden list |
| فرمانبردار ہونا (obey, NEW, reusing baseline فرمانبرداری root) | Lower risk, lacks اطاعت’s doctrinal weight | Retain as the paired synonym at 3:1 alongside تابع ہونا |
| حکمران اور اختیار رکھنے والے (rulers and authorities, NEW) | Political-theology sensitivity given contested classical debates over rightful khalīfah/imamate | Frame strictly as gospel-witness motivated civic conduct (3:1-2, 8), never as political-theological commentary |
Verdict: no vocabulary gap; risk is entirely in fencing تابع ہونا against اطاعت’s specific doctrinal payload. This is a clean, well-understood fencing problem, already correctly resolved in the Titus registry, but worth flagging here as a book-level, not merely verse-level, consistency rule across three separate relational contexts.
1.7 Avoiding Divisive Controversies (Titus 1:10-14; 3:9-11)
| Available Urdu term(s) | Weakness in this context | Recommended strategy |
|---|---|---|
| شریعت کے بارے میں جھگڑے (quarrels about the law, NEW) | شریعت shared with Islam’s comprehensive legal-theological term; risk of the critique generalizing beyond Titus’s specific historical controversy | Anchor explicitly to the specific Jewish-Christian-adjacent controversy Titus addresses (cf. 1:10, 14), never a general dismissal of legal/religious-law discussion |
| نسب نامے (genealogies, NEW) | Genealogy/lineage carries real ongoing social significance in South Asian Muslim culture (e.g. sayyid lineage claims) | Brief clarifying note: critique targets a specific speculative controversy, not genealogical record-keeping as such |
| تفرقہ ڈالنے والا شخص (divisive person, NEW) | Candidate بدعتی (bid’ah/bid’atī, “innovator”) REJECTED: a major, precisely defined and often severely contested Islamic theological category (doctrinal innovation), foundational to significant reform/polemical discourse — using it reframes Paul’s concern (factional strife) as a technical innovation-charge, a different and more legally/socially loaded category | Retain تفرقہ ڈالنے والا شخص; بدعتی is a forbidden substitution for this book |
| مخالفت کرنے والے (those who contradict), بے فائدہ باتیں کرنے والے / دھوکے باز (empty talkers/deceivers) | No significant risk beyond standard native-speaker review | Retain as recorded |
Verdict: no vocabulary gap. The risk pattern in this doctrine is uniform across all three terms: a natural-sounding Urdu word exists that would import a specific, named Islamic technical category (شریعت’s broadness, بدعتی’s innovation-doctrine weight) rather than Paul’s narrower pastoral concern. This is a fencing problem, not a coinage problem.
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
2.1 True gaps (no adequate existing Urdu term; new coinage or compound required)
Titus introduces remarkably few genuine lexical gaps relative to its doctrinal density — most of its distinctive vocabulary (regeneration, the Savior title-pattern, the Granville-Sharp construction) is conceptually new to this curriculum but lexically buildable from already-established baseline roots (نجات, پاک, خدا, یسوع مسیح). The clearest true gap is:
- παλιγγενεσία / regeneration — no single existing Urdu Bible term predates this book’s need; نئی پیدائش is coined by compounding, following established evangelical Urdu usage outside this Language Package’s baseline. This is the one doctrine in the curriculum’s assigned doctrine-list with no prior baseline anchor at all (Romans/Galatians never address regeneration by this name).
- λουτρὸν παλιγγενεσίας as a periphrastic unit — no single Urdu word renders this phrase; the periphrastic compound نئی پیدائش کا دھلاؤ is a genuine coinage, not a dictionary entry, and should be logged as such for consistency checking across all future Phase 2 documents.
Beyond these two, Titus’s apparent “new” terms in the glossary (e.g. خدا کا بندہ, خدا کا مہتمم, نگران) are compounds or applications of already-available Urdu vocabulary, not gaps requiring invention.
2.2 Crowded semantic neighborhoods (adequate vocabulary exists, but it is contested territory)
This is Titus’s dominant risk pattern. Four neighborhoods are unusually crowded:
(a) The purity/impurity field (پاک / ناپاک and its neighbors). Titus deploys at least four distinct Greek purity-adjacent roots in three chapters — ἅγιος (holy, baseline پاک), καθαρός (pure, 1:15; 3:5, پاک/پاک کرنا), μιαίνω (defiled, 1:15, ناپاک), ἁγνός (chaste, 2:5, پاک دامن). All four compete for the same small cluster of Urdu پاک-root vocabulary, which in ordinary Urdu usage is dominated by fiqh ritual-purity categories (ṭahāra: wudu, ghusl, food, prayer-readiness). Titus 1:15’s entire point — that purity/impurity here is a matter of conscience and belief, explicitly not ritual status — is thus translated using precisely the vocabulary family whose everyday meaning is ritual status. This is the single most crowded neighborhood in the book.
(b) The دین-root field (دینداری, بے دینی). دین denotes, in ordinary Urdu-Arabic usage, an entire comprehensive religious system, not a personal disposition. Titus’s use of εὐσέβεια/ἀσέβεια for a personal reverence-or-its-absence toward God sits awkwardly inside a root whose default reading is “adherent/non-adherent of a total religious system.”
(c) The اطاعت/تابع ہونا field (submission vocabulary). Discussed in §1.6 above; اطاعت’s specific Qur’an 4:59 doctrinal payload crowds the entire submission-to-authority semantic space, such that even the correct choice (تابع ہونا) requires active, repeated fencing rather than one-time selection.
(d) The صحیح/صحت بخش field (soundness of doctrine). صحیح’s dominant modern Urdu association is hadith-authentication methodology; صحت بخش’s health-metaphor sense must be actively preferred and maintained against the more idiomatically available صحیح alternative throughout the book, not just at first occurrence.
Recommended handling for all four: these are not solved by picking a term once. Recommend Phase 2 processing treat each as a standing fencing rule applied at every occurrence across the whole book, analogous to how the baseline treats کافر/اسلام/دعوت/تبلیغ as standing forbidden substitutions — not a one-time footnote.
2.3 A note on σωτήρ’s abundance, not scarcity
Unusually for this kind of analysis, the Savior/σωτήρ field is not crowded by a competing Islamic term at all — نجات دہندہ has no serious Urdu rival needing fencing. Its risk (see Ranked List, Risk #3) is structural (shared-mechanism, per the baseline نجات entry) and frequency-driven (six occurrences in three chapters, alternating referents), not a neighborhood-crowding problem. This is worth flagging precisely because it differs in kind from (a)-(d) above: no fencing against a rival term is needed, but a pattern-tracking discipline across six verses is needed instead.
3. Transliteration vs. Paraphrase Decisions
| Term | Decision | Rationale |
|---|---|---|
| παλιγγενεσία (regeneration) | Paraphrase (نئی پیدائش, “new birth”) | No transliteration tradition exists; a literal compound matching established evangelical Urdu “born again” usage is clearer than a Greek loanword and avoids inventing an unfamiliar technical term |
| λουτρόν (washing) in λουτρὸν παλιγγενεσίας | Paraphrase, periphrastic, deliberately generic | Any single-word candidate (especially غسل) imports ritual-practice associations; a descriptive phrase (دھلاؤ, “washing/cleansing act”) paired with a clarifying note avoids both transliteration (meaningless to readers) and false ritual-specificity |
| ἐπιφάνεια (appearing/epiphany) | Paraphrase (ظاہر ہوا / ظہور, “appeared/manifestation”) | A transliterated “ایپی فینیا” would be opaque; ظاہر ہوا draws on genuinely safe shared vocabulary (ظاہر as a recognized divine-attribute term) without needing a loanword |
| Ζηνᶰς, Ἀπολλῶς, Ἀρτεμᶰς, Τυχικός, Νικόπολις (proper names) | Transliteration (زیناس، اپلّوس، ارتیماس، تخِیکس، نیکوپلس) | Standard proper-noun handling per baseline convention; no doctrinal content to paraphrase |
| μιᾶς γυναικὸς ἀνήρ (husband of one wife) | Paraphrase, not idiom-for-idiom | A literal “one-wife man” idiom does not exist naturally in Urdu in a form that isolates the leadership-qualification sense from a general marriage-law statement; the fuller descriptive phrase ایک ہی بیوی کا خاندان رکھنے والا is deliberately more explicit than the Greek’s terseness, trading elegance for doctrinal precision given the cultural stakes |
| Κρῆτες ἀεὶ ψεῦσται (Cretan cultural proverb, 1:12) | Direct quotation + translator’s framing note, not silent paraphrase or omission | Paul is quoting a known Greek proverb as rhetorical evidence, not asserting an ethnic doctrine; this must be visibly marked as a quotation in the Urdu text (e.g. via quotation punctuation plus a footnote) so it is not read as the Bible’s own ethnic generalization |
| πιστὸς ὁ λόγος (trustworthy saying formula, 3:8 and parallel Pastoral Epistles occurrences) | Paraphrase, fixed formula | یہ بات سچی اور بھروسے کے لائق ہے renders the sense; no single-word or transliterated equivalent conveys this fixed idiom’s function as a doctrinal-summary marker |
| Ἀββά-style intimacy terms | Not present in Titus | N/A — noted for completeness; the baseline’s ابّا entry is not triggered by this book |
General rule for this book: Titus contains no cases where transliteration is clearly superior to paraphrase for a doctrinal term — every doctrinally load-bearing term is better served by paraphrase or by reuse of already-established Urdu Bible vocabulary. Transliteration is confined, correctly, to proper names and place names.
4. Ranked List of Titus’s Highest-Risk Ambiguities
Ranked by combined severity (doctrinal centrality × likelihood of misreading × review burden), not simply by the baseline’s risk tier alone, since several Critical-tier items in Titus are textually unambiguous (the text itself states them plainly) while some High-tier items carry more practical ambiguity risk in translation.
#1 — Titus 3:5’s unqualified “not by works done in righteousness.” Unlike Galatians’ works_of_the_law (deliberately narrow, Mosaic-Torah-anchored), this is a categorical denial that any human righteous deed contributes to salvation. This sits in the most direct possible tension with the mīzān (deeds-weighing) framework central to Islamic soteriology — more direct than any other single verse across this whole pipeline’s baseline. The ambiguity risk is not in the Greek-to-Urdu mapping (which is textually clear) but in pastoral reception: a careless presentation risks sounding like either (a) a denial that good works matter at all (contradicted by 3:8 one sentence later) or (b) a provocative, unqualified attack on the mīzān doctrine by name, when Paul’s own concern is narrower (grace, not merit, is salvation’s ground). Requires the basis/fruit distinction to be taught explicitly and adjacently every time, not left implicit between verses.
#2 — The good_works basis/fruit pattern across six occurrences (1:16; 2:7, 14; 3:1, 8, 14).
Not a single-verse ambiguity but a cumulative one: if even one of these six occurrences is translated or taught without the standing basis/fruit rule made explicit, a reader encountering that occurrence in isolation (e.g. in a lesson excerpt) could reasonably conclude Titus teaches works-based standing before God, directly contradicting 3:5. Recommend this be encoded as an automatic escalation rule in the Titus 12_ai_translation_requirements.md addendum: every νیک کام occurrence must carry or reference the basis/fruit note, not just the first.
#3 — The σωτήρ Father/Son title-interchange pattern (1:3-4; 2:10, 13; 3:4, 6). Individually, each occurrence of نجات دہندہ is a Critical-tier but textually clear rendering. The ambiguity risk is structural: a translator or reviewer processing these six occurrences independently (as separate segments, per the pipeline’s parallel-processing architecture) could render them competently in isolation while losing the deliberate Trinitarian data-point that Father and Son share the identical title across the letter. Recommend — as already flagged in the glossary — that this be reviewed as one cross-verse unit, and that Phase 2’s segment-caching explicitly link these six occurrences to each other.
#4 — Titus 2:13’s Granville-Sharp construction (“our great God and Savior Jesus Christ”). This is the single most textually explosive identity-statement in the book (more explicit than Romans 9:5), but it is not linguistically ambiguous in Greek — the grammar itself (one article governing two conjoined nouns) identifies Jesus as “the great God and Savior,” not two figures. The translation risk is therefore not “which meaning is intended” but “does the Urdu rendering preserve the single-referent force of the Greek grammar, or does it inadvertently read as two coordinate titles (implying two figures, God and a separate Savior).” Urdu’s own conjunction structure (اور) risks the latter misreading if not handled with care; recommend a translator’s note making the single-referent grammar explicit rather than relying on the Urdu syntax alone to carry it.
#5 — پاک/ناپاک at 1:15 (purity of conscience). Ranked below #1-#4 because, unlike them, this ambiguity is resolvable with a single well-placed clarifying note rather than requiring an ongoing structural discipline — but ranked this high because پاک/ناپاک is the most everyday, high-frequency word-pair in lived Urdu religious life, making the default (ritual-purity) misreading unusually likely without intervention. Recommend the consolidated cross-verse purity review already proposed in the glossary (1:15; 2:5; 3:5 reviewed as one unit).
#6 — λουτρὸν παλιγγενεσίας’s ghusl-adjacency (3:5). Ranked below #5 despite being flagged Critical, because the forbidden-substitution rule (never غسل) is a clean, binary, easily enforced rule rather than an ongoing interpretive judgment call — once encoded correctly in translation memory, the risk of accidental misuse is low. The remaining residual risk is a new team member or downstream tool not having internalized the forbidden-substitution list; recommend automated validation (regex-style check for غسل near نئی پیدائش) at Phase 2 QA, not just human review.
#7 — اطاعت-avoidance in submission-to-authority material (2:5, 9; 3:1). Ranked here because, like #6, the fencing rule is clear and binary once established, but this item’s risk is elevated by frequency and register pull: اطاعت is simply the more common, more idiomatically available Urdu word for “obey/submit” in general usage, meaning every one of the three occurrences is a fresh opportunity for a translator’s more natural instinct to override the Language Package’s deliberate choice. Recommend the same kind of automated forbidden-term validation as #6.
#8 — δίκαιος (righteous character adjective, 1:8; 2:12) vs. δικαιοσύνη (forensic righteousness noun, 3:5). A genuine but lower-severity risk: if راست (the lighter character-adjective rendering) is not consistently distinguished from راستبازی (the forensic-status noun), a reader could conclude that an elder’s or believer’s personal righteous character is itself contributing to the forensic standing 3:5 explicitly excludes from merit. Native-speaker-level risk, not requiring the heaviest review tier, but worth flagging as a real ambiguity given the two words’ shared root.
#9 — بزرگ’s Sufi-devotional pull in “elder” (1:5-9). Ranked lower than the above because the fencing solution (mandatory کلیسیا کا qualifier) is simple and, unlike #6/#7, بزرگ alone is not independently a “more natural” competing translation choice for this specific office — the risk is a drift toward omitting the qualifier over a long document, not an active pull toward a wrong word.
#10 — تجدید’s revivalist-movement resonance (3:5, renewal of the Holy Spirit). Lowest-ranked Critical/High-adjacent item: the collision (personal Spirit-renewal vs. communal mujaddid-style religious reform) is real but narrow, easily resolved with a single clarifying note, and unlikely to recur elsewhere in the curriculum the way #1-#7’s patterns do.
5. Summary Recommendations for Phase 2 Handoff
- Add غسل and اطاعت (in the submission-to-authority context) as new, book-specific forbidden substitutions in the Titus addendum to
12_ai_translation_requirements.md, alongside the standing baseline forbidden list. - Encode the good-works basis/fruit rule as a standing, automatic escalation rule triggered by every occurrence of نیک کام in Titus, not a one-time footnote.
- Process the six σωτήρ occurrences (1:3-4; 2:10, 13; 3:4, 6) as one linked cross-verse review unit in segment caching, not independently.
- Run a single consolidated purity-vocabulary review pass across 1:15, 2:5, and 3:5 together, given the four distinct but easily-conflated Greek purity roots in play.
- No new term coinage is required beyond نئی پیدائش and نئی پیدائش کا دھلاؤ (regeneration and its washing-image); all other apparent “new” vocabulary in this book is compound-built from already-established baseline roots and should be reviewed for fencing discipline, not lexical adequacy.
- Automated (regex-style) validation at Phase 2 QA is recommended specifically for the two binary forbidden-substitution risks (غسل, اطاعت), since these are the items most likely to be silently reintroduced by a translator’s more idiomatically natural instinct despite correct upstream glossary entries.
This analysis extends, and nowhere contradicts, the baseline Romans/Galatians Language Package and the Titus 08_core_glossary.md / bible_term_registry.json already produced. All term selections referenced here are binding as recorded in those files; this document’s role is diagnostic (gap/crowding/risk analysis) and routing guidance for Phase 2, not a new terminology decision layer.