Create Executive vote - November 14, 2024.md

[CivicSage3]

I've made the first run through the document as well and left some suggestions. I'll check it again in a few hours. On the other hand, we might need to wait until tomorrow with final review, if Rema decides to provide the rate changes for this spell.

[0xldr]

Executive Creation

Creation

• [x] Sync Community Git

• [x] Ensure you are working from the latest master branch

• [x] Read Associated Executive Contents sheet

• [x] Copy the executive template

• [x] Update filename

• [x] Update dates - exact time is not required and should be left at midnight.

• [x] Ensure the title refers to the most impactful/important actions included in the proposal.

• [x] Ensure that the summary refers to all actions included in the proposal.

• [x] Ensure that the publisher (entity publishing the executive on the voting portal) of the executive is listed in the preamble (at the entity level).

• [x] Ensure that the writers of the executive code are listed in the preamble (at the entity level).

• [x] Ensure that the reviewers of the executive code are listed in the preamble (at the entity level).

• [x] Ensure that the office-hours modifier is mentioned as part of the executive copy, if present in the executive spell code.

• [x] Ensure that it is clearly stated which items are affected by the GSM Delay.

• [x] Ensure that the GSM Delay period is clearly communicated.

• [x] Ensure that the proposal expiry is explicitly noted, including the length of time for which the proposal is valid.

Items

• [x] Add each item to the proposal details section

• [x] Order the items by judged impact/importance. If different from the executive contents, reorder the executive contents sheet so that they match.

• [x] For each item

  • [x] Ensure the executive summary contains a high-level overview of every action contained in the proposal.
  • [x] Ensure that each item or set of items in the executive proposal has a corresponding entry in the proposal details section.
  • [x] Ensure that each item in the copy contains a link to the reasoning for its inclusion.
  • [x] Ensure that each item in the copy contains a link to the authorization for its inclusion.
  • [x] Ensure that each item in the copy contains any links required for voters to determine the context surrounding its inclusion.
  • [x] Ensure that the framing and tense used for each item is future-conditional. Ie: "IF this executive proposal passes, THEN this action will take place."
  • [x] Ensure that hyperlinks to documentation and/or context are added to key parameters, terms, and contracts where reasonable and possible.
  • [x] Ensure that Ethereum and IPFS addresses are hyperlinked such that it is easy to view their details.
  • [x] Ensure that parties implicated in the proposal outcome related to this item are aware of the wording used.

Self-Review

• [x] Do any '$' parameter signifiers remain? (spell address is unknown at this point)
• [x] Do the executive title, summary, and executive summary accurately reflect executive copy content?
• [x] Read the executive copy in full, with the above checklists and general readability in mind. Make any required changes.
• [x] Run the copy through a spelling and grammar checker - do not blindly accept suggested changes.
• [x] Inform the reviewer that the executive copy is ready to review
• [x] Commit changes, and create a PR to the Community GitHub repository.

Submission

• [x] Merge approved executive copy PR.
• [x] Inform technical teams that the copy is ready and provide the link.
• [x] Once technical teams have provided a spell address, add it to the executive copy.
• [x] Update the proposals.json to set the active proposal on the portal.
• [x] Refresh portal cache (DUX/Jetstream can provide password)
• [x] Inform the community of the new executive proposal.

[CivicSage3]

Just one typo corrected. The rest is good to go!

Executive Document Review

Content

• [x] Check the title refers to the most impactful/important actions included in the proposal.
• [x] Check that the summary refers to all actions included in the proposal.
• [x] Check that the publisher (entity publishing the executive on the voting portal) of the executive is listed in the preamble (at the entity level).
• [x] Check that the writers of the executive code are listed in the preamble (at the entity level).
• [x] Check that the reviewers of the executive code are listed in the preamble (at the entity level).
• [x] Check that the office-hours modifier is mentioned as part of the executive copy, if present in the executive spell code.
• [x] Check that it is clearly stated which items are affected by the GSM Delay.
• [x] Check that the GSM Delay period is communicated.
• [x] Check that the proposal expiry is explicitly noted, including the length of time for which the proposal is valid.

Items

• [x] Check each item is present in the proposal details section

• [x] Check items are ordered by judged impact/importance

• [x] For each item

  • [x] Check the executive summary contains a high-level overview of the item.
  • [x] Check that each item or set of items in the executive proposal has a corresponding entry in the proposal details section.
  • [x] Check that the copy contains a link to the reasoning for its inclusion.
  • [x] Check that the copy contains a link to the authorization for its inclusion.
  • [x] Check that the copy contains any links required for voters to determine the context surrounding its inclusion.
  • [x] Check that the framing and tense used for each item is future-conditional. Ie: "IF this executive proposal passes, THEN this action will take place."
  • [x] Check that hyperlinks to documentation and/or context are added to key parameters, terms, and contracts where reasonable and possible.
  • [x] Check that Ethereum and IPFS addresses are hyperlinked such that it is easy to view their details.
  • [x] Check that parties implicated in the proposal outcome related to this item are aware of the wording used.

Final Checks

• [x] Read the executive copy in full, with the above checklists and general readability in mind. Raise any issues with the author.

[0xldr]

cast keccak -- "$(wget https://raw.githubusercontent.com/makerdao/community/0434f8718e4b63cfeb4bcc0f87b8a34ec3c8ea36/governance/votes/Executive%20vote%20-%20November%2014%2C%202024.md -O -)"
[0] Downloading 'https://raw.githubusercontent.com/makerdao/community/0434f8718e4b63cfeb4bcc0f87b8a34ec3c8ea36/governance/votes/Executive%20vote%20-%20November%2014%2C%202024.md' ...
HTTP response 200  [https://raw.githubusercontent.com/makerdao/community/0434f8718e4b63cfeb4bcc0f87b8a34ec3c8ea36/governance/votes/Executive%20vote%20-%20November%2014%2C%202024.md]
0xfb975e3cd0a4f127e0c19c95a778d5f3d4263de733a347f5cd7e7030252cb007

0xfb975e3cd0a4f127e0c19c95a778d5f3d4263de733a347f5cd7e7030252cb007 matches the output of https://emn178.github.io/online-tools/keccak_256.html

[MakerJanSky]

With the new changes, we're getting a hash of:

0x1bb8e29f12f8d0a4d03a82f8b9ad78945d3de288a79895142d213ceb2a6d0820

[VoteWizard]

Hash of the Document Before Merging

Command: cast keccak -- "$(wget 'https://raw.githubusercontent.com/makerdao/community/15c84e55529a280e29eeda56ec4bc0651ef42542/governance/votes/Executive%20vote%20-%20November%2014%2C%202024.md' -q -O - 2>/dev/null)"

Hash: 0x1bb8e29f12f8d0a4d03a82f8b9ad78945d3de288a79895142d213ceb2a6d0820

The hash matches with the outcome of this online tool: https://emn178.github.io/online-tools/keccak_256.html