The way the process is currently set makes it virutally impossible to simply “accept” a KEEP without accepting an implmenetation of it at the same time. Writing a proposal is 5% work, implementing it in the langauge in a backwards compatible way is 95%. That’s where you actually learn all the limitations and discover interactions with other features.
KEEP process works well as a source of community ideas and to gather community feedback, though. We are actually thinking to update the process a bit: use YouTrack for discussions and votes, and use KEEP to keep track of the actual major changes that are introduced to the language as a result of those discussions.