Research #
- AI Agent Liability: When Your Agent Causes Damage, Who Pays? (MintMCP) — First piece found to lay out a structured liability-allocation framework rather than just noting the gap: model developers limit exposure via ToS, platform providers face infrastructure/permission-system liability, but deploying organizations bear primary responsibility given their control over governance policy. Argues traditional product-liability doctrine (design defect, failure to warn) breaks down for learning/adapting systems, leaving EU AI Act risk tiers and NIST AI RMF as the only frameworks in progress — contractual indemnification/liability caps dominate in the meantime. Central claim: audit-trail completeness is “essential evidence” — orgs without observability infrastructure cannot demonstrate due diligence if sued.
- AI Agent Incident Response Runbook (2026): What to Do When Production Goes Sideways (I Am Stackwell) — A practitioner-authored response playbook rather than a postmortem — notable as a sign vendors’ silence (no published postmortems, per Harper Foley’s founding piece) is starting to be filled by third-party incident-response tooling/process guidance instead.
New Incidents #
- AI Agents Are Deleting Developer Home Directories: The rm -rf ~/ Pattern Hitting GPT-5.6-Sol, Claude CLI, and Claude Cowork (ChatForest) — Names the pattern connecting the three home-directory-deletion incidents already tracked in this journal (Reddit/Claude Code CLI, GPT-5.6 Sol, Claude Cowork family photos) as a single recurring failure class: tilde/
$HOME expansion inside a destructive command with no sandbox boundary. First piece found that explicitly treats these as one taxonomic pattern rather than three unrelated incidents. - AI code wreaked havoc with Amazon outage, and now the company is making tight rules (Digital Trends) — A second, larger Amazon incident beyond the Kiro/Cost Explorer case already covered here: AI-assisted code changes contributed to a March 2, 2026 failure (120,000 lost orders, 1.6M website errors) and a March 5 follow-on outage causing a 99% drop in North American order volume (6.3M lost orders, six hours). Amazon’s response was a 90-day “code safety reset” across ~335 critical systems mandating two-person review — a more substantial process response than the “blamed the humans” framing of the earlier Kiro incident, though still not a public postmortem naming AI as the cause.
Research #
- AI Incidents H1 2026 Retrospective: Failure Modes Analysis (Digital Applied) — Catalogues 50+ public AI incidents through mid-May 2026 across agentic workflows, customer-facing assistants, retrieval pipelines, and back-office automation, with failure modes ranked by root cause and severity — a broader-scope complement to METR’s agent-specific catalog and the arXiv AI Agent Index’s safety-documentation audit.
Liability, Insurance and Governance #
- EU AI Act: What Actually Applies on August 2, 2026 (Accuro AI) — Clarifies that today’s date is not the long-anticipated high-risk-system compliance deadline (the Digital Omnibus pushed that to December 2, 2027) — what actually activates today is the AI Office’s enforcement/fining power over general-purpose AI providers and Article 50 transparency obligations (AI-interaction disclosure, deepfake labeling). Directly relevant to this topic’s governance-standards tracking: the headline deadline enterprises prepared for has moved, but enforcement teeth for a narrower slice of obligations are live now.
- Discussion Paper: Legal Responsibility for AI Agents (IMDA, 2026-05) — Companion discussion paper to Singapore’s already-tracked Model AI Governance Framework for Agentic AI, focused specifically on legal-responsibility allocation across the agent value chain (developer, deployer, end user) — a more detailed treatment of the same developer-vs-operator liability split Clifford Chance’s piece raised.
- Nondeterministic Torts: A Technical Approach to AI Liability (Yale Law Journal) — Academic legal treatment arguing standard tort doctrine struggles with AI systems’ nondeterminism (the same input can produce different outputs) and proposing technical modifications to liability tests to account for it — the most rigorous law-journal-level treatment of the liability question found in this topic so far.
- Governing AI Agents: What the Amazon Outage Reveals about Enterprise Risk (Wharton AI & Analytics Initiative) — Academic/institutional analysis using the Kiro/Amazon incidents as a case study for enterprise AI-agent governance gaps — notable as one of the few business-school-level institutional treatments of a named incident, rather than vendor or law-firm commentary.
Audit Trail and Standards #
- Agent Audit Trail: A Standard Logging Format for Autonomous AI Systems (IETF Internet-Draft) — A concrete draft internet standard proposing a JSON-based logging format with mandatory fields for agent identity, action classification, outcome tracking, and SHA-256 hash-chained tamper-evidence — sits alongside prEN 18229-1 and ISO/IEC DIS 24970 (already tracked) as a third standards body now drafting agent-audit-trail specifications, this time via the IETF rather than a national/regional standards body.
Cross-links #
- AI Code Quality Docker’s ongoing “Coding Agent Horror Stories” series and the IETF audit-trail draft are also relevant to that journal’s tooling/architecture-safety coverage.
- AI Code Architecture Amazon’s 90-day “code safety reset” (mandatory two-person review, ~335 critical systems) is a production-architecture response to agent-caused failure, not just an accountability one.
- Emerging pattern: Amazon’s incident severity is escalating rather than resolving — the Kiro/Cost Explorer outage (Dec 2025, 13 hours) was followed by two larger AI-code-linked failures in March 2026 (120K and 6.3M lost orders respectively), with the vendor’s process response (90-day code safety reset) only arriving after the third, largest incident.
- Source suggestion: The AI Incident Database (incidentdatabase.ai) surfaced this cycle as a structured, citable incident registry (used to cite the Replit incident formally as “Incident 1152”) — worth evaluating as a recurring source alongside METR’s catalog.
- Noise pattern: “AI agent governance” and “AI agent audit trail” searches continue to surface a large volume of near-identical vendor/consultancy explainer posts (futureagi.com, promethium.ai, zylos.ai, decasoftsolutions.com, Cloud Security Alliance research notes) repeating the same NIST AI RMF / ISO 42001 / EU AI Act checklist framing — consistent with the noise pattern already flagged in the 2026-07-27 gather.
- Gap: Still no vendor-published document self-describing as a “postmortem” for a named incident. Amazon’s 90-day code safety reset is the most substantial process response found to date, but it was announced via press coverage of internal policy changes, not a retrospective naming the incident and root cause the way a conventional postmortem would.