--- accp: <to be assigned> title: <ACCP title> author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <email@example.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)> discussions-to: <Link to github issue on https://github.com/ampleforth/AIPs/issues> status: WIP created: <date created on, in ISO 8601 (yyyy-mm-dd) format> requires (*optional): <AIP/ACCP number(s)> ---
This is the template for ACCPs.
Note that an ACCP number will be assigned by an editor. When opening a pull request to submit your ACCP, please use an abbreviated title in the filename,
The title should be 44 characters or less.
If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of the ACCP.
A short (~200 word) description of the variable change proposed.
The motivation is critical for ACCPs that want to update variables within Ampleforth. It should clearly explain why the existing variable is not incentive aligned. ACCP submissions without sufficient motivation may be rejected outright.
Copyright and related rights waived via CC0.