That’s a good point. We’ve been using the UML diagrams as a tool to catch behavioral red flags, but the reuse and implementation details of that are left undefined.

Maybe the answer lies in also explicitly spending a few passes focusing on code health, explainability, maintainability. This is something I go through at end and then retry verification tests, but not something we explicitly require in our process at the moment.