languagelisted

# Switching the documentation language The case this exists for: a project started in one language because the team spoke it, and somebody joined who does not. From that moment the register has to be readable by everyone, and **a half-translated register is worse than an untranslated one** — nobody knows which part is current. ## Say this first, before starting **The invocation is one gesture. The work is not.** Translating an architecture register is a careful rewrite of every document, done by reading each one, not by a script. For a project with a dozen decision records and a few dozen open questions this is substantial work, and it gets interrupted. Tell the user the size before you begin: ``` python3 ${CLAUDE_PLUGIN_ROOT}/scripts/conform.py docs/architecture wc -l docs/architecture/*.md docs/architecture/decisions/*.md | tail -1 ``` Report the number of documents and lines, and agree the order. **Do not start a switch you cannot finish in the session unless you commit per document** — see below. ## The one rule that protects the record **Evidence is not translated.** Verbatim things stay verbatim: - command output, error messages, log lines; - identifiers: element ids, table and column names, role names, file paths, commit hashes; - quoted code, SQL, configuration; - proper names and product names. A register whose evidence has been translated has stopped being evidence. If a decision record quotes `compiler: flow "Flow_toConverted" carries a condition`, that st