RECORDW3C Verifiable Credentials

Know what the agent was allowed to do

Euthyne reads your Claude Code permission rules at every hook and signs them as a mandate. Each receipt then says whether its action was inside the rules, outside them, or undecidable.

What a mandate captures

Your rules, as Claude Code saw them

Every settings file

Managed settings, project and local settings, your user settings and the MCP server lists. The env block is never copied.

Allow, ask and deny

Rules are kept verbatim, from Bash(git:*) to Read path globs and WebFetch domains, with the default mode and sandbox settings.

Signed and versioned

A mandate is a W3C Verifiable Credential with an eddsa-jcs-2022 proof. When your settings change, a new version is signed and chained to the last.

Per action

In, out or unknown

  1. Deny first

    If a deny rule matches, the action is out of mandate. If a deny rule cannot be decided, the result is unknown, never in.

  2. Then ask and allow

    A matching ask or allow rule puts the action in, as does a mode that allows it, like acceptEdits for edits inside your working directories.

  3. On the receipt

    The receipt cites the mandate version and records the result, the rule and the reason. Mandates are logged before the receipts that cite them.

Related

Where to go next

Every action.
On the record.

Euthyne is in public beta. Leave your email and we'll reach out, or install the CLI and read the quickstart.

Install script
curl -fsSL https://euthyne.com/install | sh
Homebrew
brew install euthyne-labs/tap/euthyne
Read the quickstart
Euthyne
EuthyneBordeaux