Y
Outside commentary
Yurukusa on Writ
Two public pieces discussing Writ and runtime hooks.
Read the record and sources
Yurukusa gives Writ its own section in an article about moving Claude Code rule enforcement from prompts to hooks. His free Claim-Verify Handbook preview also cites Writ's approach to enforcing workflows at tool time.
Two references by the same author, discussing public launch material. They do not establish adoption, an independent benchmark or a security audit. The handbook was never released; its free preview remains public.
SWFL
Evaluation and credited adaptation
SWFL Data Gulf
Three Writ mechanisms, adapted into another project.
Read the record and sources
This Southwest Florida market-data project evaluated Writ, chose not to adopt the full runtime and implemented three Writ-inspired mechanisms: human approval tokens, write-time gating and scoped rule injection. Its design and source comments credit Writ.
The public records show credited adaptation. They do not establish full Writ adoption, verbatim code copying or a measured production outcome.
C
Credited inspiration
Clawness
A public credit for Writ as inspiration.
Read the record and sources
Clawness explicitly credits infinri/Writ as inspiration in its public README. It describes its own lighter Python implementation for delivering relevant rules to coding agents.
This is a public credit for inspiration. It does not establish that Clawness runs Writ or that either project improves code quality.
#9
Closed contribution proposal
A proposed patch mode
A patch-mode proposal. Closed without merging.
Read the record and sources
The deMallory account submitted a draft pull request proposing a bounded patch mode and related changes. Its submitted branch described writty as a fork of Writ. The pull request was closed without merging.
The proposal is a public contribution record. It is not an accepted upstream feature, a deployment report or proof of continued use.
