Sushii Story · Creator Asset Studio

Maya wants her work back under her control.

Inspect the starting Recipe →See the platform thesis →

Maya is a fictional composite: a photographer, illustrator, and family archivist used to show one human problem end to end. Her story begins with the life she is trying to organize, not with software names.

Her goal is simple.Preserve, understand, organize, and reuse the work and memories she has already created without becoming her own infrastructure team.

The human problem

Client work, illustrations, and family photographs are scattered everywhere.

Maya wants a private creative archive she can actually understand and use. She cares about preservation, privacy, provenance, search, and practical ownership more than the technology underneath them.

Photographer · illustrator · family archivist

She wants useful help without surrendering the archive.

Some files still carry camera facts and embedded authorship metadata. Some contain private location information. Some need thumbnails or derivatives. Some need better human labels. None of those needs should require rewriting the original file just to make the collection usable.

“Keep my client work and family photos organized, searchable, private, and backed up. I want local AI help, but I do not want my private images sent somewhere just to understand what is in them.”
01

Protect what already exists

Original creator files stay unchanged by default.

The system can make derivatives and sidecars, but the canonical original is preserved. Source metadata remains distinguishable from later human edits and model suggestions.

02

Keep sensitive context private

GPS and location stay private by default.

Embedded location can be useful for Maya without becoming public metadata. Privacy is a visible choice, not an invisible cleanup step.

03

Keep the person in charge

AI can suggest. Maya still decides.

Optional local intelligence can suggest captions, tags, and ways to find related work. Deterministic file facts remain facts; model inference remains clearly separate guidance.

The desired future

A studio that fits the machine and privacy posture Maya actually has.

She can begin from a complete architecture, adapt it, choose a Machine, see deterministic fit and connectivity facts, and save her own Variant. Tsugiita can explain tradeoffs later without becoming permission to use the open Kitchen underneath.

Sushii response

Creator Asset Studio

Sushii World tells the human story. Sushii Kitchen owns the executable truth: the starting Recipe, its Roll roles, provider choices, Builder, Machine fit, and optional Tsugiita guidance.

preserve originalsretain provenanceprivate locationsearchable archiveexplicit storage choiceoptional local AI
Open the starting Recipe →

Progressive disclosure · only now the technology

The Recipe is made from bounded tools with human-readable roles.

PostgreSQL keeps durable records. RustFS stores original and derivative bytes through the portable S3 path. Lychee is the creator-facing workbench. ExifTool reads embedded source facts. ImageMagick makes derivatives. n8n orchestrates workflows. Ollama and Qdrant provide optional local intelligence and semantic search.

Next step

Inspect the real Recipe in Sushii Kitchen.

The Kitchen page is a starting Recipe, not a live commercial SKU. It preserves the accepted RustFS portable default, explicit MinIO compatibility, managed Supabase alternative, and the boundary between deterministic facts and optional guidance.

Continue to Kitchen →