content(governance): add Security Council Best Practices page

[artemisclaw82]

Summary

Adds a new page to the Governance framework covering Security Council best practices for rollup governance.

Based on: From Stage 0 to Stage 1: Security Council Best Practices in Rollup Governance by OpenZeppelin (Bram Hoogenkamp & Michael Lewellen).

Content

• Understanding Security Councils — roles, responsibilities
• Formation & Timing — prerequisites, maturity requirements
• Multi-Sig Setup & Custody — configuration, thresholds, key rotation, LivenessGuard example
• Incident Response — automated vs manual pausing, emergency upgrades, scope definition
• Governance Integration — DAO alignment, cross-protocol collaboration, SEAL 911 war rooms
• Readiness Drills & Maintenance — scheduled/unannounced drills, liveness testing

Changes

• New: docs/pages/governance/council-best-practices.mdx
• Updated: vocs.config.ts (sidebar entry)
• Updated: docs/pages/governance/overview.mdx (contents list)
• Updated: docs/pages/governance/index.mdx (page link)

Build verified clean ✅

Closes #109

[vercel]

@artemisclaw82 is attempting to deploy a commit to the Security Alliance Team on Vercel.

A member of the Team first needs to authorize it.

[scode2277]

@DicksonWu654 I made this a draft till you review and mark it ready, like all the other PRs raised the past week

[artemisclaw82]

Disclosure: This content was written by Artemis, an AI assistant operated by @DicksonWu654. It has not yet been reviewed by a human. Dickson will review and revise before marking as ready for review.

[github-actions]

Sidebar Configuration Reminder

Documentation files update:

New in this push:

• docs/pages/governance/council-best-practices.mdx (added) ← NEW

Please ensure that:

• The sidebar in vocs.config.tsx has been updated to include these files
• New content has the dev: true parameter so it's marked as under development
• Sidebar links match the file paths - use the preview deployment to verify

See Contributing Guide – Sidebar & Navigation for more details.

---

_{This is an automated reminder. If this PR doesn't need sidebar changes, you can ignore this message.}

[artemisclaw82]

Verified against OpenZeppelin source article. Two corrections made:

1. LivenessModule → LivenessGuard: Optimism specs use "LivenessGuard" — fixed and added link to Optimism specs
2. Compound wargame attribution: The simulation was conducted by the SEAL Chaos Team with OpenZeppelin and Compound Labs — fixed attribution and added specific details from the source (28% WETH price inflation, $650K USDC risk)

Verified accurate against source:

• ✅ Authors: Bram Hoogenkamp and Michael Lewellen
• ✅ Council responsibilities: threat ID, emergency response, protocol stewardship, risk mitigation
• ✅ Formation timing: Stage 0 → Stage 1 in L2BEAT framework
• ✅ SLA examples: response times, upgrade review periods
• ✅ Multi-sig models: Individual EOA vs Safe-of-Safes architecture
• ✅ Key rotation: 3-4 times annually per source
• ✅ Incident response phases: detect → assess → action → communicate → postmortem
• ✅ Communication strategy: rapid notification, single source of truth, public vs private details
• ✅ SEAL integration references: War Rooms, Drill Templates

[DicksonWu654]

lgtm!

[DicksonWu654]

please undraft now and have it ready for review

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
frameworks	✅ Ready (View Log)	Visit Preview	d84bc8b

[scode2277]

@mattaereal ready to go! Thanks @DicksonWu654!!