Part 3 · Operate
Sending and deliverability
Every check in one transaction before anything leaves. Any one of them stops it.
01What it is
Every send passes a single gate that checks suppression, exclusions, caps, identity health, autonomy, budget, plan, pause state, verification and your warm network, all in one transaction.
02Why it exists
Sending is the one action with a blast radius you cannot recall. A message to a suppressed address is a complaint, and a burst to one domain is a reputation problem that takes months to undo.
Checking these separately would let a race through the gap between two of them. One transaction means the answer cannot change between checks.
03How to use it
- 01Connect a mailbox with real sending history.
- 02Watch the health indicator during the first fortnight.
- 03Use the global pause when something looks wrong. It takes effect immediately at every stage.
- 04Read the refusal reason when a send is blocked. It names the specific condition.
- 05Under the new plans, a venture its plan paused sends nothing, and an account whose payment is past its grace period stops sending until it pays. The refusal says which.
04What good looks like
- You give it
- A healthy identity, an address verified recently, one send to a domain today.
- You get
- Allowed, with the verification source recorded on the send.
- Why
- Every condition passes and the verification provenance is stored for attribution.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- A second send to the same company domain on the same day.
- You get
- Refused with domain_daily_cap.
- Why
- The per-domain daily cap is one. Two people at one company on one day reads as a campaign to their mail server.
Derived from the rules in the code