To add some context: I’m specifically thinking about cases where each individual state update looks valid on its own, but the combination over time breaks a bus

To add some context: I’m specifically thinking about cases where each individual state update looks valid on its own, but the combination over time breaks a business rule. For example, async flows where status updates and data creation are handled in different places. Curious how teams make these kinds of assumptions explicit in practice.