Docs / 06-decisions/003-language-policy-english-only
ADR-003 Language policy — English-only vault content
All content in this repo (requirements, interviews, ADRs, session logs, HANDOFF, docs) is written in English, regardless of the language spoken in working sessions. Supersedes ADR-002.
ADR-003 — Language policy: English-only vault content
Status
accepted — 2026-07-02 (decided by: taranas). Supersedes ADR-002 (Greek-primary, proposed — never accepted).
Context
ADR-002 proposed Greek as the primary language for business content, on the grounds that capture interviews and readers are Greek-speaking. The decision-maker rejected that proposal on the day it was drafted: even when working sessions are conducted in Greek, everything recorded in the project must be in English.
This aligns the vault with the rest of the TPL ecosystem (infra-okd and infra-hyperv are English-only) and keeps the knowledge maximally portable — usable by non-Greek-speaking engineers, tools, and models without translation.
Decision
- All committed content is English — requirements, interviews, company/infrastructure docs, ADRs, runbooks, session logs, HANDOFF, plans, templates, commit messages.
- Working sessions may be conducted in Greek; the agent translates when recording. Direct quotes from interviews may be captured in English translation — preserve the original Greek phrase in parentheses only when the exact wording matters (e.g. a domain term with no clean equivalent).
- Greek proper nouns are transliterated (e.g.
Γιάννης→Yannis), same rule as infra-okd. - Do not reintroduce Greek prose in new edits.
Consequences
- The entire scaffold (written in Greek earlier today, before this decision) is migrated to English in the same change that records this ADR. Git history preserves the Greek originals.
- ADR-002 is marked superseded and kept for the record (append-only discipline).
- Interview capture carries a translation step — acceptable cost for portability.