I mean, I think that I get what you're saying. And part of me is like, yeah, the thing I suggested where you have like this gate for at least the Go team where they say, here's the gate of when it's that. But I also think that that's a line that you cannot define, right? It's not a definable line to say, oh, this thing has moved from discussion to something we're going to implement. It's an emergent property of the discussion. Oh, okay. It seems like we're all in consensus here. Let's move on to just, let's move on to the implementation. Then someone pops up, hey, what about this? And then it shows back to conversation, right? It's a fluid back and forth thing. It's not what is traditionally thought of as waterfall, right? It's not like a once you get through the gate, you're good. It's like sometimes things are going to go back and something's going to go forward. Sometimes this one proposal that we're like, we're definitely going to accept it gets affected by a proposal that already got accepted and implemented. Now we got to go rethink this one, right? This is a very dynamic and fluid process. I think any attempt to like shut it down in a way or to draw a line somewhere, it's just not going to work. It's like when people say, oh, we have a dictionary that defines words, thinking that the word, the definition in the dictionary is the correct one. It's like, no, the definition in the dictionary is the emergent one. We all define words simply by using them. That's how language works. And similarly with these discussions and things we want to implement, we won't know the point at which something is ready to be implemented until we've had the conversation and figured out that we have talked about enough, this enough to implement it. And there's someone that's going to go implement it. Like, that's the gate. That's the thing at the end of the day. If the Go team wants to have a special gate there or a special quality level before they'll even look at something, that's fine. Maybe they use LLMs for that, right? To have a little bot be like, does this have enough stuff in it for us for us to use our very, very little or really resource-constrained team on? Like, is this worth it yet? That's fine. But there also might be someone else that just goes and says, I want to implement the same gets a patch and then also provides it to the Go team, right? This is the thing with the decentralized community that we have is that we just had to accept the fact that I don't think we can, we can't, we can't centralize this. We can't make this an authoritarian or oligarchic system. Yeah,