The second card in Tuesday’s brief carried two drafted payment reminders for the €18,400 sitting past thirty days. The owner of Atelier Mira read them, cut a sentence about payment terms that sounded like a contract quoting itself, typed one line about the autumn order in its place, and approved. The whole intervention took maybe fourteen seconds. Most software treats those fourteen seconds as friction on the way to send. Here they are the most useful data the system will receive all day.
An edit is a typed correction
When a draft changes between staging and approval, the change is not discarded once the email goes out. The diff is recorded: what was drafted, what was sent, and the delta between them, written against the drafting model the same way last week’s shallow markdown was written against the pricing model. The mechanics are deliberately unexciting. One edit is a data point. The same edit twice is a coincidence worth noting. The third time the terms sentence is cut from a reminder to a long-standing customer, the pattern is promoted from observation to preference, and the next draft states it in its own reasoning: terms line omitted, removed in the last three approvals to accounts older than five years.
Taste, in this sense, is nothing mystical. At Mira it is a short list of learnable regularities: never quote contract language at a customer who has paid reliably for six years; name the next order when there is one, because the relationship is the leverage; keep a reminder to two paragraphs; sign the way the owner signs, not the way software signs. Nobody wrote that list. It was extracted, edit by edit, from the gap between what was drafted and what was sent.
You never wrote a style guide. You edited nine drafts out of forty-one, and that is a style guide, with evidence.
Closer, not identical
The honest limits matter more than the promise. The system learns what you repeat, not what you feel. A one-off edit stays a one-off: recorded, visible, and not generalized from. And when a learned preference is applied, the draft says so, which is the difference between taste and drift. A wrong lesson (the terms line, it turns out, still belongs in reminders to brand-new accounts) shows up as one visible sentence in a rationale, and it is corrected through exactly the channel that taught it: edit the draft, approve, and the correction outranks the habit.
The invoice-reminder routine at Atelier Mira, at each stop of the dial. Same intelligence, different license to act.
One tap on Approve and SENA sends both, logs both, reconciles both tomorrow.
Approve → sent 09:02 → graded in Friday's ledger.
The dial is per-routine, not global. Payroll can live at “Suggests” forever while invoice reminders earn “Runs.” Trust is earned one reconciled morning at a time, and it turns back left in one click.
Edits are how the dial earns its next stop
This is the quiet connection between correcting drafts and the autonomy dial. The invoice-reminder routine’s eleven-week record is usually quoted as forty-one sent, thirty-eight expectations hit, zero complaints. The number that mattered just as much: the edits trended to zero. Nine of the first twenty-two drafts were touched; the last nineteen went out exactly as written. Edits reaching zero is the moment the drafts stop being the system’s and start being yours, and it is what makes the move to “Runs the routine” smaller than it sounds. What runs unattended is not software’s idea of a reminder. It is your reminder, reproduced, with all nine corrections baked in.
Every applied preference can be traced: which edits taught it, on which drafts, and every draft it has shaped since. Taste is subject to the same rule as everything else in the memory. If it changes what the system does, it is on the record, and you can ask where it came from.
The gap between draft and send closes over weeks, and it closes from both directions: the drafts rise toward your standard, and your reading of them gets faster because there is less to catch. Fourteen seconds of editing on a Tuesday is a small thing to call teaching. But teaching is mostly this: a correction, made where the work is, kept where the next attempt can find it. The classroom is the draft. The lesson plan is the diff. And the exam, as always here, is the next morning, in the ledger.