Translate reports section-by-section

Phase-4 feasibility reports are written for whoever needs to read them — a Task Team Leader in Washington, a forestry-agency district officer in Andijan, a community cooperative in Tashkent province. We translate at the report level, not on-the-fly with browser tooling, so the translated copy is a real artefact: archivable, shareable, exportable to PDF.

How to translate

1. Open any finalized report. Drafts cannot be translated; the "Translate" button only appears once Opus 4.7 has streamed all nine sections.
2. Pick a target language from the language pill row at the top of the report (EN · TR · RU · UZ).
3. Watch the progress bar. The P3 Report Translator agent walks the source sections in parallel, four at a time, and a sibling report is created in the target language as soon as the first sections land.

Sibling reports, not in-place edits

Each translation is a separate row in reports_cache, linked back to the source via analysis_group_id. That means:

• The original is preserved. You can always swap back to EN without re-running anything.
• You can compare side-by-side. Open the report in two tabs and pick different languages.
• Citations stay numerically aligned. Citation [3] in the EN version points to the same WB Phase-4 paragraph as citation [3] in the RU version.

Why Sonnet 4.6, not Opus

Opus 4.7 over-thinks translation prose — it adds nuance the original didn't have. Sonnet 4.6 is faster, faithful, and roughly 1/4 the cost. Domain terms (cadastral, viloyat, tuman, NDVI, MRV) are pinned via a glossary so they translate consistently across sections.

Caveats

• Closing the tab cancels the run in the current build. We have an RQ-backed background queue designed; closing-safe translation ships in Q2 2026.
• Auto-translation is labelled. Every translated report carries a "Machine translation — review before signing off" banner so nobody mistakes it for human-revised copy.