Work with us

Tell us a bit about how you'd like to work with tri-bible.ai.

Core Glossary

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 Bavarian translation in this curriculum’s chosen semi-phonetic spelling convention
  • A transliteration field recording an attested alternate phonetic spelling, illustrating the orthography’s genuine non-standardization rather than asserting a second authoritative form
  • The doctrine risk tier (Critical/High/Medium/Low)
  • Explicitly rejected alternatives, with reasons
  • Notes explaining any non-obvious translation choice, including whether the term is a native dialect adaptation or a wholesale register-gap borrowing from standard German

Governing principles

  1. Honesty about the register gap over invented authenticity — where a term (Gerechtigkeit, Rechtfertigung, Kindschaft, Erwählung) has no native Boarisch coinage, this glossary retains the borrowed standard-German form with dialect pronunciation rather than manufacturing a folksy-sounding alternative that would imply a doctrinal precision the dialect tradition never actually developed.
  2. Explicit flagging of competing folk-devotional defaults — every High-risk term tied to Bavaria’s concrete regional Catholic practice (saints, intercession, church) records why the natural dialect rendering defaults toward a specific local devotional frame (a patron saint, the Altötting shrine, a parish’s Kirchweih festival), so a translator or reviewer understands the reasoning rather than just following a rule.
  3. Version-controlled and append-only in Phase 2, spelling included — if a new term is discovered during document translation, both its meaning and its chosen spelling are added to translation memory and the version number incremented, never silently improvised or respelled per-document, since consistency here cannot be inherited from an external standard the way it can for this batch’s other five languages.

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 and spelling, the doctrine registry explains why that vocabulary matters.