> Herb has advised that my first step should be to write a proposal.
I think that's the wrong first step. Please don't write a paper yet; participate first.
I would instead recommend you start attending C++ committee meetings (in this, specifically, Library Evolution) not as a proposal author, but as a participant and reviewer. That will help you learn about our process and the constraints we have to work with.
Proposal authors who do not take the time to first participate in the committee are often disappointed, because they have expectations that do not align with the rest of the group.
> I also do not trust the current library and language evolution committees to be competent or even willing to learn about understanding why having basic human-interface tooling available by default is crucial for the long-term evolution of such a language (note that such competency is nécessary to achieve the goals set by the committee itself, so in my eyes it's all contradictory behavior).
I think it's hard to pass judgement on the library and language evolution committee without first participating in these groups. I'd encourage you both to do so.