## 3. stricter is better The Rust code review stage surfaced an issue: the app could get stuck if things happened in a specific unlucky way. State appears indeterminate but most likely fine, and it's correct to proceed. But in the meantime, state gets updated outside of our system (i.e., we read the internet). Broadly, this is a "race" and it's standard practice to deal with race conditions by applying "locks". The architecture did this, but its specific implementation was soggy. The Typescript side had passed code review, because it was looser and the implementation looked plausible. It's like asking, *if a Scot and an Irish person have a sprog, will they be ginger?* You can answer this with some probability, and make your decisions accordingly. *But if you ask the question as, if ginger Scots and ginger Irish mate, how ginger will the population be, you can see the segmentation of outcomes more easily, and assign more precise probabilities to each combination.*