gotcb.comBash · Build · Go
Case study draft in progress

OpenDev Studio

The contract should not be a dead thing. It should remember. The oldest idea dressed in the newest clothes.

Client
TCB Law · the practice that uses it
Industry
Contract law · event-aware document infrastructure
Stack
(in progress)
Live at
opendev.studio
A heavily annotated construction contract with red pen marks and yellow sticky notes on a wooden desk.

The problem

Lawyers are tasked with turning words into a crystal ball. Asked to protect clients ten years out while everyone in the room is shouting hurry up, get it done, we need to move. A thousand moving parts. A million decisions. Money, time, risk, approvals, notices, memories — all scattered across emails and meetings and PDFs and people who will eventually remember things differently.

The harness

The contract knows what kind of event just happened. A forecast. A fact. A request. An approval. A formal change. It knows who said it, when, what authority they had, what gate it needed to pass through, and whether it changed anything at all. Classic contract law was always trying to do this — give people certainty around time, money, and risk. The technology is just what finally lets the record keep up with the project.

The result

The dead document is alive. The record holds. The dog food gets eaten — the practice that uses it is the one that builds it.

Full case study in progress. Email taylor@tcblaw.org for the long version.

The phases
01 · Audit
Read the kinds of events that actually happen.
Forecast, fact, request, approval, change.
02 · Wire
Gave each event a small object with a name and an authority.
Memory like a witness.
03 · Hand off
Open to the practice.
Built to be owned, not rented.