You're the one who hits send

The scariest sentence you can say to a small-business owner is "it runs your inbox for you." Because the picture that jumps to mind is an AI firing emails at their customers, unsupervised, at three in the morning — and one wrong reply to the wrong client is exactly the kind of thing you don't get to take back. If that's what "runs your inbox" means, nobody sane says yes.

So Dustav doesn't mean that. There's a hard line drawn straight through the middle of it, and the line is this: you're the one who hits send.

Operator, not autopilot

Dustav does a startling amount on its own. It reads every email that comes in — the whole thread, the attachments. It drafts the reply you owe and does the entry: books the payment, files the receipt, catches the ship-by date. Left alone overnight, it does a full morning of work before you've had coffee.

And then it stops, and waits for you.

The reply it wrote sits in your outbox until you read it and choose to send. It never sends on its own. The way I think about it: Dustav is an operator you supervise, not an autopilot you hand the controls. It's allowed to do the work. It is not allowed to be the last word.

The line isn't "don't touch anything"

For a while I drew the fence in the wrong place. I thought the rule had to be "never write to their Gmail at all" — read-only, look but don't touch. That's too blunt, and it throws away something genuinely useful: Dustav is good at knowing where each email should be filed.

The real line is sharper than "don't touch." It's: never do an irreversible, outbound, or authorship act without a human commit. Reading is free — it's your mail, and reading changes nothing. Drafting is free — a draft you don't send is just a suggestion. But sending — the one act that leaves your building, lands in someone else's inbox, and can't be recalled — always waits for you.

Then we had one of the sharpest conversations of the whole build, and it pushed the line one notch further. The move wasn't to give Dustav a filing tool and then fence it — it was to make the capability smaller. Dustav doesn't file anything on its own; it suggests where an email belongs, and the same click that sends your reply files it too. We reasoned the whole thing down to the moment you were already going to hit send. The safest version of a power, it turns out, is the one you never granted.

The fence is what buys the freedom

Here's the part that surprised me, and it's why this isn't a limitation I'm apologizing for.

The fence at send is exactly what lets me turn Dustav loose everywhere else. Because the worst thing a confused or runaway model can do — on its most catastrophic day — is write a draft you glance at and delete, I can let it read your entire inbox and draft freely and boldly. The blast radius of its biggest possible mistake is one unsent draft. That's the whole downside.

If Dustav could send on its own, I'd have to make it timid — check twice, ask permission, hedge everything — because a wrong send is real damage to a real relationship. Fencing the one dangerous act is what lets everything upstream of it be aggressive. Restraint at a single point buys freedom at every other.

It's the shape, not a training wheel

The obvious question is whether "you hit send" is temporary — a caution I'll drop once the model is good enough, on the way to true hands-off autonomy.

Mostly, no. There's a version down the road where you give Dustav standing permission for the genuinely boring, unambiguous stuff — send the receipt, every time, you don't need to see it — and I'll build that, deliberately, behind this exact line. But the default doesn't flip. The default is that a thing going out under your name, to your customer, is yours, and you saw it. That isn't a phase the product graduates out of. It's what makes it the kind of thing you can hand your livelihood to.

An AI that does your work has to earn one specific thing: that you stop checking every output. I want Dustav to earn that, and most of my work is aimed at it. But there's one job it will never take from you, because you shouldn't want it to — the last look, and the hand on the button.

You're the one who hits send.