Industries / Architecturejilsovereign.com/products/industries/architecture
Architecture

Industries Architecture

eleven verticals, one Verdict Engine - same kernel, applied differently

Same Verdict Engine, same CourtChain™ seal, same FRE 902(14) evidentiary standard, applied across every industry that moves money under regulation. No fork. No translation layer. No vendor per vertical.

8
Verticals live
175
Total checks
Same
Verdict Engine kernel
FRE 902<
em>/Standard across all 8

§ 01Business Architecture

AudienceCross-vertical buyers: financial institutions, healthcare/MCO, insurance, government vendor & entitlement, card networks, capital-markets custodians, legal/asset-investigation firms.
BuyerVaries by vertical - Compliance, BSA, GC, CCO, RADV lead.
Economic ModelVertical-specific pricing within shared engine. Volume discounts cross-vertical for buyers that span multiple use cases.
PartnersVertical-specific data partners (Plaid, ATTOM, Refinitiv, OpenCorporates).

§ 02Technical Architecture

Shared kernel

Same Verdict Engine, same CourtChain™ seal, same BFT validator quorum across all 11 verticals.

Per-vertical config

Each vertical loads its applicable subset of the 175 checks + its data sources + its evidentiary requirements.

Cross-vertical UBO

Single UBO graph used across verticals - a sanctioned entity flagged in one vertical surfaces in all others.

Single CourtChain™

All 11 verticals' CREBs anchor to the same chain. Cross-vertical fraud patterns visible.

Customer Snowflake

Customer-tenant storage; JIL holds no PHI/PII at rest.

Data SourcesVertical-specific (see individual vertical use-case pages); shared sanctions/UBO/exclusion feeds across all 8.

§ 03Process Flow

01
Customer onboards
Vertical(s) selected, data partners configured, customer-tenant Snowflake provisioned.
02
Cases ingested
Pre-settlement claims, retroactive batches, KYT screenings - vertical-shaped.
03
Verdict Engine runs
Applicable check subset for the vertical. Cross-vertical UBO consulted.
04
CREB™ sealed
Same evidentiary standard FRE 902(14) regardless of vertical.
05
Cross-vertical insight
Recurring counterparties surface across verticals; same UBO graph.

§ 04Plain English Example

Worked example

Plain English: a single bad actor flagged in 3 verticals

A medical billing company submits Medicare claims (Healthcare). Same beneficial owner runs an unrelated LLC processing ACH payroll fraud (Financial Institutions). Same beneficial owner's spouse is listed as PI on a $500K NIH grant (Grants). When the medical billing company gets flagged for upcoding, the cross-vertical UBO graph immediately surfaces the ACH fraud pattern + the grant-PI relationship. Verdict CREB™ filed in all three verticals references the same canonical UBO record.

§ 05Capabilities Summary

VerticalsBanks, MCOs, insurance, government vendor, government entitlement, card networks, custodians, legal/asset investigation
Shared kernelSame Verdict Engine + CourtChain™ - no fork per vertical
Cross-verticalSingle UBO graph + single sanctions cache means a flag in one vertical is visible in all
PricingVertical-specific within shared engine; cross-vertical volume discounts
Data residencyCustomer-tenant Snowflake per vertical; JIL holds zero PHI/PII at rest