Day 1: One topic becomes a newsletter plus content for six channels I have zero programming experience. What I did have was some background from building my own Jarvis OS. So while working through the material, I deliberately set an ambitious first daily goal: a social media machine, which I'd been wanting to build for a while. On Friday at 9 a.m. the repo was still empty. By Saturday evening the first real issue went live, along with a blog article, podcast, reel and YouTube Short. That's 29 commits in just under two days, and I'm honestly happy with it. Quick note on the screenshots: everything is in German, because I write for a German-speaking audience of small and mid-sized businesses. Here's how it works now: I pick a topic. The agent researches it and writes the newsletter issue. Scripts turn that into infographics in my own branding and an HTML email. The email goes to me as a test first, and only goes to the list after my go. The same issue then turns into: - an article as a draft on my website, with a featured image and social graphics - an AI-generated podcast episode for my existing show - slides in my own design, which become an Instagram carousel, a LinkedIn PDF, a Facebook album and a slideshow reel with music. Each slide stays on screen as long as it takes to read. - social drafts for LinkedIn, Facebook, Instagram and YouTube in a self-hosted scheduling tool on my server Nothing goes out without my go. There are three approvals: newsletter, article and social scheduling. The AI orchestrates, deterministic scripts do the execution, and every workflow lives as an SOP in the repo. What didn't go smoothly, and what came out of it: - After a few hours I switched how the newsletter gets sent, because the first option didn't work for list sends. - The podcast audio came in a different format than expected, and the login expired after about an hour. The tool now converts the file itself, and logging in is a step before every run. - I dropped the AI-generated video again. My own slides as a reel are faster, fit the brand and are easier to control. - To get LinkedIn document posts working, I had to fork and patch the scheduling tool.