ADR-002 — Language policy: Greek primary for business content

Superseded by ADR-003 (2026-07-02, same day): the decision-maker ruled that all recorded content must be English-only, even when working sessions are conducted in Greek. This ADR was proposed and never accepted; it is kept for the record.

Revision note: originally drafted in Greek; translated to English per ADR-003 (content unchanged).

Status

deprecated — proposed 2026-07-02, rejected 2026-07-02 in favor of ADR-003.

Context

The vault records the knowledge of a Greek company: capture interviews would happen in Greek, the business vocabulary (departments, roles, processes, products) is Greek, and the primary readers are Greek speakers. By contrast, the TPL infra repos (e.g. infra-okd) are English-only — but their audience is engineers and their subject technical.

A language had to be chosen explicitly, or the vault would end up an inconsistent mix with pointless back-and-forth translation.

Decision

(as proposed — rejected)

1. Greek — the primary language for business content: requirements, interviews, company/infrastructure docs, ADRs, session-log prose, HANDOFF prose.
2. English — structural elements stay English for compatibility with the TPL ecosystem and tooling: frontmatter keys and status vocabularies, established section headings (TL;DR, Status, Context, Decision, Consequences, …), file/folder names (kebab-case, English slugs).
3. Technical terms not force-translated.
4. No retranslation of existing content in either direction without cause.

Consequences

Not applicable — superseded by ADR-003 before acceptance.