@tristanC Oh, that’s cool! I’ve not played with effects in Haskell, and this is definitely part of the picture, especially if you wanted to let multiple editors swap in their own implementations of the same feedback features The more ambitious part: how do I split the type system into two “levels”? A Tidal function doesn’t care if the pattern it consumes has editor highlights, and it would be nice to not be carrying around effect monads everywhere. However, there is a meta level where a function might want to know what highlights its dependencies trigger, so then it could opt into the live feedback effect system? This is all very speculative, and I think might require some custom type system logic