The repository describes Governance Emergency Rollback as a system for reversing executed governance proposals that create negative consequences.
It supports Compound-style governance and OpenZeppelin Governor plus TimelockControl through separate implementation paths.
Core contract: Rollback Manager, which manages propose / queue / execute / cancel lifecycle for rollback transactions.
Security model described in the README: admin can propose rollbacks and manage settings; guardian and admin can queue, execute, or cancel rollbacks; queue windows stop indefinite rollback availability.
The design preserves existing timelock delays instead of allowing instant reversals.
The key packaging trick is double encoding: rollback transactions are encoded as inputs to Rollback Manager propose(), and that call is then included inside the main governance proposal.
The repository prominently warns that the system is under active development, not complete, not audited, and not ready for production use.
Repository page
The GitHub landing page repeats the active-development and not-production-ready warning.
It summarizes the same lifecycle and security-model concepts for quick public inspection.
Why it matters to the corpus
Governance rollback is a clear post-execution governance backstop primitive.
It complements Seatbelt as a later-stage governance safeguard and helps separate three often-confused control surfaces: proposal verification before voting, vote expression during voting, and rollback authority after execution.