Negative space in design is one of the most important aspects that you need to take care of. TigerBeetle talks about this explicitly in their TigerStyle document -
"The golden rule of assertions is to assert the positive space that you do expect AND to assert the negative space that you do not expect because where data moves across the valid/invalid boundary between these spaces is where interesting bugs are often found. This is also why tests must test exhaustively, not only with valid data but also with invalid data, and as valid data becomes invalid."
This focus on negative space also resonates with the Design By Contract paradigm first coined by Bertrand Meyer in connection with the design of the Eiffel programming language.
Similar thoughts are also expressed in Floyd-Hoare logic, with a set of logical rules for reasoning rigorously about the correctness of computer programs. The idea is to assert negative paths equally exhaustively as the positive ones.
And the most important part of using this assertion based programming is to have them in the production code as well.
this is like the very fancy version of my argument that negative space in system design, combined with constraints, are what leads to the most beautiful designs
so I thought it was cool that mathematicians obviously have this very notion but abstracted and generalized