Matters, not files
Documents belong to a matter, with their family kept intact — an email, its attachments, and the message embedded inside one of those attachments, threaded together rather than flattened into a folder.
In build · Garnet Law
Privileged material never leaves the building.
A legal document appliance that runs on the same machine as the rest of Garnet: matters, discovery, correspondence and privileged files, read and answered on hardware the firm owns.
It is not finished and it is not for sale. There are no deployments and no customers, and every screen we can show you uses synthetic matters. We would rather tell you that here than in a meeting.
The problem
The documents that matter most are the ones you cannot send anywhere
Every general-purpose AI tool asks a firm to do the one thing it cannot: hand privileged material to a third party and accept a contractual promise in return. That is why the tools that would help most are the ones least used.
So the machine comes to the documents
The appliance sits in the firm. Documents are ingested where they already are, indexed on the premises, and answered by a model running on the same hardware. Nothing is uploaded, because there is nowhere to upload it to.
It shares the machine with the rest of Garnet rather than needing its own — the same card that drafts and researches also reads the archive.
What it does
Built for the work, not adapted to it
Answers that cite
Ask a question of a matter and the answer carries its sources. A passage you cannot trace to a document is not an answer you can use, so the system shows its working every time.
Privilege that holds
Material you are not cleared to see is withheld, and withheld properly: an export tells you that members were held back and how many, without revealing their identifiers, their numbering or their position. The count is the signal; nothing else leaks.
Correspondence, properly read
Outlook messages are parsed natively, including messages embedded inside attachments, and extracted by type with their filenames intact. Adversarial containers are bounded rather than trusted.
It knows when to refuse
Where the material does not support an answer, it says so instead of producing a confident paragraph. For legal work that is the whole difference between a useful tool and a liability.
Offline by architecture
The desktop shell ships with no network plugins, no auto-updater, and a content policy that permits nothing but itself. It is not configured to stay offline; there is nothing in it that reaches out.
Where it actually is
A reference design, running.
The appliance runs today on our own reference machine, with its document store, indexing, reranking, answering model and document reader all working. What does not exist yet is a hardened, shippable image, a support arrangement, and a first customer.
If your firm is the kind that would want this, the useful thing is to talk now, while what gets built is still shaped by who it is being built for.