Neural Pipeline

Living KYC Orchestration Flow
Stage 01
Intake
New KYC case enters the system. Source can be a case worker submitting manually, an API call from another system, or a client's delegated agent presenting credentials. The orchestrator receives the raw payload and begins.
Orchestrator
MCP JSON-RPC 2.0 Latency: <200ms
01
02
Stage 02
KYA Gate
If source is an external agent, the Client Agent Gateway activates. Verifies: signed assertion, agent_id, owner_id, scope boundaries, expiry, blacklist status. The six KYA questions must be answered before any data is accepted.
KYA Gateway
OAuth 2.1 + PKCE KYA Layers: 1-6
Stage 03
Triage
Orchestrator classifies the case: individual or corporate, initial risk assessment (low/medium/high), jurisdiction check (EU/EEA for v1). This determines which specialist agents are activated and what level of scrutiny applies.
Orchestrator
Classification: LLM + rules Jurisdictions: EU/EEA
03
04
Stage 04
Parallel Dispatch
The orchestrator fires simultaneous tasks to all required specialist agents. Each receives only the data it needs (least privilege). This is where the swarm comes alive — multiple agents working in parallel, each in its own sandbox.
Document Sanctions Transaction UBO
Parallel execution Sandboxed isolation
Stage 05
Specialist Execution
Each agent runs in an isolated sandbox with specific tool permissions. Document agent runs OCR + template matching. Sanctions agent checks EU consolidated list. Transaction agent analyzes 12 months of patterns. Output: structured JSON findings.
Document ×2 Sanctions ×2 Transaction ×2
Tool allowlist enforced Schema-validated output
05
06
Stage 06
Risk Aggregation
Risk Scoring Agent collects all specialist outputs. Calculates composite risk score using configurable weights. Generates recommended action with confidence level. Cross-references findings for correlation (e.g., suspicious docs + unusual transactions).
Risk Scorer
Weighted scoring model Correlation analysis
Stage 07
Policy Check
Automated verification against internal rules: risk thresholds, never-events (cross-client data leak, unauthorized access, PII in output), mandatory escalation criteria. This is the last automated gate before routing.
Policy Engine
Never-event detection EU AI Act Art. 14 compliance
07
08
Stage 08
Routing Decision
The fork in the road. Low risk + no findings: auto-advance with human notification. Medium/High risk: full escalation to case worker with evidence package containing all findings, source documents, agent reasoning traces, and recommended action.
Deterministic routing Evidence packaging
Stage 09
Human Decision
Case worker reviews the evidence package on their dashboard. Three actions: approve (case closes), reject (client notified), or request investigation (loop back to specialists with specific questions). Every decision logged with justification — EU AI Act audit trail.
Case Worker UI
Human-in-the-loop Tamper-evident logging
09
10
Stage 10
Client Prompt
When platform needs something only the human client can provide (liveness check, signature, missing document), it contacts the client directly — never through their agent. Secure channel: app push, SMS, or email with unique, time-limited link.
Direct-to-human channel Time-limited tokens