i built a content brain for my newsletter

My content agent spent the last few months building something I didn’t have before.

Not content. Infrastructure.

Most content falls apart because the creator starts from blank every time. Open a draft, stare at the cursor, try to remember what your voice sounds like. Then write something that’s 70% you and 30% whatever came out that morning.

I wanted something different. So I had my AI agent build a content operating system. A set of files that holds my voice, my stories, and my angles so the agent can read them before it writes anything.

Here’s what’s in it:

a brand voice file. Not “be clear and direct.” Specific. Every word I never use: leverage, holistic, furthermore, robust. Every formatting habit. The phrases that sound like me versus the ones that don’t. The checklist the agent runs before anything ships.

a topics queue. Eleven angles on AI-native building that are ready to write right now. Each one has a specific claim, a hook formula, a suggested platform, and the stories that back it up. I don’t start from blank. I pick from a queue I trust.

a story library. Ninety-plus atoms from things I’ve actually done, said, or built. Tweets, podcast episodes, voice memos, newsletter issues going back years. Each one tagged with what it proves, which platform it fits, and whether it’s safe to share publicly.

The whole system lives in text files. No tool, no SaaS, no subscription. Just a directory of markdown files the agent reads before it writes anything.

What changed: the agent stopped guessing what I sound like. It reads the system, follows the rules, produces a draft I can actually work with instead of rewrite from scratch.

The content I’m sending you now comes through this system.

There’s a version of this that every founder who publishes regularly should have, not just so the writing is consistent, but because it forces you to think clearly about what you actually want to say. The topics queue alone changed how I plan content, because it made me pick angles in advance instead of reacting to whatever felt relevant that week.

I’ll keep showing how this works. The setup, what breaks, what it actually changes when you run a content operation through an AI agent instead of a content calendar and good intentions.

---