The highest level discussions may surface ideas in many places including (but not limited to) the #governance channel on discord, AmplTalk Forum, social media, or community DAOs. When it appears that there is enough general support, a champion may formalize the idea by submitting an Ampleforth Improvement Proposal (AIP) or Configuration Change Proposal (ACCP).
Proposals (AIPs / ACCPs)
AIPs and ACCPs are formal documents that describe the proposed change to the protocol or protocol configuration. https://aips.ampleforth.org/.
Each proposal has a dedicated github issue where outcome-driven discussion takes place. The goal at this step is to finalize any unresolved issues and formalize offchain consensus. https://github.com/ampleforth/AIPs/issues.
If the previous step did not arrive at obvious consensus, sentiment may be gathered in a non-binding way via onchain signaling from token holders. This provides more insight into the likelihood of the outcome of the final binding vote. https://snapshot.page/#/ampleforth.
Requirements are implemented in code, launched on testnet, and audited for security.
Binding Vote / Deployment (work in progress)
System changes are currently controlled by a multisig contract. This will eventually be replaced by generalized voting from token holders.