uncertainty is like a liquid flowing. think of it like water. water goes where it can, responding fluidly to forces. the movement of clean water is a clean/lossless reflection of the forces on it. clean uncertainty is the same way. (dirty water is clean water plus some stuff; dirty uncertainty is clean uncertainty plus some stuff; doesn't make the problem intractable, just means you might need to add dimensions to the way you're locating _the thing_.)
routing [ water / uncertainty ] can be arranged to powerful ends
but if your structure naturally leaks (and by that I mean if your structure isn't self-sealing over time) the [ water / uncertainty ] will erode the system and it'll become something else, something that serves the outer scope of force passage, obliterating what you were up to with your constructed inner scope of force passage
this is an amazing feature :D suggests a whole range of things to do with [ water / uncertainty ]: suffusion, reflection, _freezing and thawing_, the whole ecological [ water / uncertainty ] cycle honestly
(careful with how you map the "freezing" metaphor: frozen water is a reflection of what the water was experiencing when it fell below its own minimum energy threshold for continued evaluation of forces. freezing uncertainty is like that, too: when observation is withdrawn, the force map in situ is persisted in ways other than movement.)
take-home: this suggests that _individual_ discomfort might be force scopes jostling, and that you might stabilize your own position by recognizing [ water / uncertainty ] leaks around you and responding to them in ways that do *not* leak
(title is a joke based on the fact that the codebase for which this was written always interprets hyphens in filenames as spaces in the content's natural title. "leak proof", like proving a system based on how it leaks, "proving" in a Curry-Howard kind of way.)