Looking at the 8.5 documentation for XO, there is a cartridge which is responsible for putting all the defined triggers from the
trigger-types.xml to a claim in ADF, the Experience Optimization cartridge.
The Claim Processors used in the Experience Optimization cartridge are packaged in the
Before an XO query is executed, the entire content of the Claim Store is cross referenced against the claim containing the triggers, and and only the matching ones are sent to FH.
This makes perfect sense, yet I cannot find anything similar in Sites 9's XO (using ElasticSearch). Is this filtering now built into the system or where is it?