The message comes in.
The job opens itself.

A customer leaves a voicemail about sixty feet of cedar privacy fence. In 5.1 seconds the customer and the job are open on your desk and a reply is drafting from your template under your standing rules. You fix what you'd fix. You press send. The software cannot send anything; the database refuses any sender but you.

Fix it once. It stays fixed.

Underneath the desk is Stet: the memory your business keeps outside anyone's head: how each piece of work goes, step by step, and the rules you'd apply at each one. Your assistant reads it before it drafts. You read the draft and send it yourself.

What it is

Every piece of work you send out uses things only you know. What you charge for a second story. Which jobs you turn down. The line you always add about access. None of it is written anywhere, so nobody else can do it and you do it after dinner.

Stet writes it down, at every level the work has. Your standing rules. Each process you run, drawn as the steps it goes through and who does each one: your assistant, you, or the customer. The rules that apply at one step and nowhere else. Correct a draft once and the correction holds the next time that step comes around. Say the same thing at two steps and it becomes a rule for the whole process.

It also keeps track of where each piece of work stands. Which step is owed and by whom, what the customer sent back and why, what has to be redone. Your assistant does the steps it can and hands you the ones it can't.

Quotes are the example you'll see in the sample workspace. The product doesn't know what a quote is. It knows what a process is.

stet (verb, from the editor's mark): let it stand. The instruction that a correction holds.

Why not your assistant's own memory

Your assistant's memory belongs to your assistant. Stet's belongs to you. Both are memory. Stet is the disciplined kind, and it goes wherever you draft.

Built-in memory is good at remembering you. Stet is for remembering how you do your work, the same way every time, whoever or whatever does the drafting.

Who it's for

How it works

1. Connect Stet to the assistant you already use. It keeps pointers to your documents, never copies, and it can't send anything: it never has the permission.
2. Tell it how one piece of work goes, start to finish, and fix the picture it draws. Hand over a folder of your last ten and give us an hour on a call.
3. Your assistant asks Stet before it drafts and follows what comes back. You correct, you send, it learns.

Which assistants

One manual, whichever assistant you draft with. Switch assistants and your rules come with you.

Any other assistant that can attach a remote connector (MCP) can use Stet, with sign-in or with a key. Setup

Where it stands

October 2026. The owner's app and the assistant connection are live and run a sample business end to end: three processes, thirty runs, rules at eight of its steps. Since October 21, DeepSeek Harness users can add Stet with one command. Pilots start late 2026 with businesses whose work goes out as a document the customer answers.

Forward one message. Read the draft that comes back.

Twenty minutes, your real voicemail. Nothing you or your customers write trains any model. Every customer field is ciphertext at rest under a key held in the database vault. Every draft, edit and send is a row in an insert-only audit log you can export.