LOADING
FINDS, ASSEMBLES AND RENDERS
The layer above the Cloud. Ask for what you need and it retrieves from the shared services, assembles the cards the task requires, and renders a workspace that exists only while you are using it.
Locates a merchant, an application, a document or a transaction across services, without knowing which module it lives in.
Reads back why a merchant is blocked, which gate stopped a transaction, and which assumption made an opinion stale.
Builds an underwriting package, a dispute evidence packet or a compliance review from records that already exist.
Surfaces what changed, what expires soon, what drifted, and which patterns in the data are worth a human looking at.
In plain language. There is no menu path to learn and no module to open first.
Which merchant, which application, which transaction — disambiguated before anything is retrieved.
Against the asker's role and row scope. Fox cannot surface what the person could not otherwise open.
From the services that hold the answer, reading the same rows every surface reads.
Into Cloud Cards chosen for the question rather than a fixed dashboard layout.
A workspace that exists while it is being used and is not saved as a page.
Any action is presented for a person to take. Fox prepares; it does not execute decisions.
It does not underwrite, approve, decline, price, classify severity or move a merchant's state. Those decisions belong to deterministic rules, to the acquirer, to the bank or to counsel. This boundary is written into the merchant certifications, and it is what lets a regulated partner supervise the platform at all.
Ask whether a support agent can close a finding. It retrieves the no-suppression rule and the Compliance Engine's never-holds list — assembled, not authored.
