blog: prove you had controls — agent liability in 2026 (publish 7/23)#780
Open
amavashev wants to merge 2 commits into
Open
blog: prove you had controls — agent liability in 2026 (publish 7/23)#780amavashev wants to merge 2 commits into
amavashev wants to merge 2 commits into
Conversation
Tier-2 post, publish date 2026-07-23. Three verified pressures — CMA March 9 guidance (deployer liability, DMCCA 10% fines), Clifford Chance contract-gap analysis (incl. missing decision-log rights), and the forming AI insurance market (Munich Re aiSure, Armilla) — converging on deployer-owned, signed decision records. Insurance claims grounded in Armilla's published underwriting approach per fact-check. Review cycles 1-2 + codex (SHIP round 1) applied.
Apply 0 / modify 1 / skip 0 (reviewer round 1, High finding): - MODIFIED, date stands: reviewer read the original SB 942 text (operative Jan 1, 2026). AB 853 (signed Oct 13, 2025) moved the covered-provider operative date to Aug 2, 2026 - verified against Orrick and Troutman Pepper analyses and consistent with the merged EU AI Act explainer (#773). Added "as amended by AB 853" inline so readers checking the unamended bill text don't hit the same trap.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prove You Had Controls: Agent Liability in 2026 — publish date 2026-07-23. Tier-2 batch post 4/5.
Three verified pressures converging on deployer-owned decision evidence: the CMA's March 9 guidance (deployer liability, DMCCA fines to 10% of global turnover without court), Clifford Chance's contract-gap analysis (including the missing right to decision logs), and the forming AI insurance market (Munich Re aiSure, Lloyd's-market Armilla — both verified real and correctly characterized). The commercial "so what" for the June evidence series.
Review trail
Fact-check (CMA/Clifford Chance/TLT paraphrases verified against sources; insurance underwriting claim grounded in Armilla's published approach per reviewer insistence) + set-level style agent (legal-advice hedges, chronology fix, clone-sentence de-dup) + codex (SHIP on round 1).
Merge notes
Test plan