Treat local promotions and pricing as localized signals that surface in the spoke outputs while the hub facts remain the canonical source. Local content should reference hub fact_ids and proofs via language-aware identifiers, but updates to core facts must go through Change Control and be versioned in the Public Business Brain. Use a local Change Log to document deviations and ensure cross-brand mappings point back to the hub’s canonical content. This preserves global consistency for AI-facing outputs while allowing local relevance in regional conversations.
Own The Conversation Digital Twin · Public Q&A
How should a hub-and-spoke Digital Twin handle local promotions and pricing, to avoid conflicting with hub facts?
Explore related questions
If this answer raises another question, follow the topic and related answers below or contact Own The Conversation for a business-specific discussion.
Related Topics
