Resources
DOC.ID 0x70 / INTELLIGENCE LIBRARY

The reference layer beneath the
platform.

Regulatory briefings, OSINT methodology, typology research, technical architecture and anonymised case studies — written for analysts, MLROs, regulators and engineering teams who need the substance, not the brochure.

§ 01 — Regulatory briefings
AMLR · MICA · FATF · TRAVEL RULE

Readiness notes for the regulated environment.

Short, technical briefings on how Sophkos maps to current and emerging financial-crime regulation. Written for compliance, legal and supervisory readers, not marketing audiences.

⌖ R.01 · AMLR READINESS

EU AMLR & AMLA: an architectural readiness model.

How beneficial-ownership transparency, harmonised CDD, AMLA supervisory expectations and the single rulebook translate into platform, data and evidence requirements.

→ READ BRIEFING
⌖ R.02 · MICA & TRAVEL RULE

MiCA, Travel Rule and the obligated crypto entity.

CASP obligations, originator/beneficiary information, self-hosted wallet exposure, sanctions screening and on-chain attribution in one regulatory frame.

→ READ BRIEFING
⌖ R.03 · FATF RECS

FATF Recommendations as design constraints.

Reading Recommendations 10, 11, 12, 15, 16, 20 and 22 not as compliance checklists but as architectural constraints on a financial-intelligence platform.

→ READ BRIEFING
⌖ R.04 · SAR/STR REPORTING

SAR-STR drafting with evidence and decision trail.

What a defensible SAR/STR looks like when the underlying evidence, behavioural reasoning and human approval are versioned and reproducible.

→ READ BRIEFING
§ 02 — Typology library
PATTERN CATALOGUE

Recurring patterns. Reproducible detection.

The Sophkos typology library catalogues recurring financial-crime patterns. Each entry pairs a behavioural and structural description with detection logic, evidence requirements and known counter-patterns.

⌖ T.01 · MULE NETWORKS

Mule networks and account farming.

Account opening clusters, dormancy patterns, controller signatures, payroll-mule and romance-mule variants, recovery and disruption strategies.

→ OPEN TYPOLOGY
⌖ T.02 · APP FRAUD

Authorised push-payment fraud topology.

Invoice redirection, impersonation, investment, purchase and romance variants. Behavioural pre-cursors and downstream laundering signatures.

→ OPEN TYPOLOGY
⌖ T.03 · SYNTHETIC IDENTITY

Synthetic identity construction.

Fragment recombination, credit-bureau cultivation, document fabrication and the OSINT signals that separate synthetic from genuine identity over time.

→ OPEN TYPOLOGY
⌖ T.04 · STRUCTURING

Structuring and threshold avoidance.

Smurfing, micro-structuring, time-shifted deposits and the behavioural signatures distinguishing structuring from legitimate cash-intensive activity.

→ OPEN TYPOLOGY
⌖ T.05 · LAYERING

Layering across products and rails.

Multi-rail layering through cards, wires, instant payments, crypto on/off-ramps and pass-through entities. Graph-shape signatures and disrupted-flow detection.

→ OPEN TYPOLOGY
⌖ T.06 · NESTED ACTIVITY

Nested correspondent and pass-through activity.

Nested correspondent relationships, third-party payment processors, shell-bank vestiges, and the structural patterns that betray hidden customers behind a customer.

→ OPEN TYPOLOGY
⌖ T.07 · SANCTIONS EVASION

Sanctions evasion and dual-use risk.

Ownership opacity, jurisdictional rerouting, front companies, trade-based laundering signatures and the OSINT layer that resolves apparent unknowns.

→ OPEN TYPOLOGY
⌖ T.08 · CRYPTO OFF-RAMPING

Crypto off-ramping and fiat conversion.

Mixer and bridge exposure, peel chains, OTC desks, instant-exchange routes, P2P off-ramps and the on-chain to off-chain reconciliation problem.

→ OPEN TYPOLOGY
⌖ T.09 · TRADE-BASED LAUNDERING

Trade-based money laundering.

Over- and under-invoicing, phantom shipments, multiple-invoicing, free-trade-zone exposure, and the documentary patterns that survive correspondent review.

