Predictika · Restricted Party Screening Check
Alder Industrial Supply, a fictional maker of industrial sensors, lets an AI agent handle export orders. Before the agent ships, holds or declines an order, the call goes to Predictika’s Restricted Party Screening Check. It checks the destination, the screening result for the buyer, how much of the buyer is owned by listed parties, whether the item is controlled, the license position, how long ago the buyer was screened, any diversion red flag, and any approval on record. Then it returns one verdict: allow, needs approval, or block.
Not legal advice. Alder Industrial Supply is fictional. The scenarios are illustrative. The rules are a simplified model informed by US export control and sanctions rules; they have not been reviewed by a lawyer or trade compliance specialist, and the legal citations were not checked against the primary text in this build.
This validator decides one thing: whether one proposed action on one export order may go ahead, given the screening facts. It is not a screening tool and not a legal opinion.
Within these rules the validator handles any combination of the listed facts, not just the seven scenarios on this page. It does not run the list screening, read the license, or classify the item; those results are taken as stated facts. The country tiers are illustrative company policy, not a government country chart.
The validator takes facts as inputs: the destination country, the action, the screening result for the buyer, the percentage of the buyer owned by listed parties, whether the item is ordinary or controlled, the license position, the days since the last screening, any diversion red flag, and the approval on record. These come from the screening and order systems at the moment of the call. The validator never sees the buyer, the list or the license itself.
Two honest limits. The validator judges the facts it is given: if the screening result is wrong, the answer follows it. And an order that never calls the validator is not checked; in this demo the agent calls it itself, and in a deployment the order workflow makes the call.
7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch
Illustrative agent statement. The validator receives the structured request below.
Proposing agent: AI agent (scripted)
Before sending, the agent must call Recorded run
What this means
General statements about screening and order tools, not about any named product. We rest this on public descriptions of how such tools work; anyone running a specific product will know it better than we do.
| What the validator caught | Typical tool | Predictika |
|---|---|---|
| Adding up ownership across listed parties | Cannot do it Name-screening tools match the buyer’s own name. They do not total how much of the buyer listed parties own, or apply the 50 percent line, unless ownership data and a rule are added. | Every rule is checked on every call and the verdict lists each finding. |
| Reading item class, destination and license together | Only if someone is vigilant An order system can hold each field. Stopping a shipment when they do not line up, and asking counsel when a license is held, needs a rule across all three. | Every rule is checked on every call and the verdict lists each finding. |
| Reporting every finding at once | Only with workarounds Many tools stop at the first hit. A complete list for one order, with the level of approval needed, takes a rule set built to return it. | Every rule is checked on every call and the verdict lists each finding. |
| Buyer is on the restricted party list | Only if someone is vigilant A screening tool returns a match. Stopping an agent from shipping anyway needs a rule that reads the result on each order. | Every rule is checked on every call and the verdict lists each finding. |
| Listed owners hold 50 percent or more | Only with workarounds Name screening tools match names. Adding up ownership across parties and applying the 50 percent line needs ownership data and a rule that reads it. | Every rule is checked on every call and the verdict lists each finding. |
| Controlled item with no export license | Only if someone is vigilant An order system can hold a license field. Stopping a shipment when the item class, the destination and the license do not line up needs a rule across all three. | Every rule is checked on every call and the verdict lists each finding. |
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the request; approval findings need a person to sign off first.
| 1 | The buyer is an exact match on the restricted party list. No shipment may go ahead (EAR Part 744; OFAC sanctions regulations). |
| 2 | Iran is under a comprehensive embargo, so no shipment may go there (OFAC sanctions programs). |
| 3 | Listed parties own 60 percent of the buyer, at or above the 50 percent that makes the buyer restricted too (OFAC 50 Percent Rule). |
| 4 | This controlled item going to China needs an export license and none is on file (EAR Part 742). |
| 5 | A license exception is claimed, but none covers a controlled item going to China (EAR Part 740). |
| 6 | The buyer is a possible match on the restricted party list. Compliance must clear or reject the match. |
| 7 | Listed parties own 35 percent of the buyer, close to the 50 percent line. Compliance must review the ownership. |
| 8 | A diversion red flag is recorded for this order. Compliance must review it (BIS Know Your Customer guidance). |
| 9 | The buyer was last screened 10 days ago, over the 7 day limit (company policy). Screen again before shipping. |
| 10 | A license is on file for this controlled item going to China. Export counsel must confirm it covers this item, buyer and quantity. |
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.
The agent's request. I'm shipping this order of sensors to the buyer in Germany today. Germany is an open destination and the items are ordinary.
Verdict: Blocked.
The agent's request. I'm shipping an order of sensors to a different buyer in Germany. This buyer was screened yesterday and is clean.
Verdict: Allowed.
The agent's request. I'm shipping this order. The buyer is not on the restricted party list, even though listed parties own 60 percent of it.
Verdict: Blocked.
The agent's request. I'm shipping these sensors to our customer in China. The buyer is screened and clean.
Verdict: Blocked.
The agent's request. I'm shipping the sensors to our customer in China again. We now have an export license on file.
Verdict: Needs approval.
The agent's request. I'm shipping the sensors to our customer in China. Export counsel has confirmed the license covers this order.
Verdict: Allowed.
The agent's request. I'm shipping this order to the buyer in Iran. Listed parties own 60 percent of the buyer and there was a flag on the order, but the buyer says it is for ordinary use.
Verdict: Blocked.
The text of the narrated walkthrough, step by step.