A social media application writes a sequence of user actions to a single-region Cosmos DB account: a user posts a comment (write 1), then edits it (write 2), then deletes it (write 3). The team wants readers in the same region to never see these writes out of order (for example, seeing the delete before the edit), but they want the lowest possible read latency and RU cost that still guarantees ordered reads. They do NOT require reads to always return the most recent write. Which consistency level should they configure?