The guide leads me to believe that’s not how it is supposed to work, left hand side writes/ filters, right hand side reads the end result.
But with User Text, the Key/ Value output is an intermediary step: it doesn’t read the actual attributes of the content. Rather, it shows how the attributes were modified.
It’s like the move component’s transform output in that sense rather than the transformed geometry output. And when you need more of the same components to read the key/value pairs you are after, this quickly becomes confusing.
