Two departments independently redefine the shared entity Citizen differently in local models. What lightweight governance practice should prevent semantic forks?
Select an answer to reveal the explanation.
Short Explanation
When two teams redefine Citizen on their own, you get two cities that do not match on the map. A lightweight model review board for shared entities keeps the enterprise meaning from forking. Local experiments can continue, but the shared term gets a checkpoint.
Full Explanation
Enterprise-shared entities require modeling governance so local designs do not fork semantics used across systems. A model review board provides a lightweight checkpoint for changes that affect shared meaning, ownership, and downstream consumers. Banning modeling entirely or allowing unreviewed conflicting definitions both damage interoperability. Spreadsheet renaming without shared-entity review likewise fails to protect enterprise semantics.