Engineering
How we build it: architecture, trade-offs, and first-principles thinking behind litigation intelligence that has to be right.
AI is too eager. Don't ship what the team can't explain.
Agents made writing code cheap and understanding it expensive. How we rebuilt our engineering around comprehension: the harness, the trace, the walkthrough
Take a number: fencing tokens on the Brief rail
A worker that hangs past its lease wakes up believing it still owns the work. A boolean can't stop its stale write. A monotonic counter checked by the database can.
Authentication at the perimeter. Authorization at the data layer.
"Access control" is three questions wearing one word: who you are, which records you can touch, and what you're allowed to do. We pulled them apart on day one and enforce each where it can't quietly fail.
Render on the server. Own the data on the client.
Why a legal product renders its first paint with Next.js, then hands every interaction after to a client cache it fully owns.