I get more messages than I can answer. Not more than I want to answer: more than one person physically can. Email, Slack, Google Chat, document comments, all of it arriving faster than any calendar allows for composing thoughtful replies. For years my choices were the standard two: answer a fraction well and let the rest go quiet, or answer everything briefly and badly. Silence costs relationships. Rushed replies cost them differently.
There has always been a third option, but until recently it was reserved for people who could afford staff.
How executives solved this before AI
Earlier in my career I worked with senior executives whose correspondence ran through a small personal staff, and I learned the system by watching it. It had levels, though nobody ever named them.
Some messages the executive wrote personally, start to finish. Some they dictated: a staff member typed, fixed the grammar, and sent, and the words were still entirely the executive’s. Some got only a directive (“reply warmly, decline the date”), and the staff, who knew the executive’s voice and preferences cold, composed the actual message. And some the executive never saw at all: staff read the incoming mail, handled it, and replied over the executive’s name, trusted to know what the executive would have wanted.
None of this carried a disclaimer. In the offices I observed, it was treated as an ordinary delegation convention: the executive owned the relationships and set the direction, and the staff were a trained extension of their judgment, accountable for the message they sent.
AI agents now put that same system within reach of anyone. I’ve built mine on my own time, around two tools I run: Ragbot (ragbot.ai) and Ragenie (ragenie.ai). But the old system doesn’t transfer unchanged, because two things are genuinely different.
What AI changes
First, some platforms tell on you. When an agent, rather than a person, performs a send on Slack, Slack stamps the message with a visible “sent using” tag. Pretending the agent isn’t there is not even an option, and designing around a disclosure the platform will make anyway is a losing game.
Second, an AI agent today is not a trained chief of staff. It is very good and it is not that. A human staff member who drafted thousands of letters for one principal almost never invented a fact. An AI agent sometimes does. If a hallucinated detail goes out over my name, presented as my own writing, the damage doesn’t stop at that message; it makes every real message of mine a little less trusted.
So unlike the executives I watched, I disclose. The design question is what the disclosure should say. My first attempt tracked process: which review workflow had run before the message went out. That collapsed under its own complexity, and it answered a question no recipient was asking. Recipients don’t care which internal approval path a message took. They care about exactly one thing: whose words are these?
Three lanes
So the labels track authorship. Every message I send now travels in one of three lanes.
Manual: my words, my hands. I write it and I send it, the way everyone has since email began. AI may have helped me research or polish, the way a spell-checker or an editor always could. Nothing to disclose, because I read every word and performed the send. No marker.
Ragenie: my words, my agent’s hands. I composed the message, dictated it, or edited a draft until the words were genuinely mine, and my agent refined and transmitted it. This is dictation, modernized. It carries one signature, always the same:
🧞♂️ I wrote this with my Ragenie
Ragbot: my direction, my agent’s words. I told the agent what to do (a specific instruction, or standing rules for a class of messages like scheduling and acknowledgments), and it wrote the words. This is the directive level of the old staff system. The signature says so plainly:
🤖 my Ragbot handled this one for me — I read every reply
That last clause is a commitment, not decoration. The loop always closes with me.
After two or three messages, the legend teaches itself. No marker: all me. Genie: my words, delivered by my agent. Robot: my agent, working under my direction. A recipient never has to parse fine print to know what they’re holding.
The rule that keeps it honest
One rule holds the system together: a lane can only claim what actually happened, and when in doubt, claim less.
The genie signature makes a strong claim, I wrote this, so it is only available when that claim is true. There is no “mostly wrote it” genie variant, and no version of it for messages I haven’t read. I know because I tried to write one, and every attempt came out self-contradictory. That failure was the design insight: you cannot phrase your way into claiming authorship of words you never saw. If the words aren’t mine, the message belongs to the robot lane, whose claim (my direction, not my authorship) is honest at any level of my involvement.
Underneath the labels there is machinery I won’t fully unpack here: a gate that forces the agent to read an entire thread history before composing a reply, a voice gate that catches AI slop before I ever see a draft, a staleness gate that re-verifies facts at send time because approval of text is not approval of a changed world, and a fail-closed hook that blocks any send that skipped the checks. The machinery serves the labels, not the other way around.
I’ve open-sourced the general system (the lanes, the persona registry that lets you brand your own equivalents of Ragbot and Ragenie under your own names, the gates) as synthesis-agent-correspondence in my synthesis-skills repository. The specific brands and signature wording stay in a small private config, which is the part that should be yours anyway.
The executives I watched had something most of us never did: enough trusted hands that no message worth answering had to go unanswered. That’s what I actually wanted from all of this. Not automation for its own sake: an honest way to be present in more of my correspondence than my hands alone allow, with labels that tell every recipient exactly how present I was.
Update, late August 2026: the signature wordings have changed since I wrote this, and every message carries its current form. The lanes still hold.
What tightened is the send permission, which is a separate question from the labelling. Mine now requires me to see the exact text of every agent-lane message before it goes out. The published synthesis-agent-correspondence skill carries the lane model; what any one person permits lives in their own private configuration, so set that part yourself, and expect to tighten it after the first message you wish you had read first.