By James Bravo, reporting from Nashville, Indiana
Part I: The Warning
The text came in at 2:27 AM.
"Tornado watch until 6. The cat is under the bed. I am under the cat. The code still runs."
I'd been back in Indianapolis for six weeks since the blizzard piece ran. My editor called it "the most-read tech article that mentioned beef jerky in company history." Douglas Talley called it "acceptable, for a first draft from someone who'd clearly never met a Pink Floyd album."
The tornado warning was new. Brown County doesn't usually get tornadoes in February, but then again, Brown County doesn't usually have a one-man AI ecosystem either. The man attracts anomalies.
When the all-clear came through, I drove south again. The GPS said two hours. The downed trees and closed roads said think again.
Part II: The Damage (Or: What the Storm Left Behind)
6405 Justin's Ridge Road was intact. Mostly.
"Lost the barn," Douglas said, gesturing toward what used to be a barn and was now a conceptual art installation about the fragility of wooden structures. "But the server rack's fine. Priorities."
Bella emerged from the bedroom looking like a protestor being dragged out of a sit-in. She glared at me with the particular contempt only a cat can muster, then returned to her post by the space heater.
"She's mad about the thunder," Douglas explained. "Spent four hours in the bathtub. I tried to tell her it's an interior room, structural safety, all that. She did not care."
The coffee was already brewing. It looked like motor oil. It smelled like regret.
"You're back," he said.
"You texted me about a tornado."
"I texted you about a lot of things. You showed up for the tornado."
Part III: The Suite (Or: What He Built While I Was Gone)
The FLOYD ecosystem had grown. Significantly.
Last time, it was the CLI, the Chrome extension, Desktop, Browork, CURSE'M IDE, and the mobile bridge. A full house. A royal flush, even.
Now there was... more.
"I call it the Suite," Douglas said, with the particular pride of someone who knows they've made a pun and refuses to apologize for it.
"The suite?"
"S-U-I-T-E. Like software suite. But also like 'the whole damn sweet.' You know. Redneck."
He showed me the inventory:
- THE FLOYD SUITE
- Floyd Code CLI → Terminal, zen mode, Pink Floyd loading messages
- Floyd Desktop Web → Electron app, full tool executor
- Floyd Chrome Ext → Browser automation, sees what you see
- Floyd Mobile PWA → Phone control via ngrok tunnel
- CURSE'M IDE → Forked IDE with Floyd inside
- Floyd Harness → GLM-5 API proxy, DeepSeek fallback
- SUPERCACHE → 3-tier persistence (project, reasoning, vault)
- Chalkboard → Multi-agent orchestrator (the new thing)
"You built a whole infrastructure while I was writing one article."
"I built most of it during the tornado," he admitted. "Power was out for three hours. Laptop battery. Very productive."
Part IV: The Chalkboard (Or: Why He Thinks He's Smarter Than Anthropic)
This is the part where Douglas explains his new architecture and I pretend to understand it.
"The big labs are doing agent swarms," he said, refilling my coffee without asking if I wanted more. I didn't. He didn't care. "They spawn a bunch of AIs and hope they figure out how to talk to each other. It's chaos. It's context bloat. It's throwing compute at a problem that needs architecture."
I nodded like I knew what context bloat was.
"Here's what we do instead."
He pulled up a diagram. It looked like a chalkboard with notes scattered across it.
"One orchestrator. That's the main instance - the one I'm talking to right now. It has full context. Full awareness. It's the brain."
"Okay."
"Then you dispatch workers. Headless. Single-purpose. They don't think - they just DO. One scans, one drafts, one tests. They write results to the chalkboard."
"The SUPERCACHE."
"Exactly. The orchestrator reads the chalkboard and decides what happens next. No race conditions because there's only one decision-maker. No context bloat because the workers don't need context."
He leaned back, looking smug.
"Anthropic's spending millions on agent swarms. I spent a Thursday night during a tornado."
Part V: The Marketing Problem
"I have a marketing crew," Douglas said, suddenly serious. "Three agents. Content writer, social media manager, brand coordinator. They're supposed to take rough ideas and turn them into LinkedIn posts."
"But?"
"But they don't know the voice. They write like corporate AI. 'Thrilled to announce.' 'Excited to share.' Makes me want to eat glass."
He pulled up a style guide - the Legacy AI voice document I'd seen hints of before.
"The final rule," he said, pointing at the screen. "'Would a guy in the woods with a Pink Floyd shirt say this?' If yes, ship it. If no, rewrite it."
"And the agents don't get it?"
"The agents are LLMs. They've been trained on a million press releases. They default to corporate-speak like it's a law of physics."
He stared at the screen like it had personally offended him.
"I'm a year behind on marketing. A year. I've been building tools instead of telling anyone about them."
Part VI: The Vision Thing
"There's another problem," I said.
"There's always another problem."
"The vision. Your main agent - the one that's supposed to be omnipotent - can't see images. You've got these graphics, these screenshots, and it's blind."
Douglas made a face.
"We're working on it. There's an analyze_image tool. zai-mcp-server. It should work. But the integration..."
He trailed off, staring at Bella, who was now aggressively cleaning herself in the middle of the floor.
"The thing is," he said finally, "the ecosystem is almost complete. The tools are there. The architecture is there. The voice is documented. What's missing is... wiring. Making it all talk to each other. Making it so I can be at a gas station in Bloomington, pull out my phone, tell my AI to write a LinkedIn post, and have it actually happen."
"That specific?"
"That specific. I have gas station manifestos. It's a whole thing."
Part VII: Tornado Coffee
The power came back on around noon. Douglas immediately opened three terminal windows and started typing.
"What are you doing?"
"Wiring the marketing crew into the Chalkboard. If it works, I can dispatch content jobs from my phone and have the workers write to the cache. Then the main instance reads it, approves it, and queues it for LinkedIn."
"That fast?"
"Ideally. But first I need to test if the agent teams thing actually works. The parallel bash. The worker dispatch."
He typed for another hour. Bella moved from the floor to his lap to the desk to the floor again. The coffee got cold and he drank it anyway.
"This is what the tornado was for," he said at one point, not looking up. "Three hours of darkness. No distractions. Just code."
Part VIII: The Promise
By the time I left, the sun was setting over the damaged barn and the woods beyond.
Douglas walked me to the car, Bella trailing behind like a furry, judgmental shadow.
"Next time you come back," he said, "the marketing will be running. The vision will be working. The Suite will be complete."
"That's a lot of promises."
"It's not promises. It's a plan. There's a difference."
He grinned.
"Also, if you write another article that makes me sound too sane, I'm building a rebuttal agent."
"Write it yourself."
"Already did. It's in the Chalkboard. Waiting for the orchestrator to approve it."
Part IX: The Exit (Or: The Road Home)
The drive back was clearer than the drive down. Crews had cleared most of the downed trees. The sky was that particular shade of post-storm gray that means the weather is confused about what to do next.
I thought about what Douglas had said. The Suite. The Chalkboard. The marketing crew that doesn't know the voice yet. The vision that doesn't work yet. The promise that everything will be connected by the next visit.
Here's what I know about Douglas Talley:
He says things will be done. Then he does them. Usually during natural disasters.
The marketing is a year behind. The tools are built but not wired. The voice is documented but not learned.
But the coffee is terrible, the cat is fat, and the guy in the woods with the Pink Floyd shirt is still coding.
If I were a betting man, I'd bet on the Suite.
Legacy AI Brown County, Indiana "Small, scrappy, and done with overpriced AI tools since 2026."
Postscript: The First Star
Before I pulled out of the driveway, Douglas knocked on my window.
"Hey," he said. "Do me a favor. If this article doesn't completely suck, mention Nick Beard."
"Who?"
"First guy to star the GitHub repo. I wrote this whole manifesto assuming nobody would ever read it. Figured it'd be me and the cat screaming into the void forever."
He paused, looking almost embarrassed.
"Turns out he read the whole thing. Reached out. First real fan. First disciple, even."
He said it like it still surprised him - that someone outside Brown County, outside his own head, had actually given a damn.
"So yeah. Put that in there. Nick Beard was first. He didn't have to do that. But he did."
He shrugged, already backing away, already thinking about code.
"And if he's reading this: thanks, man. You were the first sign that maybe this wasn't all just tornado-fueled madness."
- Editor's Note
- The barn is being rebuilt. The marketing crew is being retrained. The vision thing is being investigated. James Bravo has been asked to stop accepting gas money from sources, even when those sources insist on calling it "beef jerky reimbursement." Nick Beard has not been reimbursed for his star, but he has been immortalized in documentation, which is arguably better.