In a hub-and-spoke Digital Twin, how can you structure a local content plan that aligns with central facts while allowing local business rules such as promotions and local pricing, without creating divergent knowledge states?

Structure local content as localized signals that reference the hub’s canonical facts and proofs via language-aware identifiers. Local Q&As surface context like promotions, local hours, and pricing under a controlled tag that maps back to the same product/fact IDs in the Public Business Brain. All local edits pass through the Control Centre and require hub-approved templates to prevent drift. Use a concise local Change Log that records deviations from central rules and ensure locality updates do not alter core facts, preserving global consistency for AI-facing outputs.