Skip to content

A DeepDopple build story

In development: foundation built

Drafts that wait for your yes

How we are building DeepDopple, an AI that drafts social posts in your voice and publishes nothing until you approve it.

By Doerwise ·

The wish

I want an AI that drafts posts in my voice. Something that does the first draft, so posting regularly stops being a chore.

There is a second half to that wish, and it matters more: never post anything I did not mean.

Why it sounded impossible

The risk is in the word publish. An assistant that can post for you can post the wrong thing, at the wrong time, under your name. So the rule could not be a setting. It had to be part of the foundation.

It also had to be one product. Drafts written on the web and approved on a phone have to belong to the same account, behind the same sign-in.

Every draft starts as pending review

We started with the shape of a draft's life, written into the schema. A draft starts as pending_review. From there it can be approved, edited and approved, declined or snoozed. Only the two approvals lead on to queued, publishing and published.

Those values are enforced by a check constraint on the drafts table, so the database itself refuses any status outside the list.

Declined and snoozed drafts stop where they are and never reach the queue. Read the states in order and there is exactly one road to published, and it runs through your yes.

Editing gets its own state. A draft you changed before approving becomes edited_approved, so the record keeps apart the posts that went out as drafted and the posts you rewrote. Snoozing sets a draft aside for later without approving anything.

One publish job per approval

Approving a draft creates one publish job for that draft, and only that draft. An approval cannot sweep up the rest of the queue.

Saying no is part of the design too. The schema has a place for the reason you decline a draft: wrong tone, bad timing, or not this topic.

One account, web and phone

DeepDopple has one account and one sign-in, on the web and on your phone. That part of the foundation is built, so drafts and approvals will have one home.

Where it stands

DeepDopple is in development: the foundation is built. The account, the sign-in and the draft schema exist. The approval inbox does not yet.

The demo on its product page is the planned flow. It walks a sample LinkedIn draft through the real status values from the schema, so you can see how approve, edit, decline and snooze will work before the inbox is built. We would rather show a plan clearly labeled as one than pass a preview off as a product.

The planning docs aim it at LinkedIn text posts, and the planned editor holds LinkedIn's 3,000 character limit. The part that writes in your voice is the goal the foundation is built for.