About
What this is, and what it is not.
Backbone Legal turns a law firm’s approved systems into governed APIs and Model Context Protocol tools, so permitted people and AI assistants can work through firm-defined boundaries rather than around them.
Backbone Legal provides technology implementation and integration services. It is not a law firm and does not provide legal, ethics, or compliance advice.
Why this exists
Permission was solved once. Then automation went around it.
A firm’s knowledge is already digital and already governed, just not in one place. Documents sit in one system, matters and contacts in another, time and billing in a third, intake somewhere else again. Each of those has its own permission model, and each has been configured over years by people who understood why a particular partner should not see a particular matter.
Automation tends to bypass that work rather than build on it. A point-to-point integration copies data sideways; an assistant given broad credentials sees more than any single person is meant to. Both create a second, weaker version of a permission model the firm already got right once.
The alternative is to expose capability rather than access. Instead of a connection to a system, the firm publishes a named action with stated inputs, stated authority, and a stated failure behavior. An assistant that can file a document into an approved matter is a different proposition from an assistant that can read the document store.
Operating principles
Four commitments, every engagement.
- 01
Identity is not permission
Knowing who is asking is the start of a decision, never the whole of it. Every tool states the authority it needs separately from the identity it accepts.
- 02
Scope is explicit
Client and matter boundaries are carried on the call, not inferred from a folder path or a job title. If the scope cannot be stated, the tool does not ship.
- 03
The final deny stays local
The system that owns the record makes the last call, including revocation. Nothing in this layer can talk a system of record out of a refusal.
- 04
Evidence is bounded
Enough operational record to review what happened, without moving privileged content into general telemetry.
Where this stands
In formation, and saying so.
The honest version of a new service is a list of what exists and a list of what does not. Both are below, and both will change.
What exists today
- The enablement method, and the design work behind each of its four steps.
- Tool contract shapes that name inputs, outputs, authority, evidence, and failure behavior.
- This public site, and the people who would run a first engagement.
What does not
- A shipped connector or integration for any named legal system.
- The firm-facing white-label application. It is a separate, later product surface.
- Customers, case studies, reference firms, or usage figures of any kind.
- A compliance certification, attestation, or audit report.
Boundaries
What this is not.
- A law firm. No legal, ethics, or compliance advice is given here or in an engagement.
- A system of record. Nothing here becomes the authoritative copy of a document, matter, or ledger entry.
- A replacement for a document or practice management system.
- An insurer of professional responsibility decisions. Those stay with the firm and its supervising lawyers.
Build the first governed capability
One workflow you would trust an agent to touch.
The method is the same whether the first capability is read-only lookup or a bounded filing action. What changes is which system owns the record.