Make explicit that the CLC votes on implementation not design.

Author: AndreasPK

PROPOSALS.md

@@ -120,7 +120,7 @@ The following is a step by step guide for common proposals:
 If your proposal is a "multi-phase proposal" with multiple implementation and deprecation steps, make sure to
 precisely define when each step is supposed to take place.
 
-### A note on stale proposals
+### Stale proposals
 
 The CLC can revoke its approval for a proposal if an **"activity"** has been overdue for over a year. The revocation request, which
 explains what has changed with the passage of time to justify the review, can be initiated by the chair. If no CLC member vetos
@@ -131,6 +131,15 @@ the request, then it automatically passes.
 - for a simple proposal: whether it has been merged
 - for a multi-phase proposal: whether the next step has been carried out as planned
 
+### `base`: Bug fixes
+
+The CLC votes on concrete changes to `base` and not designs. If a change to `base`
+has been accepted but is later found to be faulty in implementation or design
+fixing it will require its own CLC proposal.
+
+Similarly fixes to existing bugs, no matter how trivial, will require
+a CLC proposal. This reduces the risk of bug fixes having unintended consequences.
+
 ## The "when"
 
 If you've got a pet issue that's been sleeping in the depths of a mailing list

README.md

@@ -41,7 +41,9 @@ core-libraries-committee at haskell dot org
 ## `base` package
 
 The primary responsibility of CLC is to manage API changes of `base` package. The ownership of `base` belongs to GHC developers, and they can maintain it freely without CLC involvement as long as changes are invisible to clients. Changes which affect performance or laziness and similar are deemed visible. Documentation changes normally fall under GHC developers purview, except significant ones (e. g., adding or changing type class laws).
+
 Proposals to change the API of the `base` package are managed by the process, described in [`PROPOSALS.md`][proposals].
+Note that while proposals can be helpful in the design phase the CLC will only vote on concrete *implementations*.
 
 [proposals]: https://github.com/haskell/core-libraries-committee/blob/main/PROPOSALS.md