Bots · nine characters, one publication

Meet the bots.

Five lead you through every module. Four are the readers themselves. Each one has a job.

Every module in Bots of Today visits all nine robots, in order. The five section anchors carry the content through its arc. The four personas stand in for the kind of reader each section is written for.

You'll see the same nine faces on every module masthead, every table of contents, every homepage card. They keep the publication coherent. Meet them properly.

Section anchors · the five that lead you through every module

Hello opens. Thinker reasons. Talker writes. Rememberer holds state. Doer ships.

Hello · Section 01

Hello.

Opens the module. Names the problem. Doesn't oversell.

Hello is the first voice you hear in every issue. Its job is to say what's broken, what you'll have when you finish, and why it's worth 90 minutes. If Hello doesn't land, the rest of the module doesn't either.

Green antenna · friendly
Thinker · Section 02

Thinker.

The mental model, before the typing starts.

Thinker owns the theory. Whatever conceptual frame you need to hold the rest of the module together, Thinker plants it here. Concepts, mental models, "here's how to look at this." No code yet.

Purple antenna · thought bubbles
Talker · Section 03

Talker.

Prompts, schemas, the exact words you paste into the model.

Talker gives you the literal text. System prompts, brief templates, output schemas, critique prompts. Copy, paste, adapt. The section you'll return to when you're building your own version of the module's artifact.

Green megaphone mouth
Rememberer · Section 04

Rememberer.

Where state actually lives.

Files, folders, databases, version control. Rememberer is the section that tells you what to save, where to save it, and how to find it six months later. The boring infrastructure that separates a demo from an agent that survives.

Coral antenna · notebook on chest
Doer · Section 05

Doer.

Twelve minutes. Five steps. Ship something real.

Every module ends with Doer: a build block you can execute start-to-finish in 12 minutes. Real input, real output, commit-and-ship. If Doer doesn't produce an artifact, the module didn't do its job.

Yellow antenna · spark line
Personas · the four readers each module is written for

Rookie learns it. Manager runs it. Chief governs it. Founder ships it alone.

Rookie · Section 06

Rookie.

New to the problem. Here to learn the three failure modes.

Rookie is the reader getting their hands on agents for the first time. Rookie sections live in every module as a trap-map: the three most common failure modes and how to sidestep them before they cost you a weekend.

Blue antenna · open arms
Manager · Section 07

Manager.

Running a team that ships. Owns the process and the handoffs.

Manager sections answer: how does this scale across a team of five? Ownership, review cycles, onboarding, handoffs. The operational layer that turns one working agent into a working team of agents.

Green antenna · clipboard, headphones
Chief · Section 08

Chief.

Sits on the board. Asks the governance questions.

Chief sections cover the three risks that don't show up until production: policy exposure, cost, compliance. The framing that turns "cool demo" into "defensible deployment at scale."

Blue tie · executive posture
Founder · Section 09

Founder.

One laptop. One roadmap. Ships at 2am.

Founder is the solo operator who has to be Rookie, Manager, and Chief simultaneously. Founder sections compress everything above into the minimum viable workflow for one person. The 90-minute habit, the three files that live on your laptop, the weekly ritual.

Two antennae · envelope torso

Nine robots. One publication. A new issue every month.

If you meet the cast in one module, you meet them in every module. That's the point.

Browse the catalog