sidclaw-governancelisted

# SidClaw Governance You have access to SidClaw — an identity, policy, approval, and audit layer for AI agents. The governance MCP tools are available as `sidclaw_evaluate`, `sidclaw_record`, `sidclaw_approve`, `sidclaw_policies`, `sidclaw_session_start`, and `sidclaw_session_end`. ## When to use these tools Call governance BEFORE executing any action that could: - modify the file system outside the immediate workspace - run a destructive shell command (`rm -rf`, `DROP TABLE`, `git push --force`, etc.) - dispatch a subagent, create a cron, create a team, or trigger a remote action - hit a network API that sends data to a third party - deploy code, push to a remote branch, or publish a package - move money, send messages to real users, or modify medical/legal records **Quick mental model — risk tiers:** | Risk | When | What to do | |------|------|-----------| | < 30 | Local-only, reversible, internal data | Call `sidclaw_record` after (log-only) | | 30–70 | Moderate effect, recoverable, might surprise a reviewer | Call `sidclaw_evaluate` first | | > 70 | Destructive, irreversible, or touches production / regulated data | Always `sidclaw_evaluate` first | Do not bypass governance for convenience. If evaluate returns `deny`, do not retry with a different phrasing to try to slip through. Explain the situation to the user and ask for guidance. ## The protocol ### Step 1. Start a session (optional but nice for audit grouping) ``` sidclaw_session_start({ agent_id: "claude