Uncontrolled is the evil dual of Methodology. Where a `Methodology b c` represents a way to turn b into c in a controlled decomposition, Uncontrolled represents a purely unknown side effect - that materialises bs out of nowhere, and sends cs into the void where we have no knowledge of what happens to them. This is equivalent to the combination of Input and Output considered as a single unit.

This exists for symmetry with Methodology and out of curiosity, but should be considered extremely dangerous. Uncontrolled can only ever be reinterpreted as an equally or more severe side effect than the context in which it's introduced. For experimentation though, this module might be fun to see how much evil you can get away with.

There is a simple interpretation in the form of runUncontrolledAsState, as well as ways of getting between Uncontrolled and Input/Output. Combined with teeMethodology and plugMethodology, this may give you a way to teleport state around your architecture.