SeriesThe Blog
The Build Archive
Notes written while the system was being built, in the order the problems arrived. What a document has to become, where arithmetic beats a model, and why a claim is worth nothing until something can fail it.
- Before You Analyze a Contract, You Have to Know What It IsStart hereA capable model may know what a contract is. That does not mean it will reliably know what deserves attention in every type of deal.
- A Document Should Enter a System, Not Disappear After GenerationGenerating a contract is an event. The document should outlive the screen that created it.
- Software Should Teach While It WorksA red flag is not an explanation.
- When Arithmetic Can Be Known, Don't Ask AIInterpretation is a judgement. A royalty calculation is not. One of those is worth asking a model for, and the other it should never be trusted with.
- Measure What You Actually BuiltA passing test suite can prove exactly what it tested. The dangerous part is everything you quietly assumed it covered.
- A Contract Should Not End at DownloadCreating the document is only one moment in the life of an agreement. The harder product problem begins when another person has to act on it.