Executive Summary — Mark 1–16 (English → Dutch)

Why it matters

Mark is the Bible study curriculum’s first extension of the Dutch Language Package beyond Romans, and it raises the doctrinal-risk bar substantially. Where the Romans baseline logged 3 Critical doctrines, Mark’s own registry logs 9 — plus a genuinely new, high-stakes cultural collision (the doulos/“slaaf” servant-language cluster) that has no precedent in the Romans package and directly touches the Netherlands’ unresolved public reckoning with its own transatlantic slave-trading history. Getting this Language Package right determines whether Dutch learners encounter Mark’s core claims — Jesus as suffering Son of God, the ransom for many, the cost of discipleship — with their full force intact, or quietly flattened by secularization, denominational crosswinds, or well-meant softening.

Key findings

• Doctrine risk profile (from doctrine_risk_registry.json): 9 Critical, 8 High, 8 Medium, 2 Low doctrines across 27 total doctrines mapped to Mark 1–16. 17 doctrines (Critical+High) require mandatory human theologian review; 8 require native speaker review; only 2 are automated-only.
• Term-level risk profile (from assets/translation_memory.json, 87 total entries — 28 inherited from Romans, 59 new to Mark): 18 terms at Critical risk, 24 at High risk — 42 terms (Critical+High) requiring theologian-level scrutiny, nearly half of the entire glossary.
• The core passage (Mark 10:35-45) is the single densest pericope in the book, simultaneously activating five doctrines (three of them Critical) and containing the curriculum’s two highest-stakes single-word decisions: “losprijs” (ransom) and “voor velen” (for many), where Dutch “voor” structurally underdetermines the substitutionary force the Greek ἀντί requires.
• Mark introduces one genuinely new class of risk absent from Romans: the “slaaf” (slave, δοῦλος, 10:44) collision with the Netherlands’ 2022–23 formal state apology for VOC/WIC-era slave trading — the single most Dutch-culture-specific risk identified across either curriculum to date.
• “Mensenzoon” (Son of Man) is a systemic, pervasive risk, not a single-verse problem: it recurs roughly 14 times and, in a low-Bible-literacy, highly secularized readership, defaults to “mere human being,” inverting Mark’s intended Danielic throne-claim.

Risks

• Highest-stakes single ambiguity: ἀντὶ πολλῶν / “voor velen” (10:45, 14:24) — Dutch “voor” does not force the substitutionary reading; NBV21 itself inconsistently drifts to “bevrijding” at 10:45 while keeping “voor velen” at 14:24, a trap this curriculum must not repeat.
• Highest cultural-sensitivity risk: “slaaf” (10:44) — usable in both directions of harm: trivializing casualness or euphemistic softening that mutes Jesus’ deliberate shock.
• Highest pastoral-harm risk: “godslastering tegen de Heilige Geest” (3:28-30) — documented history of Dutch bevindelijke piety readers wrongly fearing they have committed the unforgivable sin.
• Highest silent-drift risk: “zonde” and “de hel,” both prone to colloquial trivialization (“wat een zonde,” “het is hier de hel”) that can erase the doctrinal weight of universal accountability and eschatological judgment respectively.
• Highest structural-integrity risk: inconsistent rendering of Mark’s deliberate repetitions — the Messianic Secret silencing formula (7 occurrences), the three Passion predictions, and the Heer/heersen wordplay — any of which, if smoothed by well-meaning stylistic variation, erases a literary device carrying real theological weight.
• Sectarian misuse risk: Mark 10:18 and 13:32 are documented Jehovah’s Witness (Nieuwe-Wereldvertaling) proof-texts against Christ’s deity; every mainstream Dutch translation renders them accurately, so the risk sits entirely in teaching-note framing, not translation choice.

Opportunities

• The Heer/heersen wordplay (10:42, cf. 12:35-37) is a genuine, teachable resonance native to Dutch (both words share the root “heer”) that mirrors the Greek kyrios/katakyrieuō pun almost exactly — a rare case where the target language offers the same rhetorical device as the source, and it should be actively exploited in teaching material rather than merely preserved.
• Dutch’s vrees/angst distinction usefully separates reverential fear from anxious fear, letting Mark’s faith-versus-fear motif land with more nuance in Dutch than a single English “fear” allows.
• The Kyrie-derived liturgical register (“ontferm U over mij,” “met ontferming bewogen zijn”) gives Dutch a ready-made, emotionally warm vocabulary for compassion and mercy that both Reformed and Catholic audiences already recognize from worship.
• Fencing “lijdende Dienstknecht” exclusively for the Isaiah 53 Suffering-Servant title (newly proposed in this Language Package) solves a genuine three-way Dutch vocabulary crowding problem (knecht/dienaar/dienstknecht) before it can cause confusion in Phase 2 translation.

Recommended actions

1. Route all 17 Critical/High doctrines and all 42 Critical/High terms through mandatory human theologian review before any Phase 2 segment ships, per the escalation rules now encoded in 12_ai_translation_requirements.md.
2. Treat Mark 10:45 and 14:24 as one non-severable teaching unit in every lesson plan; never expound “losprijs” or “voor velen” without cross-referencing “bloed van het verbond.”
3. Attach a mandatory historical-pastoral framing note to every occurrence of “slaaf” addressing the Dutch VOC/WIC history and 2022-23 state apology, reviewed by a human theologian before publication.
4. Lock the Messianic Secret silencing formula, the Passion-prediction triad, and the servant/slave escalation (dienaar → slaaf) to single, fixed Dutch renderings across every occurrence, enforced via the validation checklist.
5. Adopt HSV (YouVersion ID 1394) as the default citation version and NBV21 (ID 2938) as secondary comparison, per 05_translation_landscape.md, and never default to BGT or Het Boek phrasing for any Critical or High risk term.
6. Brief all reviewers on the two Jehovah’s Witness proof-texts (10:18; 13:32) so teaching-note framing consistently forecloses the subordinationist reading without needing to alter the (already accurate) mainstream translation of either verse.

---

This summary is derived from and must remain consistent with assets/translation_memory.json, assets/bible_term_registry.json, assets/doctrine_risk_registry.json, analysis/11_doctrine_analysis.md, analysis/04_comparative_theology.md, analysis/06_linguistic_gap_analysis.md, and analysis/05_translation_landscape.md for the Mark curriculum, all of which extend and never contradict the baseline Romans Language Package.