In a traditional SDLC, validation was someone else's job and it came later. QA teams checked that the software did what it was supposed to. The behavior was repeatable, so eventually you automated the checks and moved on. So when building Slooster, I did the hard parts first: Building the prompts, tuning them, defining schemas for parameters and outputs. Building a system to pick the provider, the model, the temperature, and other tuning configs per prompt. Everything worked great...