Skip to main content
The site
The homepage. “Contracts made simple.” on cream, with the real composer under it — the control the app mounts, not a screenshot of it — and the sample contract a single sentence turns into. Below it: the three ways in, the redline section, what the other side sees, and the room.The door. One field. The plus opens a real file picker and takes more than one file; the microphone is drawn only where the browser can genuinely listen; governing law stands at the bottom right beside send. Nothing runs before sign-in, and the gate says so at the press.The governing-law picker. 184 pickable places under ten counted regions, search that resolves cities, Popular as one plain word, and more than one allowed. An anchored card at 640 and above, a bottom sheet below it, built from one body of markup so they cannot drift.The place pages. contracts.io/law — an index and a page for every legal unit, each with an “In brief” block of Wikidata facts, the source named and Wikipedia linked. No legal-system row anywhere, by proof rather than omission.The template catalogue. contracts.io/templates — an index and 87 kinds across twelve shelves. The twelve the door recognises wear “In the library”; the other 75 say plainly that the door does not match them. No download anywhere; every page ends at “Start it at the door”.The blog. contracts.io/blog — three posts: Accepting is not signing, What “governing law” actually decides, and One field, not a form: how contracts.io reads your sentence.For agents. /llms.txt and /llms-full.txt covering every URL, a static sitemap, and a robots.txt that names sixteen read, search and training agents and allows them.
These docs
contracts.io docs, first cut. This site, in the house palette: the door, governing law, templates, redlines and the room, accepting is not signing, Lex, crawlers and the questions.The model, written down. Anatomy of a contract carries CONTRACT-SCHEMA v0 — the twelve nouns, the three signature states and the eight laws the schema enforces with real checks. Both questions the docs review found open are now answered: a Version is minted on Send and at signing, and governing law is always a list. Glossary picks one word per thing and says what lost.The hole, named. CANON-1 — the canonicalisation every signature’s hash depends on — still does not exist, and the anatomy page says so rather than burying it.An API tab. The HTTP surface and the MCP server, moved in from the design repo under one banner: draft, ahead of the backend, nothing live yet.ClauseBench is in preparation, and its page carries the terms it will be built under rather than a number.