Dashboard
Regulatory intelligence overview for Capital.com (UK)
Critical / High
—
items requiring action
Unanalyzed
—
new items in feed
EU Compliance
—
readiness score
Last Fetch
—
regulatory sources
High Priority Items
No analyzed items yet — fetch and analyze to populate
Top Compliance Risks
Recent Regulatory Activity
No recent activity
Regulatory Newsfeed
Live regulatory updates — click Analyze to get AI compliance assessment
Fetch:
— applies to next fetch
No news yet — click Fetch Latest News to start
Expansion Horizon
EU market entry compliance assessment — select a jurisdiction to check readiness
Agents & Logic
Transparent view of how each agent works, what instructions it uses, and what data it accesses
1
Agent 1 — Sourcing & Collection
Fetches regulatory news from authoritative sources, filters by relevance, deduplicates and stores
System Instructions
ROLE: Regulatory news sourcing agent for a Fintech compliance team
SOURCES: FCA, EBA, ESMA, EUR-Lex, HM Treasury RSS feeds
JURISDICTION_FILTER: UK, EU
DATE_FILTER: Last 7 days only
DEDUP: SHA-slug comparison against news_feed D1 table
OUTPUT: title, source, jurisdiction, date, 2-3 sentence description
# Agent 1 does NOT analyse — only collects and summarises
# Agent 2 is triggered separately on demand (Analyze button)
Execution Flow
1
Load sources from sources.json via /api/sources
2
Fetch RSS for each active source — parallel HTTP requests
3
Parse XML — extract title, link, description, pubDate
4
Date filter — discard items older than 7 days
5
Deduplicate — skip IDs already in news_feed table
6
Claude Haiku — generate 2-3 sentence plain-language description
7
Store in D1 news_feed table — marked analyzed=0
2
Agent 2 — Compliance Analysis
Analyses each news item against client Business Knowledge DB and Compliance Risk Matrix
System Instructions
ROLE: Senior compliance analyst for a UK-licensed Fintech payment firm
CLIENT_CONTEXT: Business Knowledge DB (see Knowledge Base page)
RISK_FRAMEWORK: Compliance Risk Matrix (Fintech-specific)
JURISDICTION_RULES: UK FCA rules + EU regulatory framework
OUTPUT_FORMAT: impact_level, summary, client_impact, actions[]
# Agent 2 receives: news item + client profile + risk matrix
# Agent 2 returns: structured compliance assessment
# Triggered by: user clicking Analyze button
Execution Flow
1
Receive news item ID from frontend
2
Load Business Knowledge DB from client profile
3
Load Compliance Risk Matrix for Fintech category
4
Load jurisdiction-specific rules (UK / EU)
5
Claude Sonnet — structured analysis with all context injected
6
Store in analyses table, mark news item analyzed=1
7
Return impact level, summary, client-specific actions
Expansion Agent — Jurisdiction Check
Runs compliance gap analysis for EU market entry using jurisdiction-specific regulatory requirements
System Instructions
ROLE: EU regulatory expansion specialist
INPUT: client profile + target EU jurisdiction
FRAMEWORK: EU Fintech licensing requirements per member state
OUTPUT: compliance_score (0-100), gaps[], requirements[], timeline
# Checks: EMI/PI licence requirements, capital thresholds, local presence,
# passporting rights, DORA compliance, MiCA if applicable
Knowledge Base
Business profile and compliance risk matrix used by Agent 2 for analysis
Compliance Risk Matrix — Fintech Payment Firm
Sources
Regulatory feeds monitored by Agent 1
Archive
All fetched regulatory items — analyzed and unanalyzed
Settings & Instructions
Agent system instructions, source configuration, and platform settings