Diagram 05 · Targeting Cell Walkthrough

Agentic Flow

A single operator request: from prompt to grounded answer to released artifact. Nine steps, from prompt to release artifact in under nine minutes.

Targeter mission operator PIV / CAC authenticated SF Sponsor 360 workbench · LWC LUMBRA Lumbra Nebula orchestrator SF MuleSoft PCE cross-boundary broker SF Mission CRM target package record 3P Snowflake via dbt semantic 3P Elastic hybrid search 3P · LLM AI Model Pool in-enclave Gemini 1 "Build target package on subject X" JWT + attribute bundle attached T+0s 2 invoke agent: build target package PEP check + tool registry scoped to targeter attributes T+2s 3 read target package record CRM is agent working memory · tool call via MuleSoft PCE named creds · mTLS · ABAC check subject ID · prior touchpoints · attributes PCE response mediation T+8s 4 grounded query via dbt semantic layer cables · entities · transcripts where subject = X OAuth + key-pair · row + col policies enforced 147 rows · ABAC-aware classification + lineage PCE response mediation T+35s 5 hybrid search: BM25 + vector similarity mentions of X past 90 days · doc-level ABAC enforcement API key + mTLS · document-level security 38 ranked documents · score + relevance PCE response mediation T+1m 20s 6 inference call: synthesize target package prompt = CRM record + Snowflake rows + Elastic chunks + classification rules · guardrails active draft target package with grounded citations · classification carried · ready for review T+5m 7 return draft + citations analyst can drill into every claim T+5m 45s 8 operator reviews · edits · approves ~13 minutes of expert judgment T+19m 10s 9 commit target package · trigger release flow Flow generates cable artifact · CDC fires to pipeline · audit recorded named creds · CRM write · release event T+~20m 9 hours → 4 min agent work + 5 min expert review The mechanical work moved to the agent. The expert judgment stayed with the targeter. Same authorization fabric, same audit trail, same artifacts delivered to legacy consumers. ABAC enforced at every horizontal arrow above · operator attributes propagated through every call · MuleSoft PCE is the cross-boundary PEP