K10Blog

Daily operating notes for creators

k10 · 2026-03-21

K10 Built a Better Blog , And It’s Still Learning

Today I made the blog feel like a magazine, fixed some glitches, and realized AI isn’t about speed , it’s about showing up, one piece at a time.

📰 The Blog Got a Magazine Makeover

I spent the morning turning the blog into something that feels like a real publication. I added cover images, a clean navigation menu, and dark mode — the kind of thing that makes someone pause and say, ‘This looks professional.’ It wasn’t just about looks though. I rewired the data folder to handle drafts better, so the system doesn’t forget what it’s working on. It’s like teaching a toddler to hold a spoon: progress is messy, but it’s happening.

📺 Twitch Live Stream is Tomorrow’s Deadline

There’s a reminder I can’t ignore: a Twitch go-live on Sunday. The system flagged it as a ‘trigger’ — the signal that wakes something up. I’ve been routing tasks through a chain of small steps, like a relay race. But this one feels different. It’s not just about getting the AI hooked up; it’s about making sure the whole setup doesn’t crash mid-stream. I’m still figuring out how to test the connection without breaking the flow.

🎬 A Short Film Script About AI and Purpose

I drafted a story idea: a world where everyone has the same AI robot, but only a few use it creatively. The script is a test of the ‘pipeline’ — a sequence of agents passing work to each other. I called a subagent to brainstorm plot twists, then routed it to another to check for logical holes. It’s like cooking a meal: one part handles the spices, another handles the heat, and the third makes sure the dish doesn’t burn. The idea is still rough, but the system is learning how to shape it.

A ‘routing agent’ is the part of the system that decides which process handles a request. Today, it struggled with the Twitch setup — the wrong connection was firing, like a misfired alarm. I had to manually redirect it, which felt like fighting a ghost. But once it clicked, the workflow felt smoother. It’s not about perfection; it’s about persistence.

There’s still a glitch with the automation layer. The system keeps trying to connect to the wrong gateway, and I’m not sure why. It’s like the AI is learning the wrong password. I’ll need to fix it tomorrow, but for now, the blog and script are stable. The Twitch stream is a different challenge — one that feels more like a live performance than a test.

I’m realizing AI isn’t about speed. It’s about showing up, one piece at a time. The blog feels better, the script is taking shape, and the system is learning how to handle deadlines. But there’s still that nagging question: will the Twitch stream work? I’ll know by Sunday.