What problem does it solve? Claude Code tool calls have no audit trail, no policy enforcement, and no way to prove what was decided after the fact. Session logs are mutable, unsigned, and require trusting the operator, which fails compliance requirements in finance, healthcare, and regulated research. ## Core Features & Use Cases - Cedar Policy Enforcement: A PreToolUse hook evaluates every tool call against a Cedar policy file and blocks execution when Cedar returns deny. - Ed25519 Signed Receipts: A PostToolUse hook signs a hash-chained JSON receipt for each tool call, recording inputs, outputs, decision, and policy digest. - Offline Verification: Receipts can be verified by third parties with npx @veritasacta/verify without any server, account, or trust in the operator. - Use Case: A regulated research team needs tamper-evident evidence of every agent action. After setup, each Bash, Edit, or Write call is policy-gated and produces a signed receipt in ./receipts/ that auditors can verify offline. ## Quick Start Ask the agent to install the protect-mcp plugin, add the PreToolUse and PostToolUse hooks to .claude/settings.json, create a protect.cedar policy file, and start the local receipt-signing server with npx protect-mcp serve --enforce.