Intent Outreach architecture
Intent Outreach architecture
The Claude Code plugin drives an MCP server, which drives the pipeline engine. The engine calls a connector registry of nine adapters, which reach external data providers over HTTPS with the operator's keys. The engine consults one model provider for scoring and drafting. Results pass a validation gate before reaching the local run store.
FIXED ORDER
HTTPS, YOUR KEYS
VALIDATED ONLY
2 CALLS: SCORE, DRAFT
Claude Code plugin, orchestrator skill: skills/intent-outreach/SKILL.md
Claude Code plugin
skills/intent-outreach
Outreach MCP server: mcp/server.ts, stdio transport
Outreach MCP server
mcp/server.ts, stdio
Pipeline engine, the focal component: pipeline_core/pipeline.ts
Pipeline engine
pipeline_core/pipeline.ts
Connector registry, nine adapters called in fixed registration order: pipeline_core/connectors/index.ts
Connector registry
9 adapters, fixed order
External data providers reached with the operator's own keys: Apollo, Hunter, People Data Labs, Exa, plus five more
Data providers
Apollo, Hunter, PDL, Exa, +5
Validation gate, the only mint of the Validated record type: pipeline_core/validator.ts
Validation gate
validator.ts, typed gate
Local run store, JSONL on the operator's machine: pipeline_core/store.ts
Local run store
runs.jsonl, your machine
Model provider, Claude by default, others admitted after passing the evaluation gate: pipeline_core/providers.ts
Model provider
Claude default, eval gated
entry surface
service
focal
gate
local store
external, your accounts