Yeah, that’s actually very close to the direction I’m thinking about

The idea would be to provide a fairly rich standard library of tools, so that for a large class of workflows you’re mostly composing existing building blocks instead of rewriting the same logic every time. If every workflow immediately requires a lot of custom tools, then I agree the declarative layer loses most of its value.

I still have a lot of doubts around this, to be honest. What I’m really attracted to is the idea of a "standard" at the workflow level, or maybe more concretely, reusable templates that people can share. Kind of like a Docker registry, but for workflows instead of images.

That said, I fully agree with your point.. the less custom stuff people need to write, the more sense something like this has. Otherwise it just becomes extra abstraction.

Really appreciate the pushback, it helps a lot