becwright
About becwright
Why deterministic guardrails exist, and who builds them.
Last updated
Why becwright exists
Every AI coding setup ships rules as prose: CLAUDE.md, .cursorrules, style guides, review checklists. They all share the same failure mode — they only work if the next agent (or the next human) reads them, understands them and chooses to obey. That is a probabilistic guarantee, and probabilistic guarantees fail exactly when it matters: three months later, on the module an agent regenerated without reading the note.
becwright takes the opposite bet. A rule that matters should be a check that runs. The engine executes your constraints against the real staged code on every commit and returns pass or fail — no interpretation, no goodwill required. CLAUDE.md keeps its job (getting 95% right the first time); becwright is the safety net for the 5% that slips through.
Who builds it
becwright is built by David (DataDave-Dev on GitHub), a developer focused on making AI-assisted development safe enough to trust in production repos. The project is open source under the MIT license and grows in the open: every check, release and design decision is public in the repository.
Contact
The fastest channel is a GitHub issue — bug reports, feature requests and BEC proposals all have templates. For anything else, email works: deleonalonso77@gmail.com.