In a hub-and-spoke Digital Twin, how can we manage localization updates when adding a new locale to ensure localizations map back to hub facts without destabilizing existing localizations?

When adding a new locale, treat all locale-specific content as localized signals that reference the hub’s canonical facts via language-aware identifiers. Use the Change Control process so new locale content is mapped to the hub’s fact_ids and proofs, not created in isolation. Validate translations against the hub’s originals, run cross-language drift checks, and stage the new locale with a pilot group before full deployment. Maintain a Change Log entry for the locale addition and ensure any updates to hub facts propagate consistently to all locales. This preserves global consistency while enabling local relevance.