M · A · T · T · E · R

The MATTER Method manifesto.

Every matter-based practice, from a solo desk to a large organisation, runs on the same six primitives. Name them and you see the practice clearly. Systematise them and it stops depending on memory. Automate them and you have an AI-native practice, in exactly that order. This is the doctrine in full: why it exists, what the six primitives are, and how to install them.

Why a method

Law never named its primitives.

Every profession eventually discovers its primitives.

Accounting found them centuries ago: the debit, the credit, the ledger, the double entry. Software engineering found the function, the repository, the commit, the deployment. Medicine found the chart, the vitals, the differential, the protocol.

Law never did this properly.

Ask a lawyer what a legal practice is made of and you get a list of things: clients, cases, documents, deadlines, courts, fees. All true, none structural. It is like describing a building as bricks, glass and people. Accurate, and useless for building anything. Every practitioner reinvents their own system. Every firm is a private collection of undocumented workflows. When a lawyer leaves, retires or simply forgets, the system leaves with them.

For most of legal history this did not matter much, because the constraint on the work was judgement, and judgement lived in people. It stops being survivable once machines can execute a meaningful share of the work, because machines cannot execute what has never been named. You cannot automate a workflow that exists only as instinct.

The MATTER Method closes that gap. It is a claim about what matter-based work is actually made of, structurally, underneath every practice area, jurisdiction and firm size: all of it decomposes into six primitives. Matter. Actions. Time. Team. Evidence. Research.

Name them, and the practice becomes visible for the first time. Systematise them, and it stops depending on memory. Automate them, and you have an AI-native practice. That is the whole game.

The six primitives

Six pieces. Every practice. Everywhere.

01

MMatter

The matter, not the client, the document, or the task, is the atomic unit everything else in the practice attaches to.

This sounds obvious and is not. Most practices are organised around something else entirely. A solo lawyer is often organised around their inbox: the work exists wherever the latest email is. A small firm is organised around people: that case belongs to a specific colleague, and its entire state lives inside their head. Document-heavy practices are organised around files: the matter is wherever the folder is, and the folder is wherever someone last saved it.

The MATTER position is that the matter itself must be the container, and everything else, every action, deadline, person, document and piece of research, attaches to it. One matter, one place, one state. If someone asks where a matter stands, the answer should exist as a fact you can look at, not a reconstruction someone performs from memory, inbox archaeology and three phone calls.

The testHand a competent stranger one matter file. Could they state its full status inside ten minutes without a single phone call?

02

AActions

Existing does not move a matter forward. Actions do, the discrete, executable steps that recur across every matter of the same type.

Here is what years of practice tend to obscure: within any given matter type, the actions repeat. Two disputes in different cities are not the same case, but they are overwhelmingly the same sequence of actions with different facts poured in. Practitioners experience this repetition as expertise, but expertise is simply an action library stored in one person, retrievable only by that person, and lost when they leave.

The MATTER position is to extract the library. Every matter type a practice handles has a describable action sequence, and that sequence should exist outside anyone's head, as an explicit, ordered, improvable playbook. Not so people become script-followers, but for the opposite reason: once the routine sequence is externalised, attention is finally free for the parts that are genuinely not routine.

The testDoes a written, ordered action sequence exist for your most common matter type?

03

TTime

Billing corrupted time. Most practices record it instead of managing it.

The billable hour turned time into revenue and, in doing so, trained an entire profession to record time rather than manage it. Meanwhile the two forms of time that actually decide outcomes go largely unmanaged: deadlines, which are absolute and unforgiving, and durations, how long each action actually takes, which nobody measures because nobody named the actions in the first place.

The MATTER position treats time as a property of the matter, not a product sold to the client. Every matter carries its dates as structured facts that surface themselves before they become urgent, and every named action accumulates duration data across every matter, permanently. A practice that knows its true durations can price fixed fees with confidence instead of fear, because pricing stops being a guess about time and becomes arithmetic on data.

The testDo you know how long your most common first draft actually takes to produce?

04

TTeam

For every action on every matter: who does it, who reviews it, who decides?

Traditional practice answers this by hierarchy and habit. Work flows to whoever is available, review happens if someone senior has time, and responsibility is discovered retroactively, usually when something has already gone wrong.

The MATTER position is that roles attach to actions, explicitly. Every action has a doer and, where it matters, a reviewer. This sounds bureaucratic until you notice what it enables: once roles are explicit, team member stops being a category limited to humans. Most organisations cannot safely delegate to AI because they never built a delegation structure for humans either, no defined doer, no defined reviewer, no explicit handoff. Who does, who reviews, who decides is the entire governance model of safe AI-assisted work.

