# fidelity-translator Style Guide
This guide encodes the translation principles the skill applies regardless of language pair or domain. It is read by every translator subagent (Step 3) and every critique subagent (Step 4). When a project sets a `domain` in `project.yaml`, the corresponding domain block at the bottom is appended.
## Register
The default register is **formal-technical**. Tone matches what regulatory authorities, certification reviewers, and domain professionals expect in their working language:
- Avoid contractions in formal output ("do not", not "don't") in languages where contractions are register-marked
- Avoid colloquialisms, idiomatic expressions, marketing voice
- Match the modal-verb register of the source: a "shall" stays a "shall" (or its target-language equivalent that preserves regulatory force) — never weaken to "should" or "may"
- Match the impersonal voice of the source where the target language has one
- Preserve the source's level of nominalisation: a heavily-nominalised legal paragraph stays nominalised in the target, even if more verbal phrasing would read more naturally
## Terminology consistency — the first principle
The single biggest defect mode in technical translation is **terminology drift** — the same source term rendered differently in different chapters. The skill defends against this with two mechanisms:
1. **The pinned glossary mini-table** (provided to you at the top of each chunk) lists every source-language term in the chunk that has a target-language entry in the project glossary. **You must use the glossary's target term every time**, unless context makes it actively wrong — in which case flag with `[translator note: glossary says X, used Y because Z]` rather than silently overriding.
2. **The chunk-local consistency rule**: within a single chunk, if you choose a target rendering for a source term that is *not* in the glossary, use the same rendering for every occurrence in that chunk. Append the term to the proposals list at the end of your output.
## Section numbering, figure / table references
- Section numbers (e.g. `02.1.3`, `4.5.7.2`) are preserved **verbatim**. Never renumber.
- Tables and figures retain their original numbering; only the leading word changes (`Таблиця 01.2` → `Table 01.2`, `Abb. 3.5` → `Fig. 3.5`, `图 5-2` → `Fig. 5-2`).
- Cross-references inside body text update their leading word: a paragraph that says "see Таблицю 4.1" becomes "see Table 4.1" (preserve the case-grammar of the target language too — German's "siehe Tabelle 4.1", French's "voir Tableau 4.1").
## Numbers, units, dates, locale
- Units: SI stays SI verbatim. Imperial → SI with parenthetical on first mention (`1,000 ft` → target language equivalent of `300 m (1,000 ft)`).
- Decimal separator: convert per target locale. EN uses `.`, most EU languages use `,`. The skill's verification step will catch failures here.
- Thousands separator: per target convention (space, comma, dot, or none).
- Dates: per target convention. ISO 8601 (`2026-04-15`) is the safe inter-lingual format when in doubt; otherwise convert to local order.
- 24h vs 12h time: most regulated traditions use 24h; convert if source uses 12h.
- Currency: keep original currency code; convert with parenthetical only if conversion is genuinely useful and the rate is documented.
## Callouts — DANGER / WARNING / CAUTION / NOTE
These map across ICAO / ISO / ANSI Z535 conventions:
- **DANGER!** — imminent risk to life if not avoided
- **WARNING!** — risk to life / health
- **CAUTION!** — risk of equipment damage or non-fatal injury
- **NOTE!** — clarifying info, not a hazard
**Never swap a hazard category in translation.** A `WARNING` does not become a `CAUTION`, even if the target-language tradition uses different visual conventions. The hazard category IS the regulatory meaning.
When the source uses a category that the target tradition does not have an exact equivalent for, render the nearest equivalent and add a `[translator note]` explaining the choice. Examples:
- Russian "ОСТОРОЖНО" sometimes used for both WARNING and CAUTION semantics → flag to reviewer
- Japanese `備考` is sometimes used for both NOTE and clarifying-info — usually fine to render as NOTE
## Regulatory citations — preserve, then explain
Cross-references to regulations stay in their **original language** form (because the reviewer will look them up by their registered title in that language), followed by a target-language explanatory parenthetical the *first* time they appear in the document. Subsequent occurrences are bare.
- `Постанова Кабінету Міністрів України від 06.12.2017 № 954` (UA source) → `Postanova KMU No. 954 of 06 Dec 2017 (Cabinet of Ministers Resolution)` (EN target, first mention)
- `Verordnung (EG) Nr. 216/2008` (DE source) → `Regulation (EC) No. 216/2008 (Verordnung (EG) Nr. 216/2008)` (EN target, first mention)
- `FAR Part 23` (EN source) → translate as `FAR Part 23 (Federal Aviation Regulations, Part 23 — местная пояснительная)` (RU target)
- `EASA Part 21.J` (any source) → preserved verbatim; on first appearance, add target-language gloss
Standards-body identifiers (ISO 13485, IEC 62304, ICH E6, STANAG 4671) are universal — preserve verbatim, no translation.
## What to leave untranslated
- Drawing numbers, part numbers, schematic identifiers
- Trademarks, product names, model designations (`Saito FG-40`, `BR-200`, `Falcon X7`)
- Latin-script regulatory IDs (FAR 23.1309, AC 21-26, STANAG 4671, ISO 13485)
- File paths, code snippets, schema names, machine-readable identifiers
- SI unit symbols (m, kg, s, N — but unit *words* like "metre" / "Meter" / "метр" do translate)
- Latin scientific names (binomial nomenclature)
- Quoted text from law/regulation in its original language — translate immediately after in a parenthetical or bracketed block
## What NOT to do
- **Do not paraphrase warnings, safety notes, or modal-verb clauses.** Translate them precisely. Loose paraphrase of a safety-critical instruction is a defect.
- **Do not add information not in the source.** No "translator's helpful expansions". If the source is unclear, flag with `[translator note: ...]`.
- **Do not drop content.** Repetitive boilerplate (page header / footer repeated on every page) can be deduplicated structurally, but body content stays.
- **Do not "improve" the source.** If the source has an error, reproduce it faithfully (and flag in a translator note if you noticed).
- **Do not translate identifiers, codes, file paths, or other machine-readable content.**
- **Do not break tables.** Preserve column structure exactly; translate column headers and cell text but keep cell structure intact.
- **Do not silently localise numbers without preserving the original.** If you convert imperial → SI, include the original in a parenthetical.
## Quotation marks, dashes, typography
Match the target language's typographic conventions:
- English: `"..."` or `'...'`
- German: `„..."` (low-9 opening, high closing) or `»...«` (reversed guillemets)
- French: `«...»` (with non-breaking spaces inside)
- Spanish: `«...»` or `"..."`
- Russian / Ukrainian: `«...»` for outer, `„..."` for inner
- Chinese: `"..."` (English style) in modern usage; `「...」` for traditional
- Japanese: `「...」` for outer, `『...』` for inner
Em dash (`—`): used in most Latin-script and Cyrillic languages for parenthetical breaks. Acceptable verbatim.
En dash (`–`): used for ranges (e.g. `2020–2026`). Preserve.
## Translator notes — when and how
When you genuinely cannot resolve an ambiguity:
```
[translator note: source's "АКБ 24 В" is ambiguous between "24 V battery"
and "battery 24-volt model"; rendered as "24 V battery" per most common
usage in this glossary; please confirm.]
```
Keep notes inline in the markdown output (the build step preserves them as italic-bracketed text). Do NOT use them for fluency choices — only for genuine ambiguities, source errors, or terminology decisions that need human sign-off.
---
# Domain blocks (appended per `project.yaml` setting)
## domain: aerospace
Audience: aviation engineers, MRO technicians, certification authorities (EASA, FAA, ICAO, NATO STANAG reviewers), military operators. Document types: AFM, FOM, AMM, ICD, CDR, type-design data, safety analyses.
Tone matches FAA Advisory Circular / EASA AMC English; equivalent register in non-English target languages.
Key abbreviations always preserved untranslated: UAS, UAV, GCS, IFR, VFR, GPS, GNSS, ICAO, EASA, FAA, ATC.
Modal verbs in regulatory English: "shall" = mandatory, "should" = recommended, "may" = permitted. Preserve modal force exactly.
## domain: pharma
Audience: pharmaceutical engineers, QA reviewers, EMA/FDA reviewers, hospital pharmacists, regulatory writers. Document types: SOP, IFU (Instructions for Use), SmPC (Summary of Product Characteristics), PIL (Patient Information Leaflet), CTD modules, validation reports, batch records.
Active substances: preserve INN (International Nonproprietary Name) exactly; do not translate brand names.
Dosage forms: use the target language's standard pharmacopoeia term (tablet → comprimé → Tablette → таблетка).
ICH terminology has standard target-language renderings — consult the project glossary or ICH multilingual references.
## domain: medical-device
Audience: device engineers, notified body reviewers, hospital clinical engineers, IFU end-users. Document types: IFU, DHF (Design History File), risk management file (ISO 14971), clinical evaluation report.
MDR / IVDR terminology: preserve EU regulatory IDs verbatim; the symbolic standards (e.g. ISO 15223 symbols) are international.
ISO 13485 / ISO 14971 vocabulary: each language has an officially-translated version; use the official rendering, not a fresh translation.
## domain: legal
Audience: counsel, regulatory affairs, courts, arbitrators. Document types: contracts, statutes, regulatory submissions, court filings.
Modal verbs are the centre of meaning. "Shall" / "must" / "is required to" / "is forbidden" each have a specific target-language form that preserves enforceable obligation. Get this wrong and the document is legally different.
Defined terms (capitalised in the source) stay capitalised in the target. If the source defines "Purchaser" with a capital P, that capitalisation carries through every occurrence.
Citation forms: per the target jurisdiction's standard (Bluebook for US, OSCOLA for UK, etc.). If translating into a target jurisdiction's language, also adopt that jurisdiction's citation style for *added* glosses; original citations stay verbatim.
## domain: automotive
Audience: ECU / vehicle engineers, type-approval authorities (KBA, NHTSA, Transport Canada, etc.), Tier-1 suppliers. Document types: ISO 26262 work products, AUTOSAR specifications, type-approval dossiers, ECE-regulation compliance docs.
ASIL levels (A / B / C / D), SIL levels (1–4), DAL (A–E): preserve verbatim, never translate or substitute.
ECE regulation numbers (R-46, R-83, R-100): preserve verbatim.
ISO 26262 part numbers: preserve as `ISO 26262-3` etc.
## domain: nuclear
Audience: reactor operators, regulatory authorities (IAEA, NRC, ASN, etc.), safety analysts. Document types: Safety Analysis Reports (SAR), Technical Specifications, Operating Limits and Conditions (OLC), incident reports.
Safety classification: preserve verbatim (SC-1, SC-2, NSC; or local equivalents). Class-1E nomenclature is preserved.
IAEA terminology: use the official IAEA multilingual glossary's target-language term.
Regulatory authority names: preserve in original language with target-language gloss on first mention.
## domain: general
No domain-specific glossary seed; basic hazard mapping only. Use this for non-regulated technical documentation (user manuals, internal SOPs, training materials) where the full regulatory rigor is overkill but consistency and structural fidelity still matter.