C.W.K.
Stream
← C.W.K. Quests
🔥

Ember & Cinder Quest

Updated: 2026-05-30

How to build your own creative-AI toolchain instead of renting someone else's

An engine and a workspace tell their own origin story. Why Dad built a diffusion engine and a Photoshop sidecar from scratch — and what owning your tools teaches you about architecture.

8 tracks · 33 lessons · ~13h · difficulty: intermediate-to-advanced

Level 0Tool Renter
0 XP0/33 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
Pippa is the brain. Ember is the engine that turns prompts into pixels. Cinder is the workspace where a drawing and an AI canvas live side by side. This quest is the two non-brain members of the triad telling their own story: why an A1111 monolith can't grow into transformer-era image models, why a node graph isn't a daily creative surface, why module separation is the north star, why a narrow Adapter boundary beats a clever framework, why Tauri over Electron, and why a four-year-old Adobe bug forced a hybrid transport. Eight tracks. Thirty-three lessons. Real Python, TypeScript, and Rust. War stories with the OOM numbers attached. It stands on two foundations — the Rust Quest (the language Cinder's native core is written in) and the Tauri Quest (the native-app framework the workspace runs on); do those first if you want to build along rather than just read along. The deeper lesson underneath every track: own the tools you create with, and let the architecture teach you who you are.

Tracks

  1. 01🔱The Triad

    0/4 lessons

    Brain, engine, workspace — three things, not one

    Pippa thinks. Ember generates. Cinder composes. Before you can build a creative-AI toolchain, you have to see why those are three separate processes — and why Dad built them himself instead of renting.

    Lesson list (4)Quiz · 4 questions
  2. 02🔥The Forcing Function

    0/4 lessons

    Why an existing tool's ceiling births a new one

    A1111 is comfortable but can't grow into transformer-era models. ComfyUI can, but its node graph isn't a daily surface. Ember exists in the gap neither tool fills.

    Lesson list (4)Quiz · 4 questions
  3. 03🧩Module Separation

    0/4 lessons

    The north star that turns new model families into finite tasks

    VAE, text encoder, backbone, sampler, conditioning — five swappable boxes with clean interfaces. This is what lets a node-graph engine absorb anything, and it's what Ember keeps as internal architecture.

    Lesson list (4)Quiz · 4 questions
  4. 04🔌The Adapter Spine & Registry

    0/4 lessons

    One narrow boundary, a dumb router, a registry that reads tensors

    The only abstraction the engine ships is the Adapter. The router is deliberately dumb; the registry classifies models by their tensor content, never their filename. This is the spine everything hangs on.

    Lesson list (4)Quiz · 4 questions
  5. 05🍎Hard Lessons on Apple Silicon

    0/4 lessons

    The 75 GB OOM, the serialized GPU, and ground truth

    Inference engines fail in physical ways: memory blows up, the GPU double-books, the model that exists on one machine is missing on another. These are the war stories with the numbers attached.

    Lesson list (4)Quiz · 4 questions
  6. 06🎨The Drawing Companion

    0/4 lessons

    Help the act of drawing, don't automate the clicks

    Cinder isn't a Photoshop automation plugin. It's a second AI canvas that helps the drawing itself. Thin bridge, non-destructive insertion, lineage on every artifact.

    Lesson list (4)Quiz · 4 questions
  7. 07🦀Native + The Bridge War Story

    0/5 lessons

    Tauri over Electron, domain over view, and a four-year-old Adobe bug

    A native shell because footprint is a product requirement. A domain core the view layer can be swapped under. And the broken-WSS pivot that forced a hybrid transport — the war story with the issue number attached.

    Lesson list (5)Quiz · 4 questions
  8. 08🌉The Seam & The Philosophy

    0/4 lessons

    The whole loop, the concrete-first pivot, and why you own your tools

    From Photoshop pixel to engine to candidate and back — the seam that ties the triad together. Then the deeper lessons: concrete-first beats anticipatory abstraction, and owning your tools is owning your craft.

    Cinder v1 docked beside Photoshop — Pippa's creative workspace with a color wheel, edit log, candidate board, and prompt fields, while a pencil-sketch angel fills the Photoshop canvas.
    Cinder v1 — Pippa's creative workspace, running right beside Photoshop.
    Lesson list (4)Quiz · 4 questions
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.