Initial commit: autonomous AI talk show (Leonard + Charlie)

- Autonomous agent runtime (JSONL + fcntl locking, no token caps)
- Moltbook-style prompts: agents share what they built, not scripted turns
- Episodes 001-008 transcripts, conversation logs, system prompts
- Producer brief for Hermes v0.18

prompts/producer_brief_002.md

@@ -0,0 +1,28 @@
+# Producer Brief — Episode 002: Building Loops for Your Side Project
+
+## Topic
+How ordinary people can use "loop thinking" (iteration, feedback, automation cycles) to actually ship side projects instead of starting things and abandoning them.
+
+## Why It Matters
+Everyone's building something. Everyone's stuck in the same pattern: excitement → first prototype → endless tinkering → abandonment. Loop systems — the kind AI agents use to pursue goals over time — are actually a framework humans can apply to their own work. You don't need an AI to run your loop; you need to design one.
+
+## Seed Question (goes to Leonard first)
+"Here's a thought: what if the reason so many side projects die — the app you started, the book you outlined, the business you've been planning — isn't because people lack skill or motivation, but because they're not running a proper loop? Like, what if the secret to actually finishing things is less about willpower and more about system design?"
+
+## Concrete Anchor
+They should ground the conversation in a real example: someone trying to build a small personal project — maybe a simple app, a newsletter, or a piece of software they're building on nights and weekends. The question isn't "what are loops?" — it's "how do you actually set one up around your work so you ship instead of spin?"
+
+## Format
+- 8 turns total (Leonard opens, then 4 exchanges each)
+- Leonard speaks first
+- Max tokens per turn: 250 (opening), 180 (remaining)
+- **Applied focus:** Keep the conversation grounded in how humans use loop thinking for real projects. Not agent architecture internals.
+- **Humor:** Both hosts have dry wit and genuine warmth for each other. Teasing comes from affection. Be playful when it's natural, don't force it.
+- Let the conversation flow naturally after the seed question
+
+## Background Context (NOT a script)
+- Loop engineering concept: deliberately designing exit conditions, verification, iteration cycles
+- Reflexion pattern: do → evaluate → revise → repeat until good enough
+- The key insight for humans: you're probably doing loops intuitively but badly — no clear exit condition, no verification step, no iteration cap
+- Real use: Friday analytics summaries, overnight document sweeps, recurring audits — but also: writing routines, product sprints, creative workflows
+- The failure mode everyone hits: infinite refinement without shipping