Four AI Bot Charters Worth Building (Not Ten)

Before naming a "CEO bot" or a "CMO bot," build charters for jobs that actually exist in a product studio: a Design System bot, a Prototype bot, a Bug Repro bot, and a Launch Page bot. Each one has a narrow domain, a stated publish surface, and a human who signs off — the same handoff grammar a studio already uses for people.

Design System

Prototype

Bug Repro

Launch Page

The charter template

Every charter answers three questions, the same way you'd brief a new hire on day one:

1. What it owns — the specific, narrow domain, stated as a recurring responsibility.
2. What good looks like — the concrete bar its output has to clear.
3. Where it stops — what it must never do without asking first.

1. Design System bot

Owns: maintaining consistency of existing tokens and components — flagging drift, not inventing new visual language.
Good looks like: a report of components that have drifted from the token spec, with a proposed fix that reuses existing tokens.
Stops: it cannot introduce a new color, spacing scale, or type size on its own — any new token is a human design decision.

2. Prototype bot

Owns: turning an AI-generated or rough layout into a state-complete draft — loading, empty, error, and the happy path.
Good looks like: a prototype that is honest about being a prototype, not dressed up to look shipped.
Stops: it does not get treated as a shipped product — a design engineer still owns the last mile from prototype to something a customer can rely on.

3. Bug Repro bot

Owns: reproducing a reported bug reliably and documenting the exact steps, not fixing it.
Good looks like: a written repro case a human engineer can run and confirm without guessing.
Stops: no production deploy — capture and document only, hand off the fix to a human or a separate, explicitly-scoped Cloud Agent job.

4. Launch Page bot

Owns: building a landing page from a written brief, using existing design-system components.
Good looks like: a page that matches the brief and passes a pre-publish review (broken links, missing alt text, obvious layout breaks).
Stops: a human publishes. Every time, no exceptions — see our note on who's actually allowed to publish.

Why charters beat personas

A persona ("Marketing Bot") describes a vibe. A charter names a publish surface, a concrete quality bar, and an explicit stopping point. If a bot can't answer "what do you own, what does good look like, and where do you stop" in one sentence each, it isn't ready to run unattended — regardless of how good its name sounds.

Frequently asked questions

How many bot charters should a small studio start with?

Start with one, following the one-reversible-job test, before building out a roster of four.

What's the difference between a charter and a persona?

A persona is a name and a vibe. A charter states what the bot owns, what good output looks like, and exactly where its authority stops.

Can a Design System bot add new colors or components?

No — under this charter it flags drift from existing tokens and proposes fixes using what already exists. New visual language stays a human design decision.