Chambers
A practice-minder an attorney can trust.
What happens when the Behavioral Orchestration framework has to survive contact with a real profession — one where a hallucinated deadline isn't a bug, it's malpractice.
Context
A solo attorney is the lawyer, the clerk, the docketing department, and the file room. What they miss is what ends careers: the deadline nobody calendared, the contradiction sitting across two documents. Legal AI mostly sells generated output — research, drafting, summaries. The actual risk in a solo practice is the opposite problem: nobody reads what already exists.
My role
Founder and only builder. Product, interaction model, engineering direction, and the testing practice — built solo with AI tooling through 2026, from first spec to a running v0.79 product.
The system
Chambers reads the documents an attorney already has and proposes what it finds — matters, parties, dates, contradictions. Proposes, never asserts. Every extracted date carries its provenance. Every finding is one click from the passage that produced it. Anything the machine is unsure about waits in an attention queue for a human decision, and nothing unconfirmed ever counts as knowledge. It runs entirely on the attorney's device; AI is optional, on their own key, and constrained to summarizing sources it actually retrieved.
The Emergence Interactive
Import → intelligence
Firm Zero starts empty.
No dashboards, no dossiers — the intelligence doesn't exist until the organization's record arrives. This is the product's opening move, miniaturized.
The record, parsed
What the import discovers
The workbench · health, computed
Judgment that was always there, becoming visible. Every number above is a pure function of the record — the same inputs always score the same.
The hard calls
Three times, the honest move was deleting something impressive. A confidence percentage that looked rigorous and wasn't — deleted; the product now shows counts of things that exist, never scores invented to look sure. An economics engine that estimated billable value — deleted; work is reported as recorded, never inferred. And deadline computation, which the product once refused entirely: when it finally shipped, it shipped as cited proposals marked "verify," behind a human gate, declining rather than guessing when a rule is unclear. The discipline is the product.
Testing like it matters
I built a fictional law firm to break it — Apex Dynamics, an attorney-grade synthetic corpus grown over twelve sprints, plus a three-round evaluator protocol where a missed fact costs one point and an invented fact costs two. Two family-law matters in the test corpus share a party on purpose; merging them is scored as a serious failure. The demo world, Firm Zero, is what visitors can explore.
Where it stands
v0.79, ~530 automated tests, ~125 tagged releases, local-first, in active evaluation with attorneys. Built for roughly zero dollars. Honest gaps: multi-firm mode, server OCR, and attorney attestation of the deadline rule table are specified, not built.
Behavioral Orchestration started as a framework document. Chambers is what it looks like when the framework has to keep a stranger's law practice safe.