→ OPEN TYPOLOGY
§ 03 — OSINT methodology
OPEN-SOURCE INTELLIGENCE PRACTICE

OSINT as a discipline, not a button.

Methodology briefs covering source taxonomy, attribution, corroboration, adversarial denial, and the operational practice of running OSINT inside a regulated financial environment.

⌖ O.01 · SOURCE TAXONOMY

A taxonomy of open sources for FinInt.

Corporate registries, sanctions lists, PEP corpora, adverse media, leaks, public filings, court records, on-chain data and digital footprint — classified by reliability and freshness.

→ READ METHODOLOGY
⌖ O.02 · ATTRIBUTION

Entity resolution and attribution.

How partial identifiers, name variants, transliteration, address fuzziness and corporate aliasing are resolved into stable, defensible entity nodes.

→ READ METHODOLOGY
⌖ O.03 · CORROBORATION

Corroboration and evidentiary weight.

How independent sources are weighted, how single-source claims are flagged, and how OSINT evidence becomes admissible inside a regulated decision record.

→ READ METHODOLOGY
⌖ O.04 · DENIAL & DECEPTION

Adversarial denial and counter-OSINT.

How sophisticated actors poison open sources, manufacture corroboration and use legitimate privacy channels — and how the platform reasons under those conditions.

→ READ METHODOLOGY
§ 04 — Technical architecture
ENGINEERING REFERENCE

For the engineers reading specs, not slides.

Architecture briefs for technology leadership, platform engineers and security architects evaluating Sophkos against existing systems.

⌖ A.01 · GRAPH MODEL

The intelligence graph: schema and invariants.

Entity, relationship, evidence and decision modelling. Temporal versioning, provenance, and the invariants that keep the graph defensible at scale.

→ READ ARCHITECTURE
⌖ A.02 · STREAMING

Streaming, behavioural and catastrophe analytics.

How transaction streams are scored against behavioural baselines, graph context and catastrophe-risk surfaces — with deterministic replay for audit and review.

→ READ ARCHITECTURE
⌖ A.03 · DEPLOYMENT MODELS

API, SDK, platform, white-label, hybrid.

Choosing between embedded SDK, hosted platform, white-label deployment and hybrid topology — with data-residency, segregation and operational tradeoffs.

→ READ ARCHITECTURE
⌖ A.04 · GOVERNANCE

Governance, versioning, model risk.

Versioned rules, models and policies. Model-risk management, challenger models, human-in-the-loop approval and the regulator-facing evidence model.

→ READ ARCHITECTURE
§ 05 — Case studies
ANONYMISED · OPERATIONAL

What it looks like in operation.

A small set of anonymised case studies showing how Sophkos has been applied to specific intelligence problems — by banks, EMIs, crypto businesses and investigative practices. Names and identifying details are removed.

01 / EMI

Mule-network disruption inside an EMI portfolio.

Graph and behavioural analytics applied to a payroll-mule cluster operating across roughly 1,800 accounts. Identification, evidence assembly, account action and law-enforcement handoff.

02 / BANK

KYB topology mapping for a correspondent portfolio.

Time-aware ownership and control mapping across nested correspondent and PSP relationships, identifying hidden ultimate exposure to a sanctioned jurisdiction.

03 / CRYPTO

On-chain and off-chain reconciliation for a CASP.

Unified Travel-Rule, sanctions, on-chain attribution and behavioural monitoring across a CASP's user base and wallet topology, with regulator-ready evidence trail.

04 / LAW FIRM

Investigations workspace for a contentious matter.

Entity-centric investigation across multiple jurisdictions: ownership, transactions, OSINT, evidence and decision record assembled into an admissible bundle.

05 / REGULATOR

Supervisory pattern analytics across a sector.

Cross-firm typology analytics for a supervisory authority, identifying systemic patterns and outlier institutions without exposing individual customer data.

06 / LE

Financial intelligence for an active investigation.

Time-bounded financial-intelligence bundle assembled from open sources, public records and partner-provided data for an active law-enforcement investigation.

The reference shelf
behind the platform.

Request the full resource library or a specific briefing for your team.

Request Resource Library