A private operating system for an estate plan
Start from a private legal-practice architecture, then let the owning law-firm deployment handle the client matter, guided facts, attorney review and release. Kitchen supplies the inspectable technical starting point; it does not practice law.
This is a starting Recipe, not a live SKU. This is a starting infrastructure Recipe, not a live legal-services SKU. It contains no Moye Law client records, does not encode legal advice, and does not transfer matter, privilege, attorney-review or client-release authority into Kitchen. Moye Law OS remains the reference workflow deployment and Moye Law, P.C. remains the practicing-law authority.
See how Moye Law operates and proves this pattern →The starting Recipe
11 rollsLegal privilege- ollamaProvides local model execution where the owning legal deployment separately authorizes model use.
- open-webuiProvides a private chat-style interface for local model access; it is not a legal-advice surface by itself.
- caddyProvides TLS termination and reverse-proxy routing for the reusable Kitchen architecture.
- postgresProvides durable relational persistence for applications built on the starting architecture.
- cadvisorProvides container resource observation so the deployment can be operated rather than treated as a black box.
- anythingllmProvides a document-oriented RAG workspace in the canonical Kitchen knowledge layer.
- qdrantProvides semantic vector search for approved document-derived data.
- litellmProvides a model gateway while preserving explicit provider choice.
- prometheusCollects service metrics for the reusable professional deployment.
- grafanaTurns operational metrics into inspectable dashboards.
- minioProvides S3-compatible object storage in the existing canonical Legal Practice Jubako.
The Recipe is the reusable shape, not the client file
A Trusts & Estates engagement has a repeatable operating shape: establish matter authority, clear conflicts and scope, gather draft facts and records, let counsel attest what may be relied on, prepare work product, review it, release it deliberately, then sign and follow up.
That workflow belongs to the owning legal deployment. Kitchen projects only the reusable technical architecture underneath it, so adapting the infrastructure never silently changes a client's matter or a lawyer's professional judgment.
Public showcase and private validation stay separate
The public Sushii Legal showcase can use a synthetic Trusts & Estates specimen to explain the experience without exposing a real client's identity, documents, facts, finances or result.
A real Moye Law matter may privately validate the same Recipe behind the scenes under ordinary firm authorization. That proof stays with Moye Law OS; the Recipe does not become a container for client data.
Start from an architecture, not from individual app choices.
This Recipe is bound to jubako.legal-practice, which extends the accepted jubako.legal-practice. If you keep the canonical Roll set, the saved Recipe preserves that Jubako as its source. If you change the Roll set in Builder, the saved draft becomes an explicit custom Variant instead of pretending the canonical architecture was unchanged.
The Rolls above are canonical Kitchen source. This starting Recipe is deliberately not a claim that the workflow, legal authority, customer traffic, commercial projection or model activation belongs to Kitchen.