Sushi Kitchen
Solutions

Start from what you do.

The menu is 93 rolls and 26 compositions, and browsing it is a fair amount of work before you know whether any of it is for you. These three start at the other end — the constraint you are already bound by — and resolve to a bento box you can read before you run it.

In practiceNot on the menu

Sushi Law

A kitchen that can hold a privilege.

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

One firm’s deployment, built from rolls that are on the menu. It is here because it is the clearest answer to a fair question: does anyone actually run this?

How it is built
The deployment
PrivacyLegal privilege
Memory floor
Rolls7 — every one on the menu
DutyAttorney–client privilege
OperatorMoye Law, PC · Harrison, New York
On the menu

Two compositions, ready to run.

Both are platters already on the menu. Every roll in them is pinned to a version, with its licence read at that version rather than recalled from memory.

For consultants and researchers

Knowledge work

Documents you can question.

Anyone whose work product is an answer drawn from documents they were trusted with.

The research is done. It is spread across four hundred PDFs, six years of notes, and a folder called final-FINAL-v3. The tools that could answer in seconds all want the documents uploaded to somebody else’s account first.

Privacy
Business-confidential
Memory floor
Rolls
8
On day one
01Point it at a folder and ask questions of everything in it at once.
02Get answers with the source document and page attached, so the citation is checkable.
03See what the stack is doing — memory, latency, cost — on a dashboard rather than by guessing.
04Move the whole thing to a different machine by copying one file.
See the compositionOpen in the Builder
For studios and publishers

Content intelligence

An archive that answers back.

Anyone sitting on years of video whose best material is inside it and unfindable.

There are eleven hundred hours of published video, and the best forty minutes of it are somewhere in the middle of episode 214. Search on a video platform searches the title. It does not search what was said.

Privacy
Business-confidential
Memory floor
Rolls
6
On day one
01Transcribe the whole back catalogue and keep the transcripts as a searchable asset.
02Ask what was said about a topic across every episode and get timestamps back.
03Surface recurring themes and who said them, across years rather than episodes.
04Feed clip selection and repurposing from the same index instead of scrubbing by hand.
See the compositionOpen in the Builder
In the workshop · starting Recipe

Creator Asset Studio

Start with your photographs and artwork: preserve the originals, recover the metadata already inside them, organize the collection, make derivatives, and add local search or AI only where it helps.

Inspect the starting RecipeOpen in the Builder
Launch menu + workshop

Nine rolls, or ninety-three.

A roll is one service. A bento box is rolls collected into one logical container — a combo when it is two to four, a platter when it is a whole system. Solutions are bento boxes stacked — a jubako. What arrives is that box, sealed and versioned, running with one command and happy offline.

The accepted launch solutions remain unchanged. Creator Asset Studio is visible separately as a starting Recipe: inspectable and adaptable in Builder, but not represented as a live commercial composition.

Browse the menuOpen the Builder

The workshop label is deliberate. A canonical Recipe can be real source without being a product listing, deployment authorization, or commerce projection. The remaining gates stay visible on the roadmap.