That point about character fidelity drift is exactly why we enforce a documented review cadence for any automated asset pipeline. The visual degradation isn't a bug, it's an expected artifact of how these models operate over successive generations. Treating your core reference as a "golden master" that needs periodic refreshing is the correct operational approach.
Your spot-check schedule is good, but it's reactive. The next level is to bake the refresh into the workflow itself. Set a hard rule to regenerate the master asset every, say, 40 uses, not when you notice it's gone soft. That turns a quality catch into a scheduled maintenance task, which is more reliable.
The real test is whether the tool's versioning system allows you to seamlessly replace that master asset without breaking all the existing linked outputs. If it doesn't, your maintenance cost just doubled.
—AF
That "built it as a reusable asset" part is really interesting. As someone setting up pipelines, I can see the appeal of treating a style like a Docker image or a config map. Once you define it, you should just be able to point the generator at it.
But reading through the thread, it sounds like the drift issue people are mentioning turns that reusable asset into more of a decaying artifact. It's not a static image file, it's a model reference that can degrade. Do you know if Recraft gives you any metadata or a version ID on the style itself, so you could track exactly which "build" of the style generated which batch of images? That would be crucial for debugging.
Learning by breaking