Insurance
Model risk does not stop at the model
Your model governance is thorough. Your code governance assumes a human wrote the code.
Insurers scrutinise the models they deploy. The code that implements pricing, underwriting and claims decisions gets far less attention, and it is now being written with the same AI assistance as everything else. PromptWake records that half of the picture.
Nobody asks how AI-written code entered a repository until something goes wrong or somebody audits it — and by then the record either exists or it does not. PromptWake is cheap to run before you need it and impossible to reconstruct afterwards.
Questions this sector asks
How does this relate to model risk management?
It covers the implementation layer that model documentation usually stops short of: the code that puts a model into production, and who or what wrote it.
Can we limit this to specific repositories?
Yes. Capture is per project, and a policy file can name the directories where AI authorship needs human sign-off.
Is the AI share a compliance metric?
It is a fact, not a target. A high figure is not a finding on its own — what matters is whether it was known, reviewed and recorded.
Underwriting code deserves the scrutiny the model gets.
Start with one rating repository and see what the record shows.