Sushi Kitchen
Solutions/Sushi Law
In practice

A kitchen that can hold a privilege.

A working law practice, running its own AI on its own hardware.

Moye Law, PC · Harrison, New York

The three constants
PrivacyLegal privilege
Memory floor
Rolls7 — every one on the menu

The memory floor is unmeasured. The slot is held rather than filled — an em-dash would read as zero to someone sizing a machine.

Read this first

Sushi Law is not on the menu. It is one firm’s deployment, built from rolls that are — and it is here because it is the clearest answer to a fair question: does anyone actually run this? The composition below is real, and every roll in it can be assembled today in the Builder.

Figures on this page hold their slots — a dotted rule the width of the number — until each one has been verified against the running deployment. Identifiers, roles and the profile are not figures and stand as written.

The constraint

A lawyer with client documents has the same problem as anyone else with documents, and one additional constraint: the documents cannot leave the building.

Every general-purpose AI assistant resolves that constraint by asking for the documents. There is no setting that makes a third-party server privileged.

So the practice either sends the file room somewhere it should not go, or it goes without the tool. Both answers are bad, and neither is a technical problem — it is an architecture problem.

What it does

On day one.

01Ask a question across the whole file room and get an answer with citations back to the source document.
02Transcribe a recorded call or hearing without the audio leaving the network.
03Draft from precedent the practice already owns, not from a model's memory of someone else's.
04Run every one of the above with the network egress closed.
Egress

Nothing leaves the network.

The box is sealed: the models run on the box, the documents stay on the box, and egress is shut rather than trusted. Caddy terminates TLS and is the only door in.

That is a verifiable fact about where the traffic goes, and it is the whole reason this composition exists. It is not a legal conclusion, and nothing here offers one.

The composition

Seven rolls, and what each one is for.

Every identifier below is a roll on the menu, resolved against the catalog rather than transcribed from a brief. The role named is the role in this deployment, not the roll’s general description.

RollRole in this deployment
hosomaki.ollamathe models, running locally
hosomaki.anythingllmthe interface documents are read through
futomaki.qdrantwhat makes a filing searchable by meaning
nigiri.whispertranscription, on the same machine
hosomaki.n8nthe routine work, automated
futomaki.supabasematters, parties, dates
dragon.caddythe edge — and the reason nothing goes out

Two of these settle a drift an earlier draft reproduced: the catalog says hosomaki.anythingllm and nigiri.whisper, and those are the identifiers printed — verified, not transcribed.

Where to go from here

The rolls are all on the menu.

Nothing above is bespoke. Open the Builder with these seven selected and the requirements resolve as you go, or read them one at a time on the menu first.

Moye Law, PC is named here as the operator of this deployment. Nothing on this page is legal advice, an offer of representation, or a claim about legal outcomes, and no attorney–client relationship arises from reading it.