Where should design and process proposals live?

I have written a proposal for a merge queue and found there is nowhere to put it. We have two places today, and neither fits. `doc/designs` in the main repository is for library designs, per the design process policy. The policy repositories are for policies, with their own change process. A proposal about infrastructure, tooling or process has no home, no template, no status, and no way to be found later. So the merge queue proposal is a markdown file I am passing around by hand. That is the problem, in one sentence.

Suggestion: an `openssl/proposals` repository. One markdown file per proposal. The pull request is the discussion, so comments attach to specific lines and revisions show what changed after feedback. Status in the header: draft, accepted, rejected, withdrawn, implemented. Merging records a proposal; it does not mean acceptance, so rejected ones stay findable with their reasoning. Rendered to openssl-library.org the same way the policy repositories already are.

Why not the alternatives: Google Docs loses comments against versions and engineers avoid it. A wiki has no review step. Loomio is good for the discussion and the decision, but a thread is a poor home for a document that gets revised.

Two things to note. The design process policy still refers to the OTC, which no longer exists, so it needs an update anyway. And whatever we decide, the merge queue proposal needs somewhere to live now. Does this seem worth setting up, and who would own it?