Finding it hard to separate all the distinct, but highly overlapping types of transformations of byteco, especially around rendering a macro.

---

I took a step back and thought about these byteco transformations as pure functions. Instead of adding lots of context around exports, renders, etc, I can think of each specific type of transformation as a function that takes in arbitrary byteco/stream and spits out modified byteco. Some transformations can filter from sourceco to byteco, some take an input and spit out a routine symbol, and some spit out an assembly rom.