Comment by jasendo

We've been working on a similar problem, but went the route of pushing this into the model and runtime layer instead of the orchestration layer. Less scaffolding, more baked into how the model reasons. Happy to share more if useful