Evaluator Optimizer

One model call writes an output. A second model call, which has not seen how the first one worked, scores that output against a written list of criteria and says what to fix. The first call then writes again, and the cycle repeats until the output passes, a limit on rounds is reached, or a fallback takes over (the evaluator optimizer pattern). The writing role is the generator, and the scoring role is the evaluator.