Interesting. That changes things then…
Would the same be the case for doing some bit-ty fluid.bufcompose~ or peek~-ing rather than fluid.bufflatten~ at the end of each individual descriptor processing chain to get only the bits you want into the fluid.dataset~?
Like, if you specifically wanted mean/std/min/max of the stats and their derivs, for example.
This would make something like what I suggest here (@output attributes) even more compelling so you can get only the things you want up front, rather than getting what you don’t, and having to carefully sift/prune around it.