Lexicon – Write complex legal contracts in Markdown
Git-versioned contracts in Markdown that compile to Word—lawyers can finally use version control.

Git version control for contracts when Word still uses Agreement_v4_FINAL.docx.
Lawyers, startup GCs, legal ops teams
LawGeex · ContractKit · DocuSign CLM
When you need production output, it can be compiled to .docx with automatic clause numbering (1, 1.1, (a), (i)), cross-reference resolution, defined term validation, cover pages, signature blocks and schedules.
I'm a lawyer who runs a small practice and does GC work for startups. Drafting contracts in Word is painful and I have always hated the workflow. Track changes can be deleted by anyone, version control is "Agreement_v4_FINAL_VLs_edits(2).docx" and now copy/paste to and from Claude is a pain.
I've been thinking about how to transition off Word and into text on and off for the better part of 7 or 8 years, and the possibility of opening my workflow up to "coding" agents has given me the push to actually finalize my work.
You can play with it here: https://play.lexicon.esq. If you want to compile to docx, you can use the tool here: https://github.com/RichEsq/lexicon-docx
Git-versioned contracts in Markdown that compile to Word—lawyers can finally use version control.
Single YAML contract eliminates instruction drift across Claude, Cursor, and Copilot.
Word doc surgery for agents; MCP integration lets Claude handle contract redlines without format destruction.
YAML contracts enforce agent behavior where Guardrails and LMQL focus on outputs.
AI contract review that drafts negotiation responses in three tones.
OCI-distributed service contracts beat scattering config across six different files.