Catalog entry schema, confidence scores, and the no-auto-push rule

place for all uh catalog all patterns and anti-patterns to be noted. And what would an entry in that catalog look like? Uh the example is right here. Uh as the left-hand side it mentions the uh small hints that an LLM uh coding agent in the future could use to easily query that uh catalog. It can mention a list of symbols, uh the services where it was confirmed. Some confidence level is great here as well because as more and more services confirm this, you want to keep updating this so that uh the future agents get more and more confident that, "Okay, this is worth a human uh uh human review, and I would want to more confidently send out a code review to a human." Uh I'm still keeping the confidence uh bar to just send a code review and not directly uh push it to production. That's by intent. I uh I'll talk a little bit on why, but I do feel like there is still need for a human approval because you're modifying an existing code that is running just fine in in production in order to optimize it, which is which is very risky. If you don't know the business context, if you don't have enough test coverage, uh you might end up breaking. So, there is a need for human uh to actually be the one responsible for approving that code review.