System Architecture

Visual diagrams showing how Meta Council's core systems work -- outreach pipelines, council sessions, workflow DAGs, and scheduled automation.

Diagrams

Outreach Email Pipeline

Automated outreach sends personalized emails daily, then classifies inbound replies with AI to trigger follow-up actions, Slack alerts, and status updates.

Lead Database Daily Sender (9am PT) SendGrid SMTP Prospect Inbox replies Prospect Replies SendGrid Inbound Parse webhook Reply Classifier (AI) label Trigger Engine Auto-Reply Slack Alert Status Update Lead Scoring Webhook Trigger Rules configures

Emails are sent daily at 9am PT. Inbound replies are parsed by SendGrid, classified by AI, and routed through configurable trigger rules.

Council Session Flow

A user query fans out to N expert agents running in parallel. Each agent produces an independent analysis, then a synthesizer merges all outputs into a single decision document.

User Query Panel Selection auto / dynamic / manual dispatch Agent 1 Agent 2 Agent 3 Agent N ... parallel Analysis + Tools Analysis + Tools Analysis + Tools Analysis + Tools Synthesizer Executive Summary + Risk Matrix + Action Plan /s/{id} permalink + email notification

Agents run in parallel with independent tool access. The synthesizer combines weighted outputs into a structured decision document with a permanent shareable URL.

Workflow DAG Pipeline

Users describe a goal in natural language. The system parses intent, matches a workflow, confirms with the user, then executes steps sequentially with optional human-in-the-loop checkpoints.

Natural Language Goal parse Intent Parser match Workflow Matching Read-back Confirmation user approves plan STEP 1 Agent A output CHK yes Human Review approved STEP 2 Agent B STEP 3 Agent C Results + Email

Workflows execute as sequential DAGs. Checkpoint steps pause for human review before continuing. Each step's output feeds into the next agent's context.

Scheduled Workflow Automation

Users attach cron schedules to workflows. A scheduler checks every 60 seconds for due runs, executes the full pipeline automatically, emails results, and computes the next run time.

User Creates Schedule cron expression + workflow Scheduler (every 60s) background loop check Is it time? no -- wait yes Load Workflow Auto-run All Steps Email Results to User Compute Next Run Time update schedule record next cycle

The scheduler runs as a background task, checking every 60 seconds. When a schedule is due, it auto-executes the entire workflow pipeline and emails the results.