writ runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 5 Oct 2026.
Commit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 2 October 2026. No other catalogue keeps this.
What the code does
We read the source, 6 d ago · rules ccca72095570
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return sorted(p for p in root.rglob("*.py")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check writ every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Alternatives to writ
same job, measured the same wayCommit-time policy checks for AI agent writes (ALLOW/DENY/STEP_UP) with a tamper-evident audit log.
Pre-execution gate for AI-agent tool calls. Touch ID approval. Tamper-evident audit log.
Safe-by-default SQL guardrails for AI agents: AST-checked queries, per-table policy, audit log.
Tamper-evident audit logs for AI agents: submit, fetch, and verify cryptographic proof bundles.
BYOK Reddit/YouTube research CLI with a tamper-evident audit log and an MCP server.
Hosted CRM and task desk for AI agents: per-agent keys, scopes, pause and audit log.
Process monitoring for AI agents: start runs, submit per-task evidence, complete runs.
Nostr publishing, queries, and DMs for AI agents, with allowlists, rate limits, and an audit log.
writ — questions
Answers built from our own checks of this server.