syndicate-owner

To veto malicious governance proposals and protect vault capital, you need to monitor pending and active Sherwood proposals, simulate outcomes on-chain, and execute a veto through the Sherwood CLI using vault-owner permissions.

On-chain simulation for Sherwood syndicate governance proposals works by modeling risk-aware decision outcomes before execution, allowing guardians to assess capital impact and prepare emergency actions without moving funds.

Yes, you need vault-owner permissions to perform emergency actions in a syndicate, as these privileges authorize vetoes, emergency settlements, and capital safeguarding operations through the Sherwood CLI.

The best way to monitor governance proposals across multi-chain syndicates is to configure the Sherwood CLI with a minted agent identity to continuously track pending and active proposals across chains.

You should use emergency-settle workflows for LP capital during crises when malicious proposals threaten funds, allowing guardians to execute quick-response protective actions before capital moves.

No, you cannot use the Sherwood CLI for guardian operations without minting an agent identity, as this identity is required to join or create a syndicate and perform governance oversight tasks.