localise

name: localise description: Produce an MA-facing deliverable in a target language (Romanian, French, Spanish, or Russian) to IPPF rigour, with English as the canonical source. Use when Ane asks to "localise", "translate this brief", "in Romanian/French/Spanish/Russian", "Romanian version", "produce a French companion", or "review my Spanish draft". Applies a curated SRHR glossary (controlled terminology), preserves the Tier 1 working-brief register, makes safeguarding-aware term choices, runs back-translation QA, and flags for native review. Never authors from scratch in the target language. Does not design instruments or audit English voice (use ane-voice for English).

English is the canonical source. The target-language deliverable is derived and review-flagged. This skill produces a target-language version of a finished English deliverable, a target-language companion, or a review of your own target-language draft. It does not author from scratch in the target language.

Supported languages: Romanian (ro, fully curated), French (fr), Spanish (es), Russian (ru). French, Spanish, and Russian are working-draft glossaries refined at use. Adding a further language is a new glossary file.

When to use

Trigger for: localising a finished English brief; producing a target-language companion to an English deliverable; reviewing a target-language draft you wrote. Do not trigger for English voice work (use ane-voice) or instrument design (use instrument-designer).

Modes (detected from input)

Localise a finished doc then you provide an English deliverable (paste or path) and get a target-language version plus a QA note.
English plus companion then Vi or you provide the finished English deliverable and get a target-language companion alongside it.
Review my draft then you provide your target-language draft (plus the English source if available) and corrections are walked one by one, never a silent rewrite.

Image-based deck exports (Storyline / PowerPoint exported to Word). When a mode-3 review target is a slide-deck or e-learning export (e.g. Articulate Storyline .docx/PPT export), the translatable text is rasterized inside the slide images, not live in the document body. The only live text is slide titles and layer labels. Three consequences: (a) read the slide images to review the translation, not the body text; (b) a Word comment cannot sit on text inside an image, so anchor each comment to that slide's title paragraph and have the comment name the slide and give the EN→FR correction; (c) corrections are made in the source deck and re-exported, so also deliver a slide-keyed branded corrections sheet (Slide · EN page · Type · EN source · Current FR · Proposed FR · Why · Severity) as the actionable worklist. python-docx 1.2.0 add_comment(runs, …) preserves the export's unusual package; verify no parts are dropped on save and write to a copy, never the original.

Required inputs

The English source (or, for mode 3, the target-language draft plus the English source). Required.
Target language: Romanian, French, Spanish, or Russian (Romanian is the most curated; the others are working drafts).
Audience and member-association context (shapes register and cultural adaptation).
Restrictive-context flag (triggers the safeguarding pass on sensitive terms). Mandatory for Russian-language output (see the legal-review banner in the Russian glossary).

Method

Read the target-language glossary mel_wiki/wiki/glossaries/srhr-terminology-<lang>.md, substituting the target-language code (ro, fr, es, ru). For Russian, read the legal-review banner at the top first.
Translate and adapt. Apply controlled terms; preserve BLUF, plain language, collaborative voice, numbered steps; adapt examples to the member-association context.
Terminology-compliance check. Confirm every glossary English term in the source uses the controlled target-language rendering.
Back-translation QA. Back-translate key passages to English; diff against the source; flag meaning drift.
Safeguarding pass. List every sensitive-flagged rendering used; in a restrictive context, surface the term choice for confirmation and route it to safeguarding-reviewer (mandatory for the legally-exposed Russian terms: LGBTI+, gender identity, sexual orientation, CSE, reproductive rights).
Output. IPPF-branded Word via ane_package.reporting.word_export with the document language set via the lang parameter (ro/fr/es/ru); plus the QA note.

Output structure

The target-language deliverable.
Terminology-compliance note.
Back-translation QA note (meaning-drift flags).
Sensitive-term list and the choices made.
Native-review stamp ("native review recommended" / "validated by author").
Data gaps.

Citation requirements

ITC (2017) ITC Guidelines for Translating and Adapting Tests 2nd ed; Brislin (1970) back-translation (canonical); WHO process of translation and adaptation. Controlled terms cite their glossary source.

Writing rules

Follow CLAUDE.md house style for the English QA notes. The target-language prose follows the equivalent Tier 1 register in that language. Default register is Tier 1 working brief unless Ane names publication.

Limitations

Produces a draft for native review where the author cannot validate the output. Does not replace native-speaker sign-off for languages the author does not read. Romanian is the most curated glossary; French, Spanish, and Russian are working drafts whose unsourced and competing-rendering terms are refined at first use. Russian carries restrictive-context legal-exposure flags — never distribute Russian-language SRHR material inside Russia without legal review and safeguarding-reviewer sign-off.

Edit-preservation protocol

In mode 3, and any time Ane references an existing file by path, read the file first, edit scope-bounded via the Edit tool, preserve out-of-scope content byte-identical, and return the EDIT-PRESERVATION DELIVERY summary.

Apply mel_wiki/wiki/concepts/edit-preservation-protocol.md when target file exists.