System map

High-level view of how a banking application, MasteryHive services, vendors, storage, events, and people interact. This page deliberately omits repository paths, secret names, and deploy flags.

flowchart TB
  subgraph people [People]
    analyst[Investigators_and_ops]
    onboard[Onboarding_and_compliance]
    finance[Finance_ops]
    eng[MasteryHive_and_partner_engineers]
  end

  subgraph bank [Banking_application]
    dash[Dashboard_and_APIs]
    users[Authenticated_bank_users]
  end

  subgraph mh [MasteryHive]
    fraud[Fraud_and_TM_services]
    kyc[KYC_KYB_service]
    recon[Reconciliation_services]
  end

  subgraph vendors [External_vendors]
    idv[Identity_and_screening_vendors]
    llm[Model_providers]
  end

  subgraph data [Data_and_events]
    events[Event_bus]
    store[(Operational_and_analytical_stores)]
    files[Object_storage_for_files]
  end

  users --> dash
  analyst --> dash
  onboard --> dash
  finance --> dash
  eng --> mh

  dash --> fraud
  dash --> kyc
  dash --> recon
  fraud --> dash
  recon --> dash

  fraud --> events
  events --> fraud
  recon --> events
  events --> recon

  fraud --> store
  kyc --> store
  recon --> store
  kyc --> files
  recon --> files

  kyc --> idv
  fraud --> llm
  kyc --> llm
  recon --> llm

Interaction summary

Actor	Interacts with	Purpose
Banking application	Fraud, KYC, Reconciliation APIs / events	Request checks, scores, screening, ingestion, exception resolve; receive reports and status
Investigators / ops	Banking dashboard	Review fraud reports and (where implemented) cases
Onboarding / compliance	Banking dashboard → KYC	Drive customer due diligence journeys
Finance ops	Banking dashboard → Reconciliation	Upload statements/GL, review matches and exceptions
Identity / screening vendors	KYC (server-side)	Prembly-style ID/doc checks, OpenSanctions, adverse media search, etc.
Model providers	Fraud / KYC / Reconciliation (server-side)	Narratives, extraction, matching assist — policy decisions stay in application code where documented
Event infrastructure	Fraud and Reconciliation	Fan-out baselines, report compose, worker sessions, exception resolve
Stores / files	All products	Profiles, sessions, matches, audit rows, uploaded documents

Trust boundaries (conceptual)

1. Bank users authenticate to the banking application — not directly to MasteryHive with end-user passwords.
2. Partner backends call MasteryHive with the product’s documented auth/scope contract.
3. Vendor credentials stay on the MasteryHive (or agreed) server side.
4. Internal worker and mesh calls are platform-operated; partners use published entry points.

For product depth without internals, see the platform overview. For code-level architecture, use the internal Engineering site.