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 Kashmiri (Perso-Arabic script) translation and Roman transliteration
• The doctrine risk tier (Critical/High/Medium/Low)
• Explicitly rejected alternatives, with reasons drawn from either Islamic theology, Kashmir Shaivism, or both
• Notes explaining any non-obvious translation choice, including where a term’s meaning is already fixed by prior religious usage

Governing principles

1. Established regional Bible-translation usage over invention — where existing Kashmiri Scripture translation already has a settled rendering (خُدا, یِسوع, خُداوند, مسیح), this glossary follows it rather than proposing an alternative.
2. Explicit rejection, not silent avoidance — every Critical-risk term records why the tempting alternative is wrong, whether that alternative comes from mainstream Islamic theology (شرک concerns, Tawhid, an already-settled meaning like Ruh al-Qudus) or from Kashmir Shaivism (shaktipat, pratyabhijna, non-dualism).
3. Dual-audience discipline — this glossary never assumes a single tradition’s risk reasoning covers both audiences; several notes explicitly separate the Islamic-context risk from the Trika-context risk for the same term.
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 matters.