Wrapped software rolls. Useful bento boxes. A jubako of connected systems.
A visual guide to Sushii Kitchen, Sushii Legal and Sushii Deck, and the contracts that let their components work together.
Sushii KitchenSushii LegalSushii Deck
19 slides · Arrow keys or Next · Interactive examples inside
Product direction and proposed architecture. Implementation status appears near the end.
The ecosystem
Three workspaces, shared foundations
Each workspace owns a different kind of work. References and permissions carry the context between them.
Sushii Kitchen
Choose software, compose systems, develop applications and operate them.
Owns: system blueprints, configurations and installed state.
Sushii Legal
Build and use legal workflows with matter context and substantive review.
Owns: matter records, domain decisions and legal work product.
Sushii Deck
Assemble explanations, visual materials and briefings for people and agents.
Owns: briefing revisions, renditions and review history.
The Sushii connection surfaceIdentity · Capabilities · Artifacts · Jobs · Source references
Wrapped software supplies the capabilitiesModels, document processing, databases, developer tools and other supported components.
Sushii Sourcing records what is insideArtifact identity, license evidence and provenance tied to a wrapper release.
Sushii World supplies the umbrella brand and navigation. “Law” versus “Legal” remains an open product naming decision.
The people
One architecture, three starting points
The entry point changes with the task. The same wrappers, system records and briefings support the work.
Build a tool for your own practice
Start with a document workflow and adapt its forms, prompts and outputs without hand-wiring the infrastructure.
Result: an editable local application and a source-linked briefing ready for attorney review.
KitchenCompose the parser, local model, retrieval store and editable app.
LegalApply matter permissions, domain instructions and substantive review.
DeckExplain the result with source references, visuals and open questions.
SourcingKeep the application’s software and model evidence attached to the selected versions.
Lawyer builders
Adapt a document workflow into an application for the practice.
Kitchen supplies the system. Legal owns matter context and conclusions. Deck holds the explanation and review.
Outcome: an editable app with a reviewable briefing.
Local AI users
Choose a workflow that fits the actual machine.
Kitchen plans model and service connections. Sourcing tracks downloaded software and models. Deck explains the configuration.
Outcome: a reproducible local system.
Software developers
Build locally and understand the software being incorporated.
Kitchen supplies the development environment. Sourcing captures exact versions and license evidence. Deck communicates the decisions.
Outcome: code plus a traceable software inventory.
These are proposed workflows. Legal participates when the task needs a legal domain workspace.
The roll
The outer wrapper makes the roll connect
The filling represents upstream software. The outer Sushii wrapper adds the declared interfaces, adapters and evidence that let it participate in a system.
Nori is the visual stand-in for the integration envelope. Every software family can carry a wrapper, including sushi forms without an outer nori sheet.
Connection pointsWhat the roll provides, what it requires and which interface versions fit.
Adapters and configurationHow the upstream API and runtime connect to Sushii’s contracts.
Lifecycle and permissionsHow the integration starts, stays healthy and uses approved resources.
Versioned sourcing evidenceWhich exact software and license records travel with this release.
A wrapper release is fixed. A running instance binds that release to a workspace, configuration and credential references.
The bento box
Different rolls, fitted into one useful package
A bento box packages a composed system. Its compartments represent typed connections and explicit boundaries around the components.
Select a numbered compartment. The different food forms make different component families visible.
Compartment 1 · Hosomaki
Local inference
A model engine and its supported interface can work together as separate rolls. The wrapper declares the operation contract that an application may call.
Several families, one composition
Hosomaki: inference. Futomaki: data. Nigiri: interfaces. Uramaki and temaki: visual and workflow capabilities. Each selected roll retains its own release identity.
The box has a system lock
Exact wrapper releases, artifact versions and bindings describe what belongs inside. A compartment accepts only compatible contracts.
Roll: 1 componentCombo: 2–4 rollsPlatter: 5+ rollsBento box: packaging form
The jubako
Bento boxes stack into a larger system
The jubako makes composition visible at the next scale: separately packaged systems connected through declared interfaces.
Top box · Explain
Briefing and review
Deck receives permitted artifacts and source references. It keeps the narrative, renditions and review history.
Middle box · Apply domain work
A legal application
Legal uses document and model capabilities while retaining matter scope and substantive decisions.
Foundation box · Supply capabilities
Local AI and development
Kitchen assembles inference, data services and an editable application from supported rolls.
Between the boxes: explicit exports, required interfaces, scoped access and revision references.
This is an illustrative composition across workspaces. A box can change independently when its exported contract remains compatible. State and data migrations still need a plan.
The common contract
What every connection needs to say
The connection surface is the set of contracts that lets a component be found, configured, invoked and understood.
Surface
Declared information
Why it matters
Discovery
Capability, owner, instance and availability
Find the right candidate.
Interface
Contract ID, version, operations and schemas
Know whether the two sides fit.
Binding
Endpoint, configuration mapping and credential reference
Wire only the chosen connection.
Permission
Workspace scope, allowed artifacts and data destinations
Keep authority explicit.
Execution
Job state, request ID, timeout, cancellation and typed errors
Track the real outcome.
Artifacts & context
Source locators, revision IDs and output references
Carry results into another workspace.
Lifecycle & evidence
Health, upgrades, exact versions and sourcing snapshot
Understand what is running and why.
Interactive connection inspector
A shared label is only the beginning
This document app needs a particular vector-store interface. Change the provider to see how the proposed contract check works.
Consumer: document app
Slot
vector_store
Capability
cap.vector-db
Contract
qdrant.http
Version
>=1.0.0 <2.0.0
Features
Collections, upsert, query
Provider: selected instance
Capability
cap.vector-db
Contract
qdrant.http
Version
1.0.0
Features
Collections, upsert, query
Contract match
The declared contract, version and required features match. Runtime readiness and permissions still need verification.
Resolved endpoint http://vector-db-01:6333/
Scoped credential reference vector-db-01/client-api-key· injected at apply time
Illustrative contracts and fixtures only. This interaction performs no network request or installation.
How differences are handled
Adapters translate at clear boundaries
A shared interface keeps the workspace stable while an adapter handles the details of a particular provider or runtime.
01
Runtime adapter
Maps a system plan onto Compose or an explicitly supported host service. Checks readiness and reconciles interrupted work.
The originating workspace keeps ownership of the underlying system or matter.
Software provenance and licensing
The evidence travels with the wrapper version
Sushii Sourcing answers: what software did I acquire, which exact bytes did I receive, and what licensing evidence supports that release?
Artifact identity
Origin, upstream version, source revision, full digest and platform. Models and dependencies need their own identities.
Inventory & evidence
Included packages, license text, notices, scanner version and explicit coverage gaps.
Reviewed interpretation
Declared and detected licenses, reviewed conclusions and an assessment for the intended use.
Release snapshot
An immutable evidence snapshot attached to the exact wrapper release, available to systems and briefings.
Wrapper 1.2.0 + snapshot A
The existing release keeps the evidence it shipped with. Later findings can reference it without rewriting its history.
Wrapper 1.2.1 + corrected snapshot B
A published evidence correction creates a superseding release, even if the upstream software stays the same.
Track by default. Optional project policies can warn or enforce. Unknown evidence remains visible, and an inventory does not itself establish license clearance.
The platform underneath
Shared services with clear owners
Workspaces can reuse identity, storage and execution records without creating competing sources of truth.
IdentityShared organization and project context, with resource access checked for every workspace.
ArtifactsAddressable outputs and source references. Each domain retains responsibility for its records.
JobsDurable operation IDs, progress, results and recovery through shared contracts.
GenerationModel and image capabilities available through task-specific interfaces in the relevant workspace.
RegistryCurated wrapper releases and capabilities, separate from the supervisor’s observed installations.
NavigationOpen another workspace with the project, selected revision and return location intact.
Existing commerce boundaries remain: Medusa owns commerce orchestration. Payload owns editorial catalog content. The application and Supabase own wallet accounting and entitlements.
The pieces together
A lawyer builds a document review tool
Follow the records through the workspaces. Each handoff preserves the responsible owner and the source revision.
01 · Kitchen
Assemble
Choose the parser, local model, retrieval store and editable app. Review the connections and apply the system.
Output: app revision, system lock and runtime receipt.
02 · Legal
Use and review
Work with authorized matter documents. Inspect the evidence and refine the domain analysis.
Output: work product, source locators and review questions.
03 · Deck
Explain
Build a briefing with citations, diagrams and an interactive explanation. Collect review on its revision.
Output: human rendition and agent context package.
Across the workflow
Trace
Sourcing links selected software and models to their exact versions, evidence and outstanding findings.
Output: referenced release snapshots and acquisition records.
The return path: application changes go to Kitchen. Substantive changes go to Legal. Deck keeps the explanation and review history aligned.
The Sushii proposition
What makes the whole experience distinctive
The value comes from maintaining the connections across the entire workflow.
Composable software with declared fit
Recipes resolve typed connections and tested capabilities into an explainable system plan.
License evidence tied to what ships
Sourcing follows the wrapper release, its artifacts and later findings through the system’s history.
Focused workspaces with shared context
Building, legal work and briefing review each have a clear home and an explicit handoff.
Local operation that remains understandable
Users can inspect the code, machine requirements, connections and records behind their workflow.
These are proposed product differentiators. The presentation does not claim that no other platform uses these individual patterns.
What exists and what comes next
A foundation, a contract, then one complete workflow
The reports establish a design and a source audit. They do not establish a deployed Sushii wrapper runtime or integrated Deck workspace.
Existing foundation
Catalog and composition code
The pinned audit found a catalog, composition generator, delivery boundaries and early capability metadata.
Audit boundary: repository commit 109f4c5e…. This is not a fresh production verification.
Proposed next layer
Wrapper and connection contracts
Versioned releases, typed bindings, exact artifact locks, sourcing snapshots and a local supervisor.
Draft schemas and examples exist as design artifacts. The fixtures do not install software.
First implementation proof
A useful local application
Compose inference, parsing and retrieval. Edit the app. Capture its sourcing evidence. Explain and review a revision in Deck.
Then prove a compatible provider change, a wrapper update and recovery from an interrupted job.
The first milestone should prove the connections in one real workflow before extending the same promise across the catalog.
Reference
The source material behind the model
Your latest direction governs the product boundaries. The earlier documents supply the architectural detail and historical context.
Current product direction
Sushii World branding, the Sushii wrapper, Deck as a context and briefing workspace, and the three audiences with versioned license metadata, and the roll / bento box / jubako visual model.
Accompanying conversation · September 2026
Sushii World and Deck report
Product responsibilities, the versioned briefing, human and agent outputs, review rules and shared services.
sushii-world-and-deck-report.docx · sections 2–9
Wrapper engineering report and appendix
Release identity, typed bindings, adapters, the local supervisor, sourcing snapshots and implementation sequence.
The composition model defines roll counts and bento-box packaging. The Menu v1.1, Sushi Stack narrative and Ultra-Light Systems Project Bible inform composition and evidence ownership.
Supplied project material · historical design context
Still to decide: the Law/Legal naming split, the first supported machine and recipe combination, and the exact scope of the first Deck release.
Watercolour illustrations show the metaphor; editable labels define the mechanism. Use Notes for slide-level sources and technical qualifications. Read all opens a continuous view. This file’s interactions work offline; it contains no live system connections.
