bethatghost
Review before delivery

Every message passes
through your hands.

Explicit review states replace hidden automation. You can see where every message is, what it says, and why you approved it — before it reaches anyone.

Review states

Seed → Generated → Approved → Delivered

Each state is explicit. A message cannot skip from generated to delivered. It cannot be scheduled without approval. The path is clear.
01
Seed

A seed is what you bring to the composition — a phrase, a memory, a feeling, or even just a name. It is deliberately minimal. Its role is to give the AI a true anchor, not a script.

The seed is always preserved in the audit record alongside the generated draft, so you can always see what you started with.

02
Generated

The system produces a draft using the seed, your voice profile, and the recipient context you provided. This draft is in a generated state — it exists, but it is not approved, not scheduled, not going anywhere.

You can generate multiple drafts from the same seed, compare them side by side, and discard the ones that don't feel right.

03
Under review

When you read the draft and want to think it over, you can move it to under review. This is not a required step — it is a holding state for messages that feel almost right but not quite. You can leave notes to yourself here.

Review states do not expire. A message can stay under review for days or years. There is no pressure to approve.

04
Approved

Approval is your explicit sign-off. It means: this sounds like me, this is for this person, and if the moment arrives, I want this delivery to move forward. You can attach a rationale note, a short explanation of why this version felt right.

Approval can be revoked at any time before delivery. If you change your mind, pulling the message back is a single action.

05
Delivered

After delivery, the record closes. The full chain — seed, generated draft, review notes, rationale, verification events, and delivery outcome — stays in the audit log permanently. Nothing is deleted.

If delivery fails, the delivery surfaces in the retry queue. It does not silently disappear. You decide whether to retry or cancel.

Audit trail

Every decision stays on record.

The audit trail isn't a log you have to dig for — it's part of how you work. When you write a rationale note or compare seed to final copy, you're building a record of intent that persists alongside the message.

compareDiff viewCompare seed text to generated draft to approved copy. See exactly what changed and where the AI took liberty with your phrasing.
sticky_note_2Rationale notesAttach a short note at approval time explaining why this version felt right. That note travels with the audit record.
manage_historyVersion historyEvery draft iteration is saved. If you regenerated three times before finding the right version, all three attempts stay in the record.
receipt_longEvent logEvery action, create, edit, review, approve, verify, queue, deliver, is recorded with a timestamp and the actor who took it.