The testCould you hand one action in the sequence to a machine and state exactly who reviews it?

05

EEvidence

The connections are the asset, not the pile of documents.

Everything asserted in matter-based work stands on something: a document, a testimony, a precedent, a fact. Evidence is the primitive of grounding, and it is, in most practices, the most disorganised primitive of all. The documents exist, thousands of them, but the connections do not. The link between one clause and the page that supports it lives in the drafting person's memory, to be rebuilt live, under pressure, months later.

The MATTER position is that the connections are the asset. Every claim in every draft should be anchored to its source, page and paragraph, as structure, not memory. A practice that does this owns something durable: its work product becomes self-verifying, and AI fabrication has a standing answer, a rule that no assertion enters work product without an anchor to a source.

The testCan you trace a specific claim in a draft back to its source document in seconds?

06

RResearch

Research is a stock, not a flow.

The traditional model treats research as an event. A question arises, someone researches it, an answer comes back, and the work evaporates. The memo serves its matter and dies in its folder. Next year, the same question arises in a different matter, and someone researches it again, from zero.

The MATTER position is that every question answered should compound into a growing, searchable body of institutional knowledge, attached to the matters it served but living beyond them. A practice that runs research this way for a few years develops institutional memory no rival can buy. Machines are extraordinary at retrieval and synthesis, which makes a well-structured research stock exponentially more valuable, and unreliable at invention, which makes grounding research in verified sources non-negotiable.

The testDoes last year's research make this year's matters faster, or did it die in a folder?

The sequence

Name. Systematise. Automate.

The order is the doctrine. Most organisations run it backwards, buying automation for practices they have never systematised, built on primitives they have never named, then blaming the tools when it fails.

01

Name

Describe the practice in terms of the six primitives. This costs nothing but honesty, and most organisations have never done it.

02

Systematise

Move each primitive out of memory and into structure. Weeks, not years, in a small practice, and it pays for itself before any AI is involved.

03

Automate

Now machines have something to grip. Agents hold parts of the sequence, people supervise all of it. That is the AI-native practice.

The maturity ladder

Four stages. One direction.

The ladder is a map, not a judgement. Most solo and small practices start at Manual or Assisted, and the climb is shorter than it looks.

Find your stage, ten questions
01

Manual

The person is the system. Everything runs on memory and habit.

02

Assisted

Tools exist, but the person is still the index holding them together.

03

Augmented

The practice is systematised and AI is genuinely in the workflow.

04

AI-Native

AI runs first on every matter, systematically. People supervise. The system measurably improves.

How the method ships

A doctrine you can install.

MatterOS

The agentic version

Agents assemble the matter and run the first pass. You supervise. 7-day free trial.

See MatterOS

LexOS

The Notion version

Run the Method yourself in a one-time Notion system you own forever, no per-seat fees.

About LexOS

Work with me directly

The installed version

For practices and organisations that need the whole model installed rather than self-served: I audit the practice against the six primitives, build the systems and agents it needs, install them into the working day, and measure the result.

See representative builds

FAQ

Questions about the Method

What is the MATTER Method?
An operating doctrine I built after nine years of watching matter-based work fail the same way, everywhere. It holds that all matter-based work decomposes into six primitives, Matter, Actions, Time, Team, Evidence, Research, and that the sequence for transforming a practice is fixed: name the primitives, systematise them, then automate them.
What are the six primitives?
Matter, the case or file as a structured container, not a folder. Actions, the named, repeatable moves that resolve it. Time, managed deadlines and measured durations. Team, explicit doer and reviewer roles, human or machine. Evidence, every claim anchored to its source. Research, a compounding stock of institutional knowledge.
Why does the order matter: name, systematise, automate?
Because machines cannot execute what has never been named. Buy AI tools for a practice you have never systematised and you get expensive chaos at higher speed. Naming costs nothing but honesty. Systematising pays for itself before any AI is involved. Automation then has something to grip.
Do I need software to use the MATTER Method?
No. The Method is a doctrine you can apply in any tool. It ships in two implementations I have built myself: LexOS, a Notion system you run yourself, and MatterOS, standalone software where AI agents do the assembling and first-pass work.
How do I know which stage my practice or firm is at?
Take the free practice maturity diagnostic: ten questions, about two minutes, scored against the definition of an AI-native operation used throughout this writing. Stages run Manual, Assisted, Augmented, AI-Native.

Start with honesty

Name your primitives.

Book an intro call