Now
Today
“What is waiting on a person.”
What needs you
Every count here is a queue with a human at the end of it. A zero is a real answer, not a missing one — the empty state says so rather than showing you a dash and letting you wonder whether the route failed.
Step one
Before the Send
“Can we send, and how much, and is anything burning.”
Reputation
Bounce and complaint rate against the AWS SES account-review limits. AWS tracks reputation per account, not per domain — one bad burn domain puts every identity in account 724702275866 under review. That is why uncorrelatedalts.com is permanently off this account (spec §6, hard rule).
Step one
Before the Send
“Can we send, and how much, and is anything burning.”
Domain Fleet
The cold / warm domain split and the lifecycle state of every burn domain. Cold outreach ships from a separate domain than the brand domain so that spam classifiers, list complaints and natural noise never accumulate against uncorrelatedalts.com (spec §6, domain reputation isolation).
Step one
Before the Send
“Can we send, and how much, and is anything burning.”
Sender Identities & Ramp
Ramp is a property of the identity, not of the system — every mailbox starts at day 1 on its own clock (runbook §0, rule 2). A mailbox that cannot receive a reply must not send (rule 3). Both are gates, not guidance.
Step one
Before the Send
“Can we send, and how much, and is anything burning.”
Mailbox Warmup
Phase A sends cold‑domain → warm‑mailbox; Phase B auto‑replies, rescues from spam and promo, and archives under the Warmup label. One‑sided traffic looks suspicious to spam classifiers, so the reply rate is the health metric, not the send count (spec §6, warmup framework).
Step two
The Send
“What is going out, to whom, and from whom.”
Campaigns
Every active template, its audience, who sends it, and whether it mints HubSpot pipeline. Deal creation is the one HubSpot write that is hard to undo in bulk, so it is shown here per campaign rather than buried in a Worker secret.
Send a campaign
Template settings
Step two
The Send
“What is going out, to whom, and from whom.”
Lifecycle State Machine
The AI Coordinator advances deal stages on observable signals rather than waiting for a human to drive them. It auto‑advances to Early Prospect and no further; everything beyond that is human judgment surfaced through stale-deals-daily (spec §3.6). Transitions the spec flags NOT YET WIRED are drawn dashed so nobody assumes automation that does not exist.
Step three
What Came Back
“Who answered, who a machine answered for, and who we must not contact again.”
Reply Triage
Prospect replies awaiting triage, newest first. A matched non‑unsubscribe reply is what advances a deal Raw Prospect → Early Prospect. Marking an item handled stamps your email onto the send event — replied_handled_by has existed since migration 007 and could not be filled honestly until per‑operator tokens shipped.
Step three
What Came Back
“Who answered, who a machine answered for, and who we must not contact again.”
Auto‑Reply Suppression
Messages the poller matched to a send but classified as machine‑generated. None of them set replied_at, so no HubSpot deal advanced and every sequence kept running — including the departures. Nothing on this screen has been blocklisted by the engine. A possible departure waits here until you confirm it, because blocklisting is permanent and a regex should not be the one deciding. Read the reason against what they actually wrote, then confirm or dismiss.
Step three
What Came Back
“Who answered, who a machine answered for, and who we must not contact again.”
Stale‑Deal Bubble‑Up
The design driver, stated plainly in spec §3.6: Ryan does not reliably maintain CRM state, so the system surfaces stale deals for human judgment instead of expecting humans to advance the pipeline. Raw Prospect is stale at 28 days because that is the five‑email drip cadence (E5 lands day 28); every other open stage is stale at 7. Bubble‑up only — nothing auto‑closes.
Step three
What Came Back
“Who answered, who a machine answered for, and who we must not contact again.”
Suppression
Blocklist size, breakdown by decline kind, and expired deferrals ready to re‑approach. Unsubscribe stamps cold_outreach_unsubscribed_at and is deliberately distinct from the blocklist, which covers every reason (spec §3.6 data model).
Record
Changelog
“What shipped, when, and what it changed.”
What shipped
Newest first. Every entry names the migration or the file, so a claim on any other screen can be traced to the change that made it true. If a screen and this record disagree, this record is the one that carries a date.