Yes, we could send it today
No rule fires on this answer, for a product that runs on a third-party or fine-tuned model. A reviewer moves on.
We mean a document your company has formally approved, such as a vendor register, a subprocessor list, or an architecture document someone senior has signed off. It has to name the provider and say where the model runs. A line like "claim summaries are generated by Anthropic Claude, running in AWS in the us-east-1 region" is what a reviewer needs to see. A page in an engineering wiki that nobody has approved does not count, and neither does telling them you use a leading AI provider.
A carrier has to name every third party inside your product in its own examination response, so the reviewer needs a sentence they can copy across. "We use a leading provider" is not something they can write in a regulatory file. Approval matters as much as the content, because a wiki page can change the day after they read it, which is why they ask for a document your company stands behind. When a reviewer cannot close the question on their own side, the safe move for them is to stop and ask you, and that is how a forty minute review becomes a six week queue.
Each outcome below was produced by running Vaulith's rules engine on that answer, for a product that runs on a third-party or fine-tuned model. The same rules run in the paid assessment, on your whole estate, with the arithmetic shown.
No rule fires on this answer, for a product that runs on a third-party or fine-tuned model. A reviewer moves on.
One model (the system you described) runs on a third-party provider that is not named in any approved record. "A leading commercial provider" is not an answer a reviewer can write down. The carrier has to name every third party in its own examination response, so an unnamed provider makes your gap their finding, and a reviewer who cannot close a question in their own file will stop and ask rather than accept it.
The snapshot asks this and eight more, in about ninety seconds, with nothing leaving your browser, and returns every finding with its reasoning and its remediation.