| name | send-gateway |
| description | The single outbound chokepoint for every autonomous action Bravo performs on behalf of CC. Enforces CASL compliance, cooldown windows, daily caps, and cross-engine idempotency architecturally — callers cannot bypass it. |
| disable-model-invocation | true |
| triggers | ["route outbound through gateway","send via send_gateway","enforce cooldown before sending","check if lead was recently contacted","outbound chokepoint"] |
Send Gateway — the only outbound path
Rule of law: If code sends email, a DM, or any outbound message on CC's behalf, it goes through scripts/send_gateway.py. Direct smtplib.SMTP_SSL() calls from a business engine are a regression and must be reverted in review.
Why this skill exists
Before 2026-04-20, four Python engines and one N8N workflow could contact the same lead on the same day without seeing each other. They wrote to three different tables. No engine could answer "was this lead contacted in the last 72 hours?" before acting. That is the root cause of the duplicate-email bug CC described in the 2026-04-19 audit.
This skill encodes the rule that closes that bug: every send goes through send_gateway.send(). Idempotency is not a library callers must remember to invoke — it is architecturally enforced because the smtplib call lives inside the gateway and nowhere else.
When to use the gateway
Use the gateway whenever your code:
- Sends an outbound email (cold, nurture, confirmation, reminder, template-based)
- Sends an outbound DM / Instagram / LinkedIn message
- Logs a call or meeting as outbound activity
- Delivers anything on CC's behalf to anyone outside his organization
Do NOT bypass the gateway just because a send is "simple" or "one-time." The whole point is that the cooldown ledger remains whole.
Quick reference
From Python (importable)
from send_gateway import send
result = send(
channel="email",
agent_source="outreach_engine",
to_email="jane@acme.example",
lead_id=None,
subject="Quick question about your HVAC scheduling",
body_text="Hi Jane, ...",
body_html=None,
brand="oasis",
intent="commercial",
cooldown_hours=None,
metadata={"campaign": "hvac-q2-2026"},
ics_content=None,
ics_filename="meeting.ics",
dry_run=False,
)
send() NEVER raises. On any error it returns status="error" with a reason string. Callers can rely on the return shape.
From the CLI (scheduler, Telegram, manual)
python scripts/send_gateway.py --json send --channel email \
--to jane@acme.example --subject "..." --body "..." \
--agent-source manual_cc
python scripts/send_gateway.py can-act --lead-id <uuid> --channel email --json
python scripts/send_gateway.py history --lead-id <uuid> --limit 10
python scripts/send_gateway.py stats --json
Intent semantics
| Intent | Suppression check | CASL footer | List-Unsubscribe | Example use |
|---|
commercial | enforced (fail-closed) | added | added | cold outreach, nurture, sales |
transactional | skipped (CASL s.10(9)) | added | added | booking confirmations, reminders, password resets |
internal | skipped | skipped | skipped | internal test mail, CC-to-self notifications |
Brand identity
The brand keyword selects CASL footer sender name + business name + address. Add a brand to BRAND_IDENTITY in scripts/send_gateway.py when CC wants a new one to share the chokepoint.
| Brand | Business name | Sender | Use for |
|---|
oasis (default) | OASIS AI Solutions | Conaugh McKenna | Agency outreach, client comms |
conaugh_mckenna | Conaugh McKenna | CC (Conaugh McKenna) | Personal brand, content, DJ inquiries |
nostalgic | Nostalgic Requests | Conaugh McKenna | Nostalgic Requests product mail |
Cooldown defaults
Conservative by default — CC is still building reputation; better to under-send than look spammy.
| Channel | Cooldown | Daily cap |
|---|
| email | 72h (3 days) | 50/day |
| instagram | 48h | 30/day |
| linkedin | 72h | 20/day |
| phone | 168h (7 days) | 15/day |
| skool | 24h | — |
| telegram | 0 (internal) | — |
Override per-call with cooldown_hours=<int>. Daily caps are hard — gateway refuses over-cap sends with status="blocked".
Engine wire-up (2026-04-20 rewire)
All five outbound Python engines now route through the gateway:
What the gateway writes
Every successful send writes to three places:
lead_interactions (architectural truth — cooldown_until + agent_source + metadata)email_log (legacy SMTP-layer truth — keeps analytics and report tooling working)leads.last_contacted_at (keeps CRM pipeline view fresh)
Failed sends write only to email_log with status='failed' for forensics.
Related
When adding a new channel
- Add the channel name to
KNOWN_CHANNELS (frozenset).
- Add a default cooldown to
DEFAULT_COOLDOWNS.
- If there's a daily cap, add it to
DAILY_CAPS.
- In
send(), add a channel-specific branch that performs the physical send — route it through a _send_<channel>() helper that is the ONLY place where the real client call lives.
- Add tests for the new channel to test_send_gateway.py.
Maven-specific adaptation
Maven owns scripts/send_gateway.py for marketing email blasts, Meta Ads spend, Google Ads spend, and any DM/social-post outbound. The architecture is identical to Bravo's — single chokepoint, fail-closed critic gate, name sanitization, daily/hourly caps, suppression-list check. Caps are stricter on the Maven side because marketing list sizes are larger (200/day vs Bravo's cold-outreach pace). The killswitch env var is MAVEN_FORCE_DRY_RUN=1. Paid-spend channels (meta_ads, google_ads) additionally consult cfo_pulse.json before approving. Maven NEVER bypasses the gateway, even for "small" tests — every outbound action goes through it or it's a regression.
