What you describe sounds like more of a data modeling/integrity concern than a data consistency concern. A better example of a data consistency requirement is

What you describe sounds like more of a data modeling/integrity concern than a data consistency concern. A better example of a data consistency requirement is a SINGLE record that should be the same when 200 different users read it at the same time, e.g. the current price of a stock. I'd prefer that a user not be able to see a stock's price at all rather than show them the wrong price. Contrast this with a record that does not need to be the same for all users at the same time, such as a list of users that liked a blog post. Given the choice, I'd prefer that my post is available for anyone that wants to read it rather than sacrificing availability to ensure that the list of users that liked the post is totally up-to-date.