Yes. I am saying that there’s no clarity in what is “GRIP work” and what is simply community debate (@shane 's hours, for instance), and that the structure of GRIP time was based on the points I outlined in my previous comment, not in typical community debate. The purpose of that category was the things outlined above, both with GRIP work and with community feedback on viability, feasibility, and to highlight points which may have been missed in the proposal.
I left that original comment in response to @Dermot’s comment:
…which is exactly the concern here, that the waters are exceedingly muddy as to what is GRIP work in the preproposal category, what is not, and that debates are occurring in this category before a proposal is actually “ready”, which was the entire purpose of the category to begin with, to get proposals “ready” for debate.
I lobbied strongly in favor of the original proposal, because I expected the GRIP team to be doing the things I previously outlined: assisting with supporting graphics, helping identify technical challenges and feasibility issues, etc. You yourself said many times that changing the proposal mid debate made it challenging for people to understand the current state of the proposal, but now that debates have essentially moved into the preproposal category, we’re seeing the exact same thing. Moving the location of the debate doesn’t solve the core issue, and I don’t see GRIP work clearly being done as most of the comments in the preproposals are full on debate versus clarification or feasibility analysis.
The lack of clarity around what is GRIP and what is not (and to be frank, the amount of time billed for GRIP which is meetings or typo editing versus actual work which streamlines the proposal process) make me question the value being returned. I don’t know what guardrails need to be put in place to resolve this, but I’m finding it difficult to support in its current form.