Checks / AI liability and damages / supplier and deployer responsibilities split in contract
AI liability and damages
Civil Liability (Contribution) Act 1978 - supplier and deployer responsibilities split in contract
This control asks you to show: supplier and deployer responsibilities split in contract. Who pays when AI causes harm: negligence, unfair contract terms, contribution between supplier and deployer, data protection compensation, discrimination claims and latent damage.
What evidence passes
The check reads the field
liability_allocation in the decision or governance record. It passes when that field is present and not empty. Anything else fails, with the reason stated.Check it now
Free, no account. You get PASS or FAIL, the reason, and a tamper-evident receipt.
Run it from your AI assistant
Connect
https://sebbi.pro/mcp to Claude, ChatGPT, Cursor or any MCP app, then call:sebbi_run_check {"check": "sebbi_aidamages_004", "record": {"liability_allocation": "..."}}Or run every AI liability and damages control at once with sebbi_run_framework. How to connectRelated AI liability and damages controls
- Negligence - duty-of-care risks from AI outputs assessed
- UCTA 1977 s.2(1) - no exclusion of liability for death or injury caused by AI
- UCTA 1977 s.11 - AI liability caps reasonable and documented
- Supplier contracts - indemnities cover AI model failures
- UK GDPR Art.82 - compensation risk from AI data handling assessed
- Equality Act 2010 - AI decisions tested for discrimination