05 · Lifecycle
From trigger to send
A single outbound message moves through the AWS-native pipeline — each stage owned by a different system, each handoff recorded in the DynamoDB status field of the single-table store hv-hub-v2-development-tasks (us-east-2). The audit trail is the status timeline plus the Undo audit items and Audit_Log.
01
Trigger · n8n "Auto Tasks" cron fires
scheduleTrigger node activates and POSTs to the producer. Body context: playbook_id, list_id, source_workflow. (Re-pointed off the VPS 2026-06-08.)
n8n · POST /generate
02
Producer · API GW → SQS
The task-producer Lambda ACKs 202 in <1s and enqueues onto SQS tasks-ingest (+ DLQ, maxReceiveCount 5). Decouples the cron from the slow Bedrock draft.
Lambda · SQS tasks-ingest
03
Consumer · pull + enrich
task_consumer Lambda dedups (task_guid#idx), pulls the audience (HubSpot list membership / Airtable Orders view), enriches (deal, owner, last touch), and loads Bot Settings (Gabrielle / Sales_Assistant) for the system prompt + guardrails.
Lambda · HubSpot · Airtable
04
Governor gate · ALLOW / DEFER / BLOCK
Before drafting, the consumer calls POST /api/governor/check (GOVERNOR_ENABLED; fail-closed by default). Hard suppress / opt-out → BLOCK; out-of-family or over-cap → DEFER (writes a held task), or DROP when the config is set to drop; otherwise ALLOW. HOLD is reserved in the type but never emitted. Every decision logged to the GOVDECISION audit partition.
Governor · /governor/check
05
Generate · Bedrock draft
Prompt + context → draft via Bedrock Converse (claude-sonnet-4-6). Confidence scored; below the threshold (the Governor confidenceThreshold, default 60, authoritative for all playbooks — the per-playbook SSOT "Confidence Threshold" is deprecated for gating; the consumer's hard-coded fallback is DEFAULT_CONFIDENCE_THRESHOLD=60) routes to needs_review with no draft shown. Guardrail failures route to manual review, never auto-discard.
Bedrock · Converse
06
Queue · PutItem DynamoDB
Item written PK=TASK#<id>, SK=META, status=pending_review (GSI1PK=STATUS#pending_review). Idempotent on task_guid#idx. The consumer only ever writes — it never sends.
DynamoDB · single-table
07
Review · Hub v2 Tasks queue
Reviewer (Jess / Mario / Farid) works the tasks-v2 queue at hubv2.apphappenventures.com, one at a time. Six actions: Approve & Send, Edit (incl. Edit-with-AI), Reject, Snooze, Comment, Escalate. Approve & Send → status=resolved with an optional, non-blocking sign-off reason (DEV-471).
Hub v2 · /tasks-v2 · human
08
Send · outbound_sender Lambda (Unified Sender)
A sending reviewer action enqueues a typed message onto SQS outbound-messages; the message-dispatcher Lambda claims it idempotently (OUTBOX# in DynamoDB) and routes by channel to the matching adapter — email (Gmail DWD), Slack (chat.postMessage), WhatsApp (Meta Graph — adapter real, token secret not yet populated); SMS is still a stub. The send gates now live in the Governor config (edited from /admin/governor, no deploy), not just env vars: whether a real email leaves is the Governor sendDevelopmentMode flag — ON redirects every recipient to the developmentTestEmails inboxes, OFF sends to the real client. As last verified (2026-07-30) it is OFF, so email reaches the real recipient; read /admin/governor for today's value. (The legacy maestro_sender Gmail worker still exists but ships inert: SEND_DRY_RUN=true and its EventBridge tick DISABLED.)
Lambda outbound_sender · SQS · multi-channel
Dual send-worker risk
A legacy n8n "AWS Send Worker (Maestro)" polls the approved sales queue (GET /queue/approved) and was never confirmed retired at the Unified-Sender cutover. The inert maestro_sender Lambda (dry-run + its EventBridge rule DISABLED) is a third, dormant poll worker on the same queue. With the SQS-based message-dispatcher now the live sender, any approved task the n8n worker also picks up can be sent twice to the client. Retiring the n8n worker is the pending step — see Risks.
