turned into upstream patches. When you're deep enough in a feature
Is covered by the same lookup rules as:
，更多细节参见新收录的资料
Mog is a statically typed, compiled, embedded language (think statically typed Lua) designed to be written by LLMs – the full spec fits in 3200 tokens.
There’s a part of this I haven’t seen anyone say out loud. When the person opening the PR gets credit for shipping and the reviewer bears the consequences of reviewing a bad merge, you have a structural problem no tool can solve. That incentive gap widens when the contributor isn’t an engineer building context over time. A PM using an AI coding tool isn’t on a path to owning the service. Unlike a junior engineer who gradually needs less oversight, they’ll need review for every change they make, indefinitely, because they’re not building the kind of context that earns independence. So that review load doesn’t taper but remains a permanent line item, and most teams aren’t planning for it that way.