Garnet Law

Privileged material stays on the appliance.

A legal document appliance that runs on the same machine as the rest of Garnet.

running on our reference machine · not yet shipping

Garnet Law, surface by surface: the matter's documents with their protective-order markings, a question put to them in plain English, an answer shown beside the passage it came from with its Bates number and page, the same question asked of a record that cannot support it and refused with its four checks, and the production gate, where a passage is blacked out of the copy that leaves with nothing behind the bar to uncover, and the firm's own wording is checked before anything goes.

Privileged material stays on the appliance.Stored on it, questioned on it, answered on it.

The record arrives.Fifty-five documents, seven custodians, forty-six email-and-attachment families.

You see only what you are allowed to open.The rest stay out of view — not greyed out, absent.

You say how they are marked.The appliance reads them and never guesses a marking.

And it never lowers one for you.Open to the case team. Confidential. Attorneys' eyes only. Source code.

It reports what happened to every single file.Loaded, skipped, or failed — each one named.

Then you ask a question.In plain English, of the documents you are allowed to open.

It answers.Drawn only from the record in front of it.

And it shows you where the answer came from.One source. Not a summary of several.

The passage it matched.Bates number, page, line — and the designation that governs the document.

Read it yourself.The cited sentence, highlighted in the page it came from.

A human check is still required.A citation can land on the wrong document.

Now ask it something the record does not support.

Nothing in the record supported an answer.Not an error. A result.

It searched the documents in scope for you.And no passage cleared the relevance floor.

The model was never called.So nothing was drafted, and nothing was guessed.

A refusal is logged like any answer.The stop is in the activity log, the same as a result.

And when something does leave the firm —

— it checks the wording first.Black out a passage so the words underneath are truly gone, or check what you are about to send.

Including our own words.“air-gapped” becomes “offline by architecture”. “guarantees” becomes a qualified statement.

Nothing leaves unchecked.The matter shown throughout is a synthetic demonstration — no real client, no real document.

Demonstration. The matter, the documents and the markings shown are synthetic — no real client, no real document.

Where it actually is

A reference design, running.

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.

It runs today on our own reference machine. What does not exist yet is a hardened, shippable image, a support arrangement, and a first customer.