Engine reference

Regulator matching

Regulator matching is the deterministic process that produces the regulator list shown on every diagnosis and validation report. The process takes five inputs and returns an ordered, deduplicated set of regulators.

What regulator matching is

Regulator matching runs once per diagnosis against the financial-economy overlay catalogue. The result is a list of regulators, each with a citation and a jurisdiction code, rendered on the regulator block of the result page and on the masthead of the diagnosis and validation PDFs.

The five inputs

  • Customer jurisdiction. ISO 3166-1 alpha-2 code.
  • Data-subject geographies. Set of ISO 3166-1 alpha-2 codes.
  • Sector. One of the twelve catalogue keys.
  • Industry. One of the catalogue's industry slugs.
  • Model name. One of the catalogue's seventy-six model types.

The six-step resolution

Each diagnosis runs the same six steps in the same order.

  1. Normalise the inputs.
  2. Sanctions filter, EU-only at v0.1.
  3. Home rule.
  4. Data-subject rule.
  5. ALL-or-ALL rule.
  6. Deduplicate and sort.

Sanctions scope

IADTX OU is an Estonian entity. EU consolidated financial sanctions are the only sanctions scope binding the operator at v0.1. The comprehensive codes North Korea (KP), Syria (SY), and Iran (IR) trigger an early-exit. Eighteen partial codes are recorded and surfaced in the result UI as a watch-list, with no automatic deny on the diagnosis itself.

Refresh cadence

The sanctions catalogue refreshes hourly against the EU consolidated feed. Removals alert the operator and merge through a signed admin endpoint, sub-five-minute live-deny once confirmed.

Where you see this in the product

The regulator block on the result page renders the matched list with citations. The diagnosis and validation PDF mastheads render the same list as a chip strip. The full list survives into the audit log for every download.