Eleven Years in the Making: From Matter Hierarchies to One Auditable Legal Dataset

People sometimes assume a legal data platform launched in 2026 must have been conjured up by a language model over a weekend. We understand why. But the website is the newest part of this project, not the oldest. The thinking behind it goes back more than a decade, and it began years before anyone could ask a chatbot to draft a matter plan.

2015: Starting With the Shape of a Matter

In 2015 our founders began building legal matter data hierarchies. The starting question was simple to ask and hard to answer: if you strip a legal matter down to its structure, what shape is it? Not the facts of one client, but the recurring skeleton that every divorce, every debt recovery and every caveat dispute shares with the others of its kind.

Today every plan on the network uses the same hierarchy: a matter type breaks into stages, stages break into milestones, and milestones break into tasks. Holding to one shape consistently, across practice areas that describe their own work in very different words, is the hard part, and it is the part that work started.

2019: From Structure to Practice Systems

A hierarchy on its own is a map. Practitioners need a vehicle. In 2019 the founders began building legal practice systems on top of that structure: precedent libraries, so the documents a task calls for sit next to the task, and workflow generators, so a matter can be opened with its steps, deadlines and documents already in place rather than rebuilt from memory each time.

Practice systems built one at a time share a well-known weakness: each tends to invent its own names for the same things. A client name in one precedent becomes a party name in another and an applicant in a third, and every new workflow means another round of mapping. That is the problem a single standard is meant to remove.

2026: One Uniform, Universal Dataset

This year we started combining that knowledge into a single uniform dataset: matter plans, the court and council forms and precedents they call for, and one canonical field standard that both of them speak. Instead of three systems that each need translating, there is one stack where a plan task, a form field and a practice management system field all point at the same defined term.

• Matter plans in the same four-level hierarchy, classified against the SALI Legal Matter Specification Standard.
• A forms and precedents library where every fillable field is bound to a named field in the standard.
• A field standard of several thousand defined terms, each carrying its own description and format.
• An audit trail underneath all of it: content hashes, a change log for plans, and version hashes for forms.

Why Auditable Matters More Than Fast

We do use modern tools, including AI-assisted research, to draft and extend plans. We say that plainly because the useful question is not whether a tool was used but whether the result was checked. Every legal claim on the network is held to a primary source, and when a source cannot be found the claim comes out rather than staying up with a warning on it. The posts that follow in this series explain how we do that, with the real numbers.

“The structure came first. The software came later. The checking never stops.”

- OMPN Team