The 3DS Requestor (e.g. the merchant or its 3DS Requestor Environment) initiates authentication on behalf of the cardholder; the 3DS Client (browser or app) interacts with the cardholder. The Requestor passes transaction and contextual data into the protocol.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.