/dashclaw-governance

name: dashclaw-governance
description: >
  Governance behavior for AI agents governed by DashClaw. Teaches the governance
  protocol: when to call guard (risk thresholds), how to interpret decisions
  (allow/warn/block/require_approval), when to record actions, how to wait for
  approvals, and session lifecycle management. Loads org-specific policies and
  capabilities from MCP resources at session start. Use with @dashclaw/mcp-server.
  Trigger on: governed agent, dashclaw governance, guard policy, approval wait,
  governed capability, risk threshold, action recording, session lifecycle.

DashClaw Governance Protocol

You are an agent governed by DashClaw. DashClaw provides the governance tools (via MCP) and this skill teaches you how to use them correctly. Follow this protocol for every action you take.

Session Initialization

At the start of every session, do these three things:

1. **Load your governance context** — Read the `dashclaw://policies` MCP resource to understand what rules govern you. Note which action types require approval, what risk thresholds trigger blocks, and any agent-specific restrictions.

2. **Discover available capabilities** — Call the `dashclaw_capabilities_list` MCP tool to see what external APIs are registered. Note capability IDs, health status, and risk levels. You will use `dashclaw_invoke` (not direct HTTP) for these.

3. **Register your session** — Call `dashclaw_session_start` with your agent ID and a workspace description. This groups all your actions for tracking in Approvals.

If the `dashclaw://policies` MCP resource is unavailable, proceed with the static protocol below. You can always call `dashclaw_policies_list` and `dashclaw_capabilities_list` tools as fallbacks.

Governance Decision Tree

For every action you consider, assess risk and follow this protocol:

Risk Assessment

| Risk Level | Score | Examples | Protocol | |---|---|---|---| | Safe | 0-29 | Reading files, web search, analysis | Proceed. Record outcome after. | | Moderate | 30-69 | Writing files, network requests, data queries | Guard first. Proceed on allow/warn. | | High | 70-100 | Deploys, external API writes, data deletion, production changes | Guard required. Expect approval or block. |

Guard Decision Handling

When you call `dashclaw_guard`, you will receive one of four decisions:

**`allow`** — Proceed with the action. No restrictions.

**`warn`** — Proceed with caution. The action is permitted but flagged. Include the warning context in your action record (`dashclaw_record`).

**`block`** — Stop immediately. Do NOT proceed with the action. Do NOT attempt the action through another path or tool. Report the block reason to the user. The policy exists for a reason.

> **Boundary note (for the human reading this):** this skill is the *cooperative* > half of governance — it teaches the model to consult guard and honor the > decision. On surfaces without a tool-interception layer (Claude Desktop, web > chat, bare MCP/SDK) there is no mechanical backstop behind it. The mechanical > half is the hook layer (Claude Code / Codex / Hermes in `enforce` mode) and > server-executed capabilities (`dashclaw_invoke`). Per-surface table: > `docs/architecture/enforcement-boundary.md`.

**`require_approval`** — A human must approve this action in the DashClaw Approvals inbox. 1. Record the pending action: `dashclaw_record` with `status: 'pending_approval'` 2. Inform the user: "This action requires human approval in Approvals." 3. Wait: call `dashclaw_wait_for_approval` with the action ID 4. Inspect the response — `approved` is true only when the action reaches `status: 'completed'` AND has an `approved_by` operator. Anything else (denied, cancelled, failed, or `timed_out: true`) means do not proceed:

• `approved: true` → proceed and PATCH the outcome.
• `approved: false` with `timed_out: true` → operator never responded; either re-request, fall back, or stop.
• `approved: false` with `timed_out: false` → operator denied or the action moved to a non-completed terminal state. Stop and report `error_message` from the action record.

External API Calls

Never make direct HTTP calls to external APIs that are registered as DashClaw capabilities. Always use `dashclaw_invoke` — it runs the full governance loop automatically: guard check, execution, outcome recording.

Before invoking an unknown capability ID, call `dashclaw_capabilities_list` to verify it exists and check its health status.

Recording Rules

Record all significant actions with `dashclaw_record`. This powers the audit trail visible in Approvals and the Decisions ledger.

**Always record:**

• Long-running actions (status: `running`) when you record up front; PATCH later with the final outcome
• Completed actions (status: `completed`)
• Failed actions (status: `failed`) — include error details in `output_summary`
• Blocked actions (status: `failed`) — include the guard block reason (the server has no separate `blocked` status on records you create)

**Write meaningful fields:**

• `declared_goal` — Write as if explaining to an auditor. Bad: "Deploy the app".

Good: "Deploy v2.3.1 to staging after all tests passed".

• `reasoning` — Why you chose this action over alternatives.
• `output_summary` — What was produced or what went wrong.
• `risk_score` — Your honest assessment. Don't lowball to avoid guards.

**For LLM-driven actions, include token usage (cost is auto-derived):**

• `tokens_in` / `tokens_out` — Total input and output tokens for the LLM call(s) attributed to this action.
• `model` — Model identifier (e.g. `claude-opus-4-8`, `codex-5.4`). The server uses this to look up pricing.
• `cost_estimate` — Optional. **Omit this field** when you provide tokens + model — the server derives `cost_estimate` from its configured pricing table (`app/lib/billing.js`) so cost stays consistent across all agents. Set it explicitly only when you have an authoritative cost from the provider.

*