Memo Casting is the authorial voice layer of 📝MythOS Newsletters. Where newsletters distribute memos automatically based on topic and threshold, Memo Casting gives creators two deliberate publishing tools — preambles and broadcasts — for the moments when you want to speak directly to your subscribers rather than let the library speak for you.
Preambles
A preamble is a short, creator-written introduction that appears at the top of subscriber digests. Think of it as a letter to your readers: context for what you've been working on, a note about what's coming, or a reflection on what the week's memos mean to you.
How It Works
- Write — compose your preamble in the same rich editor used for memos, with full support for mentions, hashtags, formatting, and links
- Save draft — drafts persist between sessions. Edit as many times as you want before publishing
- Publish — publishing archives the current preamble, clears the editor, and increments the version number. Subscribers receive the new preamble in their next digest — and only once, because the system tracks which version each subscriber has already seen
- History — every published preamble is archived with its version number, title, and publication date. Browse prior versions and copy any back into the editor to use as a starting point
Preambles are version-tracked per subscriber. If a subscriber receives a weekly digest and you publish two preambles that week, they see the most recent one. If they've already seen the latest version, the digest arrives without a preamble — no repetition.
Broadcasts
A broadcast is a standalone email sent directly to subscribers, independent of your memo publishing activity. Use broadcasts for announcements, event invitations, personal updates, or anything that doesn't belong in a memo but belongs in your subscribers' inboxes.
How It Works
- Compose — write your broadcast with a subject line and body using the full rich editor
- Choose your audience — send to all subscribers or narrow to a single topic. Subscribers who have opted out of broadcasts are automatically excluded
- Preview — see a recipient count before sending so you know exactly who will receive it
- Send — delivery happens asynchronously. The system batches emails and logs every send for your records
- History — every broadcast is tracked with its subject, audience, send date, and recipient count. If a send stalls, a retry option appears automatically
Broadcasts respect subscriber preferences at every level. A subscriber who follows your "AI" topic but not "Philosophy" only receives broadcasts targeted at AI. A subscriber who has disabled broadcasts receives nothing, regardless of targeting.
What Makes It Different
Most newsletter platforms force a choice: either you manually compose every issue, or you set up an automated feed. 📝MythOS doesn't make you choose. The automatic newsletter handles distribution of your knowledge work. Preambles let you add a human voice to those automated digests. Broadcasts let you reach subscribers on your own terms, on your own schedule. All three — automatic delivery, preambles, and broadcasts — coexist in the same system, use the same subscriber lists, and respect the same preferences.
Related
- 📝MythOS Newsletters — the automatic newsletter system that Memo Casting extends
- 📝My Omakase Newsletter — Brian's newsletter concept built on MythOS
The original version of Memo Casting was duct tape — Clay scraping memos, Make stitching context, external tools doing the thinking. It worked well enough to prove the concept: that my library could generate 📝Contextually Augmented content with minimal oversight. But the seams were everywhere. Now the entire flow is native. The preamble is where I talk to my subscribers as a person, not as a content machine. The broadcast is where I reach them on my terms, not on a schedule dictated by when I happened to publish a memo. The library still does the heavy lifting — Memo Casting just gives me a microphone when I want one.