Yabanin — i18n glossary
Translation policy for the seven machine-translated locales (ja, ko, hi, id,
pt-BR, es, ar). Every dashboard string (web/dashboard/src/i18n/en.json) and
site string (web/site/) is translated by machine, then flagged
needs-review (see the flagging convention below). Human review is a separate
QA step (a browser-run pass covers all locales; the flag marks what still
needs a native-speaker pass).
Flagging convention
- Each locale JSON (
en.jsonsibling, e.g.ja.json) is a machine translation of the full key set — same keys, same structure, no key omissions. - Machine-translated locales are declared needs-review in
docs/plans/work-records/I18N-0<3..9>.mdand in the commit message (needs-review). - Do NOT mark individual strings; the whole locale is needs-review until a native pass completes it.
Core terminology (lineage / audit / sovereignty)
These terms carry legal and technical weight in Yabanin docs and UI. They must be translated consistently across all locales and screens; when a term is kept in English, the table says so and the translation must not invent variants.
| English | Keep in English? | Guidance |
|---|---|---|
| lineage | No | The jurisdictional provenance record of a request (region claim + evidence tier + signature). In CJK/Arabic scripts translate with the established term below; in Latin-script locales (pt-BR, es, id) prefer the direct translation, not "lineage"/"linhagem" borrowed. Avoid terms that denote ancestry or genealogy (the family-lineage connotation): the term here is about verifiable provenance of a request, not descent. |
| attestation | No | A signed, verifiable claim about where inference happened (or a tier of it). Keep "attest" as the verb family. |
| audit | No | Offline spend/quality analysis run on logs. Distinct from "security audit" — this is cost/quality audit. |
| sovereign / sovereignty | No | Data/gateway sovereignty: the customer's control over where requests and data are processed. Do not reduce to "national" only. |
| residency pack | No | A curated set of policy rules mapping a jurisdiction to routing behavior. |
| evidence tier | No | The kind of region claim: provider_attested, endpoint_pinned, header_observed, provider_declared. Tier names (the snake_case identifiers) are NEVER translated — they are API values. Only the display labels are translated. |
| signature / signature valid | No | The cryptographic verification of an attestation. |
| counterfactual | No | The cost that would have been paid without optimizations. |
| tier (model tier) | No | Routing tier for models (e.g. baseline/candidate tiers). |
| scope (applied scope) | No | The organization/provider/period filter set applied to a report. |
| credits | No | Prepaid balance. Keep the financial connotation, not "credit score". |
| gateway | No | The self-hosted AI gateway process. |
| air-gap | No | Fully isolated installation. |
| shadow mode | No | The mode that mirrors traffic for evaluation. |
| kill criterion | No | The ≥45% savings threshold that justifies a model change. |
| privacy mode | No | The dashboard mode that masks error text and raw JSON. |
| provider | No | The upstream model provider. |
| org / organization | No | Tenant organization. |
| request | No | A single API request record. |
| model | No | An LLM in the registry. |
| token / tokens | No | LLM tokens. |
| cost | No | Monetary cost. |
| savings | No | Money saved by optimizations. |
| cache / cache hit | No | Exact/semantic cache. |
| UTC | Keep | Time zone label, never translated. |
| USD | Keep | Currency code, never translated. |
| API key / agent key | No | The credential artifacts. |
| Yabanin | Keep | Brand name, never translated or transliterated. |
| Astra | Keep | Design system name, never translated. |
| OpenAI-compatible | Keep | Protocol description, keep "OpenAI". |
CJK / Arabic script-specific
- ja (Japanese): lineage → リネージ (katakana) is acceptable in product UI, but the preferred consistent term is 請求系統 (せいきゅう けいとう) when a kanji term is wanted; use リーネージ consistently in UI labels. attestation → アテスト (証明/証言). Do not mix kanji-only and katakana forms within one screen.
- ko (Korean): lineage → 리네이지 or 요구사항 계보; prefer 요구 계보 consistently. attestation → 인증/증언. Use hangul consistently; keep snake_case tier names in Latin.
- hi (Hindi): lineage → अव्यवच्छेद्यता is too heavy; use निरीक्षण-रेखा (inspection line) or keep लाइनेज (transliteration) consistently. attestation → प्रमाणपत्र/गवाही. Devanagari throughout.
- ar (Arabic, RTL): lineage → نسب الطلبات (request lineage). attestation → إثبات. sovereignty → السيادة. RTL is handled in a dedicated pass; this document only supplies the translation. Arabic numerals: use Western (0-9) for IDs, amounts, and timestamps to stay consistent with en data.
Numbers, units, and data tokens
- Numbers, currency codes (USD), dates, timestamps, IDs (
req_…,org uuid), model names (gpt-4o-mini), and field/operator tokens (starts_with,org_id) are never translated — they are data. Translations keep them verbatim, including{{interpolation}}placeholders (exact same tokens, same order where grammar allows; if word order requires, the placeholder tokens must remain intact). - Interpolated values (
{{from}},{{total}},{{pct}}) must appear in the translated string exactly as in en.
What is NOT translated
- Code snippets and CLI commands (kept verbatim in
<pre>blocks). snake_caseidentifiers and API field names.- Email addresses, URLs, brand names.
- Placeholder values that are data examples (
prod-backend,nightly-etl,acme,gpt-4o) — these are sample data, not UI copy.