1 files changed, 19 insertions, 0 deletions

diff --git a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
index b4ca450..49f4000 100644
--- a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
+++ b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability.md
@@ -1018,6 +1018,25 @@ multi-recipient field, so there is prior art to reuse rather than a blank page.
 model, not an SMTP client written here. A design that puts a socket in this
 process is out of scope regardless of how the UI turns out.
 
+**What exists on this machine, measured 2026-08-20, because the sentence above
+assumes something that is not there.** "Sending should be an external script on
+the same model" is easy to write and there is no such model to copy: the fetch
+side has `mbsync`, and the send side has NOTHING.
+
+- No MTA is installed at all. `msmtp` and `sendmail` are both absent.
+- neomutt sends over its OWN built-in SMTP, configured per account
+  (`smtp_url` and `smtp_pass` in `~/.config/neomutt/accounts/*.rc`), so the
+  working setup this application mirrors has no external send path either.
+- All five accounts already configure a `drafts` folder, so the draft half has
+  somewhere to live before anything is decided.
+
+That is the first question for the user, and it is not a UX one: sending needs
+either an MTA they choose to install and configure (msmtp being the obvious
+one, and the only shape that keeps the no-network-protocol rule intact), or a
+decision to relax that rule. Do not assume the first just because it is
+tidier; installing and configuring an MTA is work they have not asked for, and
+the credentials already exist in neomutt's files.
+
 **Approach.** Brainstorm first, on its own branch, producing a spec under
 `docs/superpowers/specs/` before any code. The open questions are all UX, as the
 note says: where a composer lives, how a draft is stored so `notmuch` can see