Warrant

Lets an assistant file signed, hash-addressed decision records into a local warrant store and verify that store's integrity.

What you can do

Exposes three tools: warrant_file_decision files a propose, accept, reject or supersede record with prose reasons and optional re-runnable checks, returning the warrant id; warrant_verify_store verifies every hash, signature and link and returns the CLI's verify report; warrant_show_reason returns a warrant's decision, actor, reasons and verified why chain, re-executing ski@v1 checks locally. The store is initialized on first use, and the server runs the warrant CLI as a subprocess.

When to use it

Use it when an agent should deliberately record its own decisions, with reasons that can be re-executed offline, into a local evidence store. It is not the sealing proxy for someone else's MCP server; if you want to record what an existing server is doing, this is the wrong tool.

Requirements

A local Python runtime with the warrant-verify package (0.8.0 or newer) installed, or a checkout run directly. Configure the store path via --store or WARRANT_STORE, preferably absolute; the actor via --actor or WARRANT_ACTOR; and the signing key via --key or WARRANT_KEY. The warrant CLI must be available, by default beside the module or on PATH.