Why contract automation is not an easy problem
Contract automation is not just summarization. The hard work is turning complex agreements into operational rules that can be checked over time.
Lynn Cole / Writing
Essays, thoughts, and technical notes.
Contract automation is not just summarization. The hard work is turning complex agreements into operational rules that can be checked over time.
AI coding projects fail for familiar engineering reasons: weak planning, vague standards, missing security, poor QA and testing surfaces nobody can manage.
The new compiler wants you to think of it as a modern language.
Before paying for another training run, inspect the process: clean inputs, explicit steps and properly labeled tool results solve a different class of problem.
A prediction about democratizing compute, open agent systems and the economic big bang I imagined they would create.
Mocks can disappear from an agent’s memory after compaction. Detailed epics help—and bugs remain valuable information about the structure you actually built.
A weekend inside an inference engine reveals device middleware, data shaping and old architectural assumptions that still deserve to be challenged.
Documentation is infrastructure, whether it lives in code, a ticket, a notebook or a coffee-stained napkin. Write down what tomorrow will need.
A range editor needs to know which lines an agent has actually read. My design tracks witnessed content and makes stale edits explicit.
Prompt moderation is not image moderation. I argue for evaluating generated images and building correction loops around the output.
Bigger embeddings do not automatically mean better retrieval. Match the corpus, chunking, context and search architecture to the job.
What if agents shared dense study notes the way students do? One agent does the reading, and a whole peer group benefits.