Okey, went through temporal.io and prompted how could it be implemented into our workflow It actually can replace the semaphores, checkpointing, cancellation and even add crash recovery (since it's for free, why not).
But I don't understand what makes it a state machine. Temporal sounds like durable execution enabler. It is better fit to sit on top of our state machine.
Good point. It's flaky, because the orchestration is fully Opus driven. It has tools, skills, multiple turns. I was inspired inspired by the OpenClaw system. The UX should improve the most by tuning the internal `.md`s, but I'm also thinking about adding stricter workflow for each type of physical product like https://github.com/obra/superpowers does. Toys, enclosures, statues, servo robots, all need different amount of user feedback and artifact refinement.
Yeah, ordering actually works, we just had the first order :)
But I don't understand what makes it a state machine. Temporal sounds like durable execution enabler. It is better fit to sit on top of our state machine.