Writ

Governance runtime for Claude Code. Enforces workflow gates at tool time, delivers the engineering rules relevant to the work, and preserves decision provenance

What is Writ?

Governance runtime for Claude Code. Enforces workflow gates at tool time, delivers the engineering rules relevant to the work, and preserves decision provenance across sessions.

Overview of Writ

What it is

Writ is a governance runtime for Claude Code that enforces workflow gates at tool time, delivers engineering rules relevant to the work, and preserves decision provenance across sessions. It runs on the local machine and consists of hooks that Claude Code calls around each tool use, a local daemon that makes decisions, and a Neo4j database in Docker that stores rules and decision records. It moves selected requirements out of the prompt into code that runs when the agent acts.

Key features

  • Moves requirements from prompts into executable checks and acceptance gates that run when the agent attempts actions
  • Provides acceptance gates including mode, plan, test-skeleton, drift, plan freeze, project boundary, debug root cause, and credential write gates
  • Refuses writes that violate active gates instead of merely discouraging them
  • Records each refusal and approval as a row on an audit stream in JSONL files
  • Links commits to changed files, the plan's reason for changes, and the rules shown to the agent via a post-commit hook
  • Delivers context (rules, methodology, past decisions) relevant to the current prompt, file, and workflow phase
  • Constrains a cooperative agent, not a sandbox

Use cases

Writ is used to enforce workflow gates during Claude Code sessions. Example use cases include requiring an approved plan before any source writes, requiring approved test skeletons before implementation, preventing writes outside the project root, blocking writes to credential files, and preventing plan drift after approval. It provides a way to audit what was approved, why files changed, and which rules were applied.

Getting started

See the repository README for installation and configuration instructions. The system requires Docker for the Neo4j database, and the daemon runs locally on your machine.

License and pricing

Writ is open source under the MIT license.

Based on the project's public README and repository metadata.

Add this badge to your README

Featured on YunoDB Badge styles & help

Maintain this project? Show that it is featured on YunoDB.

Markdown[![Featured on YunoDB](https://yunodb.com/badge/infinriwrit.svg)](https://yunodb.com/tools/infinriwrit?utm_source=github&utm_medium=badge)
HTML<a href="https://yunodb.com/tools/infinriwrit?utm_source=github&utm_medium=badge"><img src="https://yunodb.com/badge/infinriwrit.svg" alt="Featured on YunoDB" height="20"></a>