bmad-os-editorial-review-translation

To detect content injections in translated documentation, perform a structural and semantic fidelity audit comparing target files against the English source. This process identifies off-topic additions, hidden messaging, and unauthorized links introduced during localization.

Translation fidelity auditing verifies that localized content maintains the original intent and structure of the source material. It utilizes back-translation and structural mapping to compare translated files against English sources, detecting meaning drift and omissions.

Validating structural consistency involves mapping translated documentation against English source files to ensure headings, frontmatter, and links remain intact. This structural comparison catches unauthorized modifications and formatting drift in localization workflows.

Yes, you can review a pull request for a new language localization by running an editorial audit on the translated files. It compares the changes against the original English documentation directory to ensure faithfulness and prevent external agendas.

The best way to prevent meaning drift in localization workflows is to perform a semantic fidelity audit using back-translation. This rigorously compares translated documentation against the original English source to verify integrity and identify unauthorized content.

Translated files contain off-topic additions or unauthorized links when external agendas are introduced during localization. Running a structural and semantic fidelity audit detects these injected messages by verifying translated content against the original English source material.