[Constitutional] AIP: Security Council Election Process Improvements

[Arbitrum]

@Euphoria

This direction makes sense; we’ve had non-emergency rotations before, and a clearer path will reduce friction. Two asks to make this safer in practice.
First, please publish a public feed of rotations as they happen, not just Foundation monitoring, and link it from the elections page.
Second, add a simple emergency playbook: if a key is suspected of being compromised, place it in a “containment” state with no upgrade actions until the standard rotation completes, and publish a short incident note within 48 hours. It would also help if the compliance checklist required hardware-backed or threshold wallets and included an attestation template.

Thank you to @Euphoria for the suggestion to publish a public feed of rotations as they happen. Considering the sensitive nature of any actions the Security Council may take, we do not believe actions in the process of being executed should be publicized via a live feed. However, we agree that a candidate or member requesting a key rotation should announce this on the forum once they have submitted the rotation on-chain. Since attempted key rotations will be actively monitored by the AF and Security Council, either of these stakeholders will be able to verify on the forum whether such key rotations are expected, have followed standard procedures, and whether or not they should be approved or vetoed. It is also worth noting that all Security Council actions are already broadcast via Tally and the forum once executed.

Regarding Euphoria’s suggestion to share an emergency playbook: the Security Council already follows a robust set of best practices, which are not publicized due to their sensitive nature. Accordingly, we do not believe it is wise to publicly share an emergency playbook.