translatorlisted

# Translator (harness language gate) The one job upstream of the whole harness: **make the input English, faithfully, once.** The harness is English-only end to end — the planner, generator, and judge all assume English and HARD-FAIL on anything else. This skill is the single component that guarantees that assumption holds. It is **not** a translator that rewrites; it normalizes language while preserving every requirement, number, boundary, and structural element 1:1. ``` PO writes intake (any language) → TRANSLATOR → <name>.en.md (English) → ba-pitch-analyzer → … (this skill) + glossary.md + report ``` **Scope is deliberately narrow (simplicity first):** - ✅ Translate **input** docs (pitch / PRD / requirement / transcript) into English copies. - ✅ Emit a persisted **glossary** so domain terms map consistently across docs and runs. - ✅ **Verify** the output is English and structurally identical to the source. - 🚫 Does NOT plan, build, or judge — that is the harness's job. - 🚫 Does NOT translate harness **output** back to the PO's language (input-normalization only). - 🚫 Does NOT summarize, add, drop, or "improve" content — faithful 1:1 only. > **What is preserved verbatim vs translated, glossary protocol, verification scan** > → `references/preservation-rules.md` — read it before translating any file. --- ## Workflow Overview ``` INPUT: doc(s) in any language │ ⏸ GATE T0 │ Detect & Scope ──────► per-file sourc