Summary: Delta-Aware (Incremental) Translation to Preserve Manual Edits and Optimize AI Credit Usage.

The Problem / Challenge: Currently, when a page or block is updated in the master language (e.g., English) and auto-translated, the translation engine (both Opal and the CMS Languages gadget) retranslates the entire page.

This presents several significant issues for enterprise organizations managing many languages (such as the 13-language setup we have):

• Wasted AI Credits: If an editor makes a minor change (e.g., fixing a typo or changing a single sentence), we are forced to pay the credit cost to translate the entire page again across all 13 languages.

• Loss of Manual Adjustments: If local market editors or professional translators have manually refined, polished, or culturally adapted certain sections of the translated page, a full retranslation completely overwrites and wipes out those human refinements.

• Translation Drift: Because LLMs are non-deterministic, retranslating unchanged sentences can introduce slight variations in wording, breaking established brand consistency across the site.

Potential Solution: We'd like to request the introduction of a Delta-Aware (Incremental) Translation Mode within Opal and the CMS translation workflows.

When a page is submitted for retranslation, the system should:

1. Compare Version History: Automatically compare the current version of the master language (English) page with the previous version to identify only the specific blocks, sentences, or fields that have changed (the "delta").

2. Translate Only the Delta: Send only the changed text blocks to Opal's Content Translation engine, dramatically reducing credit usage.

3. Surgically Patch Target Pages: Merge the newly translated changes directly into the existing target language versions (e.g., Spanish, Vietnamese, etc.) while leaving unchanged, previously translated, and manually edited blocks completely untouched.

Business Value & ROI

• Cost Efficiency: Reduces AI credit consumption by up to 80-90% for ongoing content maintenance.

• Content Quality & Safeguards: Protects valuable manual localization efforts from being lost during automated updates.

• Operational Velocity: Allows teams to safely automate translation pipelines (like a daily schedule) without fearing that automated runs will ruin hand-polished translations.