Production Tool, Teaching Tool — Different Species

"A DAW is a workshop for making things. A learning tool is a classroom for understanding them. Don't ask the workshop to teach."

The Idea, Pushed to Its End

Run the whole test and the result is clean: Logic fails the API condition (not buildable), Live passes the API but fails residency and the value test (buildable, wrong host). No DAW satisfies all three conditions. And the reason isn't bad luck — it's categorical. DAWs are production tools: their job is to make a finished recording. A learning tool's job is to change what's in your head and hands. Those are different species, and a production host is not built to do a teaching job.

The Collapse Back to Independence

Is Bonfire to a DAW what Cinder is to Photoshop?
  Logic: fails (2) API            -> not buildable
  Live:  fails (3) + value fit    -> buildable but wrong host
Conclusion: no DAW hosts a LEARNING tool (DAWs are PRODUCTION tools).
  => Bonfire is an independent engine with its own canvas.
  => Capo (standalone, not a plugin) is the existing proof.
  => Live stays a future *optional input adapter*, never a core dep.

The model collapses, on purpose, back to: Bonfire is an independent engine with its own canvas. This isn't a consolation prize — it's the right answer, and it already has a proof. Capo, the clearest reference for the analysis-and-practice surface, is a standalone app, not a DAW plugin. The market already voted: the learning/analysis tool lives on its own, next to the DAW, not inside it.

Keep the Door, Lose the Dependency

Independence doesn't mean ignoring DAWs forever. Live stays on the map as a future optional input adapter — when Dad is working a clip in Live and says 'show Pippa this,' a thin bridge (the music analog of Cinder) could pull the clip into the Bonfire engine. But that's one consumer among many inputs, built after v1, and never a core dependency. The discipline: take input from a DAW, never live inside one.

Code

The collapse to an independent engine·text

Is Bonfire to a DAW what Cinder is to Photoshop?
  Logic: fails (2) API            -> not buildable
  Live:  fails (3) + value fit    -> buildable but wrong host

Conclusion: no DAW hosts a LEARNING tool (DAWs are PRODUCTION tools).
  => Bonfire is an independent engine with its own canvas.
  => Capo (standalone, not a plugin) is the existing proof.
  => Live stays a future *optional input adapter*, never a core dep.

Exercise

Think of two tools you use: one for producing/making, one for learning/understanding. List what each is optimized for. Now imagine forcing the learning job into the production tool. What breaks? That breakage is the same one that sends Bonfire out of the DAW and onto its own canvas.

Hint

Production tools optimize for the finished output; learning tools optimize for the user's growth. Force one to do the other's job and you get a tool that's great at the wrong thing — exactly the DAW-as-teacher mismatch.