Core Glossary

translation_memory.json is the enforced glossary for every Phase 2 translation in this curriculum. This document summarizes its shape and the principles behind it; see the Glossary Risk Groups for the full per-term entries.

Composition

The glossary currently holds 47 terms spanning all four risk tiers, drawn from the doctrines identified in Doctrine Analysis and grounded in the cultural risks identified in Culture Analysis. Every term entry records:

• The approved Kurdish (Kurmanji) translation and transliteration
• The doctrine risk tier (Critical/High/Medium/Low)
• Explicitly rejected alternatives, with reasons — including, distinctively for Kurdish, alternatives rejected because of political-vocabulary overlap or Sufi/Yazidi mystical-absorption risk rather than a competing orthodox-religious claim
• Notes explaining any non-obvious translation choice

Governing principles

1. Native Kurdish vocabulary where a safe option exists — this glossary prefers Xwedê, Bav, Mizgînî, and similar native terms over Arabic-derived alternatives, both for linguistic authenticity and to avoid collisions inherited from Arabic’s own linguistic history.
2. Explicit anchoring for politically-loaded terms — because Rizgarî (salvation) and Padîşahiya Xwedê (Kingdom of God) share vocabulary with Kurdish nationalist political aspiration, this glossary requires deliberate contextual anchoring rather than assuming the spiritual sense is automatically understood.
3. Guard against both rejection and over-assimilation — unlike most Language Packages, several Kurdish entries (Sonship, Incarnation) must guard against a reader too readily absorbing the doctrine into an existing Sufi or Yazidi framework, not only against outright rejection.
4. Version-controlled and append-only in Phase 2 — if a new term is discovered during document translation, it is added to translation memory and the version number incremented, never silently improvised per-document.

Relationship to the Doctrine Risk Registry

Every glossary term’s doctrine field links back to an entry in doctrine_risk_registry.json, so a term’s risk tier is always traceable to the specific doctrine it protects — the glossary enforces vocabulary, the doctrine registry explains why that vocabulary, even where linguistically correct, still requires deliberate political and theological framing for a Kurdish-speaking reader.