Linguistic Gap Analysis
Linguistic Gap Analysis: Philemon (English → Persian)
Destination language: Persian (Farsi, Iranian house-church and Christian register)
Baseline authority: Romans Language Package (translation_memory.json, bible_term_registry.json, doctrine_risk_registry.json). This document extends, and does not contradict, that authority. All baseline-reused terms retain their baseline risk tier and rendering; only Philemon-specific gaps and collisions are analyzed in depth below.
Scope: Full letter, Philemon 1:1–25. The core passage (1:8-21) is the theological anchor for the appeal-and-obedience doctrines but does not bound the scope of this analysis — the salutation (1:1-3), thanksgiving (1:4-7), and closing (1:22-25) are covered fully since they carry load-bearing vocabulary (church-in-a-house, fellow-prisoner, human spirit, hospitality) not present in Romans.
0. Method and Relationship to Prior Steps
This analysis builds directly on analysis/08_core_glossary.md and the Philemon-specific additions logged in assets/bible_term_registry.json. Where the Core Glossary records what term was chosen, this document records why, focusing on:
- Which doctrines have adequate existing Persian Christian vocabulary, and which have gaps;
- Where Persian’s existing religious vocabulary is “crowded” — i.e., a term already carries strong meaning in Iranian Shia Islam, Sufi mysticism, Zoroastrian heritage, or state political discourse — requiring deliberate semantic fencing;
- Where transliteration (retaining a foreign form) is preferable to paraphrase, and vice versa;
- A ranked list of the letter’s highest-risk ambiguities for Phase 2 translators and reviewers to watch for above all else.
Philemon presents a distinct linguistic profile from Romans: it is a short, intensely personal occasional letter built on wordplay, social-status vocabulary, and a single sustained rhetorical appeal, rather than systematic doctrinal exposition. The gap analysis reflects that difference — fewer purely doctrinal collisions, more social/relational and rhetorical ones.
1. Doctrine Vocabulary Matrix
| Doctrine | Available Persian Term(s) | Weaknesses | Recommended Strategy |
|---|---|---|---|
| Forgiveness and Reconciliation | بخشش (bakhshesh, forgiveness) / بخشیدن (bakhshidan, to forgive/grant); آشتی (ashti, reconciliation); به حساب من محسوب کن (accounting metaphor, v.18); بیعدالتی کردن (wronged, v.18) | بخشیدن is broad, everyday vocabulary shared with secular use (forgiving a debt, forgiving an insult) — it lacks inherent doctrinal weight and can read as simple interpersonal courtesy rather than gospel-patterned substitutionary reconciliation. آشتی (reconciliation) in Persian more often connotes conflict-resolution between quarreling equals (family disputes, tribal feuds) than a status-asymmetric master-slave reconciliation. | Do not coin a new term. Use بخشیدن/بخشش for the everyday forgiveness sense but always pair the accounting metaphor (به حساب من محسوب کن, v.18) with an explicit teaching note bridging to the baseline’s Critical عدالت محسوبشده (“imputed righteousness,” Romans 4) — this is Philemon’s unique contribution: forgiveness modeled as one believer voluntarily absorbing another’s debt, foreshadowed by and echoing Christ’s own substitution. Use بیعدالتی کردن (not the weaker ظلم) for “wronged” to keep reconciliation inside the same عدالت (justice/righteousness) root-family the baseline already anchors, rather than a separate word-family that would sever the conceptual link. |
| Christian Brotherhood across Social Status | برادر (baradar, brother); عزیز/محبوب (aziz/mahbub, beloved); همقدم (ham-qadam, fellow-traveler, optional bridge) | برادر is doctrinally rich but crowded: (a) pan-Islamic ummah-brotherhood (“all Muslims are brothers,” Quran 49:10) uses the identical word for a horizontal solidarity that nonetheless coexists with real social/legal hierarchy (including historically, slavery itself); (b) Sufi طریقت (tariqat) orders and craft-guild فتوت/جوانمردی (fotovvat/javanmardi) fraternities also use برادر while preserving a master-disciple or senior-junior rank structure internally. Neither prior use of “brother” actually dissolves social hierarchy the way Philemon 1:16 requires. | Reuse برادر (no viable substitute exists and none is needed — the word itself is fine), but require an explicit teaching gloss at every occurrence in Philemon materials: this brotherhood is a status-abolishing family category secured by union with Christ (κατὰ σάρκα καὶ ἐν κυρίῳ, “both in the flesh and in the Lord,” v.16), not a devotional solidarity-label layered on top of an unchanged social hierarchy. This is the letter’s central doctrinal payload and must not be assumed to transfer automatically from the familiar word. |
| Slavery and the Gospel’s Transforming Power | غلام (gholam, slave); بنده (bandeh, servant/slave of God — rejected here); برده (barde, slave — rejected here); آزاد کردن / اعتاق (azad kardan / e’taq, manumission) | This is the letter’s sharpest genuine vocabulary gap. غلام retains real social-legal force (correct) but Persian readers’ most available religious framework for resolving a master-slave relationship is the classical fiqh manumission procedure (اعتاق), which is a legal act freeing the slave from ownership — categorically different from Paul’s move, which does not ask Philemon to free Onesimus legally but to reclassify him relationally as برادر while (implicitly) leaving the legal question remarkably open. A Persian reader supplied only with غلام + اعتاق vocabulary will likely resolve the letter’s tension the wrong way (expecting/assuming manumission is the point) rather than see the more radical relational claim Paul is making. | Retain غلام (already fixed in the term registry as Critical). Do NOT introduce اعتاق vocabulary into the translation itself; if the manumission-expectation gap needs to be addressed, do so only in surrounding teaching/study-note material, explicitly naming and setting aside the fiqh framework as an available but insufficient comparison — Paul’s appeal exceeds manumission, not because manumission would be wrong, but because “brother” changes more than a legal category. |
| Intercession and Appeal on Behalf of Another | التماس کردن (eltemas kardan, to beseech/entreat); شفاعت (shafa’at, intercession — baseline Critical term, NOT primarily active in Philemon); دعا (do’a, prayer) | The baseline’s Critical شفاعت entry (Karbala/Hussein intercessory-suffering devotion) is keyed to Christ’s own priestly intercession in Romans 8 and does not directly recur in Philemon’s vocabulary — Paul is not interceding in a mediatorial/atoning sense but making a personal appeal (παρακαλέω) and offering a personal financial substitution (v.18). There is a real risk that Persian readers, primed by Romans study to expect شفاعت-category content, over-read Paul’s role in Philemon as a mediatorial/intercessory office parallel to Christ’s, rather than as one believer’s costly personal advocacy for another. | Use التماس کردن for παρακαλέω (already logged) and do NOT introduce شفاعت vocabulary anywhere in the Philemon translation, even loosely, to describe Paul’s role. Teaching material should explicitly distinguish Paul’s personal, non-mediatorial appeal-and-substitution from Christ’s unique, mediatorial intercession already taught from Romans 8:26-27, 34 — the analogy (someone advocating and paying on another’s behalf) is pastorally rich but must not blur the categorical uniqueness already established for Christ’s intercession. |
| Grace-Motivated Obedience | فیض (feyz, grace — baseline Critical); اختیاری/اجباری (voluntary/compulsion); رضایت (consent); اطاعت (obedience, bare form) | فیض’s baseline weakness (Illuminationist/Mulla Sadra emanationist loading) recurs identically here (vv. 3, 22, 25) and needs no new analysis. The letter’s distinctive gap is اطاعت (v.21): stripped of the baseline’s compound قید اطاعت ایمانی (“obedience of faith,” a gospel-response category), the bare noun اطاعت is Persian’s default vocabulary for the entire Shia command-hierarchy of اطاعت خدا، اطاعت پیامبر، اطاعت ائمه (obedience to God, the Prophet, the Imams) — an authority-based, not persuasion-based, category. Philemon’s argument (v.14: not by ἀνάγκη, “compulsion,” but ἑκούσιον, “voluntary”) depends on اطاعت here meaning the voluntary fruit of persuaded love, the near-opposite of the command-hierarchy sense the bare word normally carries. | Never let اطاعت stand alone without the surrounding vv.14/21 argument fully rendered nearby (اختیاری, رضایت, محبت) — the four terms function as a single interlocking argument in Persian and must be translated and taught as a unit, not verse-by-verse in isolation, or the compulsion-vs-voluntary distinction Paul is making will collapse back into the ambient command-obedience default. |
2. Missing Vocabulary vs. Crowded Semantic Neighborhoods
2.A Genuinely Missing Vocabulary (no adequate existing Persian Christian term)
| Concept | Gap | Resolution |
|---|---|---|
| The Onesimus name-pun (χρηστός/ἄχρηστος/εὔχρηστος/ὀναίμην wordplay on Ὀνήσιμος) | Persian has no lexical root shared between اُنیسیموس (a transliterated proper name) and بیفایده/سودمند/خیری ببینم (the surrounding “useless/useful/benefit” vocabulary). The entire rhetorical device — Paul teasing that a slave named “Useful” was once useless but is now truly useful — is invisible in the Persian text as it stands. | Mandatory translator’s note at both occurrences (1:11 and 1:20), already logged in the term registry. This is not fixable by a better word choice; it is a structural gap requiring paratextual scaffolding (footnote or study-note box) rather than an in-text lexical solution. |
| A single Persian term for κοινωνός (bare “partner/co-sharer,” distinct from κοινωνία “fellowship”) | Persian’s ordinary options are شریک (crowded — see 2.B below) or همکار (too weak, implies task-based collegiality rather than shared standing/identity). No existing Persian Christian usage has developed a dedicated, doctrinally-safe rendering for this bare-noun sense distinct from the already-established مشارکت for the abstract noun. | Use شریک but require mandatory contextual scaffolding (e.g., “شریک من در مسیح,” “my partner in Christ”) at every occurrence so the referent — shared standing in Christ, not commercial or religious partnership — is unmistakable from the immediate co-text; consider the compound همقدم و شریک as a heavier-handed but safer alternative for pedagogical materials (though not necessarily the flowing Bible text itself). |
| A commercial “charge it to my account” idiom that also carries theological resonance | English “charge that to my account” naturally carries both a literal accounting sense and a felt echo of substitutionary theology for English readers already familiar with “Christ paid my debt” language. Persian has functional accounting vocabulary (به حساب گذاشتن) but it does not spontaneously evoke a theological register for a Persian reader the way the English idiom might. | Deliberately engineered fix, already logged: use به حساب من محسوب کن to reuse the same محسوب root anchored in the baseline’s عدالت محسوبشده. This creates an artificial but doctrinally valuable bridge; it must be made explicit in teaching material since it will not be independently obvious to the reader the way it may be to an English reader steeped in Reformation-descended “reckoning” language. |
2.B Crowded Semantic Neighborhoods Requiring Deliberate Fencing
| Persian Term | Occupied By | Collision Risk | Fencing Strategy |
|---|---|---|---|
| شریک (sharik) — “partner” | The precise technical vocabulary of شرک (shirk), associating a partner with God — the paradigm violation of tawhid, reinforced daily in the shahada-adjacent confession “لا شریک له” (He has no partner). | The single highest lexical-collision risk in this letter. An unscaffolded “او را مثل شریک خود بپذیر” (“receive him as your شریک”) risks momentarily activating, even if only subconsciously, the exact vocabulary Persian speakers use to deny the possibility of partnership with the divine — jarringly inverted here to command human partnership between two believers. | Never let شریک appear without an immediate possessive/relational anchor naming both parties and the shared sphere (“شریک من در مسیح” / “شریکِ ایمانِ ما”)! Never use شریک in any general or abstract theological statement about God. Confine it strictly to this one interpersonal, human-to-human occurrence (v.17). Flag for mandatory human theologian review at every occurrence per the baseline’s escalation convention for Critical terms. |
| پیر (pir) — candidate for “old man” (πρεσβύτης, v.9) | Sufi spiritual mastery: a پیر is the revered master in the pir-morad (master-disciple) relationship, commanding lifelong devotional authority over the disciple’s spiritual formation — a live, culturally prestigious category in Iranian religious life. | Using پیر for Paul’s self-deprecating “I am an old man” would accidentally increase Paul’s perceived spiritual authority at the exact moment the text is working to lower it rhetorically (Paul renouncing command-authority in favor of appeal). This inverts the passage’s rhetorical function. | Use سالخورده (elderly, no spiritual-authority connotation) instead of پیر. If translating the ambassador (πρεσβευτής) textual variant instead, use the neutral سفیر. Either way, translator’s note required flagging the textual-variant decision itself. |
| اسیر (asir) — candidate for “prisoner” (δέσμιος) | The Karbala-captivity devotional category (اسرای کربلا, “the captives of Karbala”) — the surviving family of Imam Hussein taken captive after his martyrdom, a load-bearing emotional and liturgical category in Twelver Shia Muharram observance, already flagged in the baseline under “salvation.” | Naming Paul “a captive of Christ Jesus” using اسیر risks Persian readers assimilating Paul’s imprisonment into the Karbala-captivity narrative pattern — an innocent holy figure suffering unjust captivity, evoking the specific grief-and-intercession devotional response trained by Muharram observance — rather than reading it as Paul’s own neutral, legally-descriptive self-identifier. | Use زندانی (legally neutral, describes actual Roman imprisonment) throughout the letter without exception, including the compound همزندان for συναιχμάλωτος (v.23). This fencing decision is already fixed in the term registry; this analysis confirms and explains its rationale for Phase 2 reviewers. |
| اختیار (ekhtiyar) — “voluntary” (v.14, within the ἑκούσιον/ἀνάγκη pair) | The exact technical term of the classical Islamic jabr/ekhtiyar (compulsion vs. free will) theological controversy — a live, still-taught debate in Iranian seminary (howzeh) and popular theological discourse concerning divine decree versus human freedom. | A Persian reader encountering اختیاری in a scriptural text may reflexively map Paul’s narrow, relational point (Philemon should respond freely, not because Paul is forcing him) onto the much larger, unrelated metaphysical question of whether any human act is ever truly free given divine sovereignty. This would import an entire unrelated doctrinal controversy into a verse making a simple pastoral point. | Always pair اختیاری/اجباری with the concrete relational contrast it is actually drawing (رضایت, “your consent,” and محبت, “love,” v.14) in immediate proximity, so the verse’s plain relational sense is reinforced rather than left to stand as an isolated abstract philosophical claim. Flag for native-speaker review at minimum; escalate to theologian review given the baseline’s precedent of Critical/High routing for terms with a documented competing theological framework. |
| معرفت (ma’refat) — “full knowledge” (ἐπίγνωσις, v.6) | The technical term of Sufi mystical gnosis — experiential knowledge of God attained through graduated spiritual stations (maqamat) under a spiritual guide’s direction. | Risk of importing an entire Sufi epistemological framework (knowledge as mystical attainment through ascetic stages) onto Paul’s simpler point: the effective, active outworking of shared faith in recognizing every good thing believers have in Christ. | Prefer the more neutral شناخت where the mystical-attainment framework would distract from the passage’s practical, communal point; if معرفت is retained for its richer register, pair it with concrete language (“هر آنچه از خیر و نیکی در ماست به خاطر مسیح است”) that keeps the referent Christ-centered and communal rather than individually mystical. |
| دل (del) — “deep affection” (σπλάγχνα, vv.7, 12, 20) | Persian devotional and romantic poetry (Rumi, Hafez) uses دل extensively for mystical longing and romantic/spiritual union — a register broader and more diffuse than Paul’s specific, concrete compassion for named individuals. | Risk of Paul’s very concrete pastoral affection for real people (Philemon, Onesimus) drifting into generalized poetic sentiment when read against the weight of Persian’s devotional-literary دل tradition. | No substitute term is recommended (دل remains correct and necessary), but teaching material should anchor each occurrence to the specific named person in view (Onesimus at v.12: “او دل من است,” “he is my very دل ”) rather than leaving دل as free-floating sentiment. |
| عشق (eshgh) — REJECTED for ἀγάπη | Sufi mystical/romantic love vocabulary, the dominant register of Persian devotional love-poetry (divine-human love figured as beloved/lover). | Using عشق for Paul’s ἀγάπη (vv.5, 7, 9) would shift the entire letter’s argument — built on committed, other-directed, costly love as the basis of appeal — into the mystical-romantic register, undermining the sober, ethical weight the argument needs. | Confirmed rejection; retain محبت exclusively, as already logged in the term registry. No further fencing needed beyond consistent enforcement. |
3. Transliteration vs. Paraphrase Decisions
| Item | Decision | Rationale |
|---|---|---|
| Ὀνήσιμος (Onesimus) | Transliterate: اُنیسیموس | Proper name; no viable paraphrase. The wordplay loss is handled via translator’s note (see 2.A), not by attempting a meaning-preserving substitute name, which would break continuity with the wider Christian tradition’s use of this specific historical figure’s name. |
| Φιλήμων (Philemon) | Transliterate: فیلیمون | Proper name; same rationale. The φιλέω-root fittingness (v.9’s love-based appeal to a man whose name means “loving/fond”) is noted in teaching material only, not attempted in the text itself. |
| ἀββά (Abba) — cross-reference only, not in Philemon’s text | N/A for this letter | Not applicable; included here only to confirm no conflict with the baseline’s transliteration precedent. |
| ἀνάγκη/ἑκούσιον (compulsion/voluntary) | Paraphrase: اختیاری / اجباری | A transliteration is not applicable (these are ordinary Greek adjectives, not proper nouns or untranslatable technical terms); the paraphrase choice itself, however, must be fenced per Section 2.B above given اختیار’s independent theological loading. |
| κοινωνός (partner) | Paraphrase with mandatory scaffolding: شریک + possessive/relational anchor | Considered and rejected: a transliterated loanword (there is none available — this is not a proper noun) or a wholly novel coinage. A novel coinage was rejected because the baseline’s stated preference (Section on Reading Level in 12_ai_translation_requirements.md) is to prefer established compounds already used in Persian Christian theological literature over novel terms; شریک, despite its risk, is the term Persian Bible tradition (Tarjome Ghadeem/Mojdeh) already uses for this Greek word elsewhere in the NT (e.g., Luke 5:10), so consistency with existing Persian Bible usage outweighs the risk of coining an unfamiliar substitute. |
| πρεσβύτης/πρεσβευτής (old man/ambassador) | Paraphrase, with explicit textual-variant flag: سالخورده (preferred) or سفیر (if following the ambassador variant) | No transliteration applicable. The translator must record which Greek textual variant is being followed and note it, since the choice changes Paul’s rhetorical self-presentation (humble old man vs. dignified but constrained ambassador). |
| ἄχρηστος/εὔχρηστος/ὀναίμην (Onesimus wordplay vocabulary) | Paraphrase, with mandatory translator’s note | No transliteration is possible for common adjectives; the paraphrase (بیفایده/سودمند/خیری ببینم) conveys the semantic content accurately but cannot recover the pun, hence the note requirement rather than a lexical fix. |
| δοῦλος (slave) | Paraphrase (established term): غلام, not transliterated, not coined | Already an established Persian Bible tradition term (Tarjome Ghadeem/Mojdeh); no transliteration or coinage needed, but the term’s full social-legal weight must be actively taught (see Section 1) rather than assumed self-evident. |
| ἐπίγνωσις (full/experiential knowledge) | Paraphrase, with a fenced choice between two options: معرفت (richer, riskier) or شناخت (safer, plainer) | Both are native Persian paraphrase options; no transliteration applicable. Final selection should be made once during Phase 2 pre-flight and then held consistently for this curriculum (see Ambiguity #4 below). |
General transliteration policy for this curriculum: Transliterate only true proper names (اُنیسیموس, فیلیمون, and the already-baseline-fixed عیسی, مسیح, پولس, etc.). Do not transliterate common nouns, technical terms, or wordplay-bearing vocabulary — for all of these, select the best available Persian paraphrase and supply a translator’s note where the paraphrase cannot fully carry the source term’s rhetorical or theological freight.
4. Ranked List of Highest-Risk Ambiguities in Philemon
Ranked by combined severity (doctrinal/social distortion potential) and likelihood (how easily a translator or reader could default to the wrong reading without deliberate intervention).
-
κοινωνός → شریک (v.17), “receive him as you would receive me” — Highest risk. The shirk-root collision is the single sharpest lexical hazard in the letter — sharper even than the baseline’s already-flagged مشارکت, because this is the bare partner-noun itself, unsoftened by an abstract-noun form. A reader half-attending to the text could momentarily register vocabulary otherwise reserved for denying partnership with God, applied here to commanding partnership between two men. Mandatory theologian review at every occurrence; mandatory contextual scaffolding; no exceptions.
-
δοῦλος/ἀδελφός juxtaposition (v.16), “no longer as a slave… but… a beloved brother” — Doctrinally central, high risk of flattening. This verse is the letter’s thesis. The single greatest risk is not a bad word choice (غلام and برادر are both correctly chosen) but under-teaching the force of the transition between them — allowing “brother” to be read as an additional honorific layered on top of unchanged slave status (paralleling how ummah-brotherhood or guild fraternité can coexist with real hierarchy) rather than a status-superseding reclassification. Requires the most extensive surrounding teaching-note support of any single verse in the letter.
-
ἑκούσιον/ἀνάγκη and ὑπακοή (vv.14, 21), voluntary consent vs. compulsion; obedience — High risk of unintended doctrinal importation. اختیار’s live technical currency in Iranian jabr/ekhtiyar theological debate, combined with اطاعت’s default association with the Shia obedience-hierarchy (God/Prophet/Imams), creates a real risk that this letter’s narrow relational argument (respond freely because you are persuaded by love, not because you are commanded) gets absorbed into one of two much larger, unrelated frameworks: either the metaphysical free-will debate, or the authority-based obedience-to-office category. Both vv.14 and 21 must be translated and taught as a single interlocking unit, never in isolation.
-
ἐπίγνωσις (v.6), “full knowledge of every good thing” — Medium-high risk, register drift. The choice between معرفت (richer, Sufi-adjacent) and شناخت (plainer, safer) is a genuine open decision with no baseline precedent to constrain it (this word does not occur, in this sense, in the Romans curriculum). Left unresolved, different Phase 2 workers could make inconsistent choices, and whichever is chosen risks pulling the verse toward a Sufi mystical-attainment framework the text does not intend. Recommend fixing this choice now, in translation memory, before Phase 2 begins, rather than leaving it to per-segment discretion.
-
δέσμιος (throughout) vs. the culturally adjacent ἀσίρ/Karbala-captivity register — Medium risk, well-mitigated but requires constant vigilance across five occurrences (1:1, 9, 10, 13, 23). The fencing decision (زندانی only, never اسیر) is already sound and documented, but because “prisoner” recurs five times across a short letter, there is real cumulative risk of drift toward the more emotionally resonant اسیر vocabulary in less formal drafts, study guides, or spoken teaching that paraphrases the text. Flag for consistency-check across all derived materials, not just the primary translation.
-
πρεσβύτης (v.9), “Paul, an old man” — Medium risk, single occurrence but high rhetorical stakes. The rhetorical logic of the entire appeal (Paul deliberately lowering his own authority-claim) depends on this self-description landing as humbling, not exalting. Using پیر would invert this function. Lower cumulative risk than items 1-5 because it is a single occurrence, but the potential distortion, if mishandled, works directly against the letter’s central persuasive strategy.
-
The Onesimus name-pun (vv.11, 20) — Lower doctrinal risk, but total recoverability failure without intervention. Unlike the items above, there is no wrong word choice to make here — بیفایده/سودمند and خیری از تو ببینم are both accurate. The risk is pure information loss: without the mandatory translator’s note, Persian readers lose an entire layer of the letter’s wit and argument (that Onesimus, whose very name means “useful,” was once useless and is now, fittingly, useful) with no way to recover it from the text alone. Ranked lower than the items above because it degrades delight and rhetorical texture rather than doctrine, but it is the single most certain loss in the letter if the required notes are omitted.
-
σάρξ in its social-sphere sense (v.16), “both in the flesh and in the Lord” — Lower risk but requires explicit disambiguation given prior Romans exposure. House-church readers who have studied Romans will have σάρξ trained into them as the Critical sin-nature/flesh vocabulary; encountering the same Greek word (rendered differently, در جسم, in Philemon) in a neutral social-sphere sense could cause confusion if the distinction is not flagged. Lower ranking reflects that the Persian rendering itself (در جسم rather than reusing any sin-nature vocabulary) already substantially mitigates the risk; a brief note suffices.
5. Summary Recommendations for Phase 2 Pre-Flight
- Fix the معرفت vs. شناخت decision for ἐπίγνωσις (v.6) in translation memory before Phase 2 batch processing begins, to prevent inconsistent worker-level choices.
- Require mandatory contextual scaffolding (not just glossary-correct word choice) at every κοινωνός/شریک occurrence (v.17) and escalate to human theologian review without exception.
- Treat vv.14 and 21 (voluntary/consent/obedience cluster) as a single translation-and-review unit rather than independent segments, given the interlocking argument across them.
- Carry forward, without exception, the baseline’s established غلام/برادر, زندانی (never اسیر), and سالخورده (never پیر) fencing decisions already fixed in the term registry — this document confirms their rationale for reviewer training purposes.
- Attach mandatory translator’s notes at both Onesimus wordplay occurrences (vv.11, 20); this is a paratextual requirement, not a translation-choice problem.
- In all teaching/study material (not the base translation text), explicitly distinguish Paul’s personal, non-mediatorial appeal in Philemon from Christ’s unique mediatorial intercession already established from Romans 8, to prevent شفاعت-category over-reading of Paul’s role.
This document extends but does not amend translation_memory.json, bible_term_registry.json, or doctrine_risk_registry.json. Any new term or risk designation proposed above requires formal entry into those files, per the baseline’s version-increment and theologian-review procedures, before Phase 2 translation begins.