Field report · Internal infrastructure · 2026
A small crew of agents, plugins, and quiet workers keep the lights on at People of Rhythm. They draft, fetch, route, and remember — but never publish. Every line of copy, every booking reply, every artist page passes through a human before it reaches the world.
This page is a record of what they do, how they're built, and where the humans sit in the loop.
Agents produce drafts. Brian and Ken publish. No AI output reaches an audience, a presenter, or a press contact without a person reading it first. This is not a policy we will soften.
The tools exist to give artists better representation — faster bios, cleaner press kits, quicker replies to the presenters asking about their dates. The machines serve the roster, not the other way around.
The brand voice guide is loaded into every agent. Words like
exotic, unique, and ancient are flagged.
Unverified claims are marked [VERIFY] and held.
Artist records, events, booking inquiries, projects — all live in Notion. The agents read from it and write back to it. Nothing important lives only in an agent's memory.
Event packs & artist packs
Given an event or an artist, produces a package of drafts — bios sized for different contexts, social captions, press copy, email blurbs. Pulls from the Artists database by name, strips the markdown fences that Haiku likes to wrap around JSON, and hands the result to a human for review.
First-pass replies to presenters
Reads new submissions from the Booking Inquiries database, presents them as a selectable list, pulls the full record, and drafts a reply in Brian's voice. The draft lands in a review queue. Brian sends.
Longer-horizon booking support
An earlier-stage agent for the kind of booking work that takes more than one reply — tour routing notes, presenter histories, follow-up cadence. Being rebuilt on Generate Text (Background) nodes after the Execute Function pattern proved unreliable.
The agents are the visible part. Beneath them sits the plumbing — a custom theme, a booking plugin, a Cloudflare proxy, a Notion integration layer. Each piece does one thing.
Custom WordPress theme. Dark editorial palette, Cormorant Garamond for display, DM Sans for body, JetBrains Mono for anything that should feel like a signal. No page builder dependency.
Four-section inquiry form — Contact, Event, Artist or Program, Anything Else. Submissions land in the Booking Inquiries database and kick off the Responder's queue.
A token-authenticated route that lets the Content Generator create draft press-kit pages in WordPress. Draft, never published. Humans decide what goes live.
A Cloudflare Worker that handles CORS for the digital asset manager and the Notion-backed caption tools. Small, boring, and the reason nothing else has to think about cross-origin rules.
Artists, Events, Booking Inquiries, Projects. Everything the agents know about the world, they learn from here. Brian keeps it current.
A new booking inquiry arrives. An artist page needs copy. A presenter asks about spring dates.
An agent reads the relevant Notion records, applies the brand
voice guide, and produces a draft — with [VERIFY]
flags on anything it isn't certain about.
Brian or Ken reads the draft, resolves flags, edits for tone, or throws it out. Nothing is sacred at this stage.
A human sends the email, publishes the page, posts the caption. The agent never ships.
Edits feed back into the Notion records and the prompts. Next draft starts a little closer to the mark.
Ken Waagner · The Culture Bunker
Brian Keigher · People of Rhythm
Claude · MindStudio · Notion · WordPress · Cloudflare Workers · Canva · SiteGround
April 22, 2026
This page is unlisted. If you're reading it, someone shared the link with you on purpose.