Skip to content
Skip to this exploration
All explorations

Practical self-hosting · intermediate

30 · Keep the music playing when the brain is busy

Separate continuous delivery from optional AI generation.

10 min 5 sectionsv1

What you can take away

  • Design a bounded CPU-model experiment and a deterministic fallback.
  • Build a paper schedule for three fictional tracks

Your trail through this idea

Checking saved progress…

Ian requested a CPU-efficient, Mastra-powered radio on a server separate from the larger intelligence system. That was a design request, not verified evidence that such a deployment is running.

Prerequisite: complete the preceding lesson or bring its worksheet.

Mark sections complete when you choose. Reading alone does not mark them.

Understand the system

A continuous audio service has deadlines that conversational generation may miss. Separate preparation from playback: generate and validate optional announcements ahead of time, cache approved results, and provide a deterministic fallback when generation is unavailable. Mastra’s explicit workflow model is relevant to preparing work in stages; it does not by itself guarantee uninterrupted audio.

CPU efficiency should be measured against a bounded task. A short introduction may tolerate a modest model and a strict output limit. The test should include generation time, memory, power if measurable, and whether audio delivery remains unaffected. A larger model is not automatically a better radio component.

Checking saved progress…

Work through the case

Original fallback ladder: approved announcement available → use it; generation missed deadline → use approved generic station identification; identity or model service unavailable → continue the approved music schedule if the audio path remains healthy. Do not invent track rights or assume every local file is authorized for broadcasting.

Checking saved progress…

Make something useful

Try this

Original exercise

Build a paper schedule for three fictional tracks. Assign an announcement deadline, validation step, and fallback to each. Simulate a slow model and an unavailable model. The schedule must remain complete without pretending generation succeeded. If testing a CPU model, use an isolated endpoint and fake metadata, never the live broadcast queue.

Checking saved progress…

Check your reasoning

A quick check · for your own learning

What should happen when an optional radio announcement misses its deadline?

Choose one answer

A self-study prompt. You can retry; this is not an exam.

Checking saved progress…

Keep the result and follow the sources

Success is a schedule that survives optional-service failure. The practical ambition is dependable listening, not maximum model complexity.

Sources and scope

  • Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
  • Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
  • Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.
Checking saved progress…

These checks are for reflection and practice. Your answers and reflection notes are not sent anywhere.

Back to all explorations