[dkersten]

I’m building something similar. It’s not public yet because it’s still early and I’m still working on exactly what it is supposed to be.

But the idea is similar in that I start with a spec and feed the LLM context that is a projection of the code and spec, rather than a conversation. The context is specific to the specific workflow stage (eg planning needs different context to implementing) and it doesn’t accumulate and grow (at least, the growth is limited and based on the tool call loop, not on the entire process).

My main goals are more focused context, no drift due to accumulated context, and code-driven workflows (the LLM doesn’t control the RPI workflow, my code does).

It’s built as a workflow engine so that it’s easy for me to experiment with and iterate on ideas.

I like your idea of using TOML as the artifact that flow between workflow stages, I will see if that’s something that might be useful for me too!

[beshrkayali]

Very much the same thinking. Ossature already structures work that way at the plan level during audit, so curious to see where you take it. Happy to share more about the TOML approach if useful. Feel free to reach out (me at my domain)