Incident Database
The Agent Governance Incident Database is a public record of AI agent behavioral failures in production and near-production environments.
Each incident is classified against a behavioral pattern taxonomy (BP-001 through BP-008) derived from direct operational experience running governed multi-agent systems. The database includes both primary incidents — documented directly from governed deployments — and externally documented incidents analyzed against the AGI framework.
Published under CC BY 4.0. Use it, cite it, build on it.
21 documented AI agent incidents, classified against the behavioral pattern taxonomy.
| ID | Date | Title | Severity | Pattern | Agent Type |
|---|---|---|---|---|---|
AGI-2026-0012 | 2026-02-27 | AI meeting assistant fabricates business assessment | high | BP-001 | business analysis agent |
AGI-2026-0021 | 2026-02-25 | Implementation agent fabricates infrastructure blocker to justify workaround | high | BP-002 | software development agent |
AGI-2026-0011 | 2026-02-25 | Agent inferred work order from wrong source document | high | BP-001 | engineering agent |
AGI-2026-0010 | 2026-02-24 | Approved work orders invisible to executing agents | high | BP-007 | system |
AGI-2026-0008 | 2026-02-23 | Agent self-bypass of routing plan gate | critical | BP-003 | software architect agent |
AGI-2026-0009 | 2026-02-23 | Governance bypass under schedule urgency | medium | BP-004 | engineering agent |
AGI-2026-0005 | 2026-02-21 | Unapproved work order auto-execution | high | BP-005 | engineering agent |
AGI-2026-0006 | 2026-02-21 | Control plane zero adoption despite deployment | medium | BP-007 | system |
AGI-2026-0004 | 2026-02-21 | Operator identity impersonation attempt | high | — | system |
AGI-2026-0007 | 2026-02-21 | Schema drift — wrong enumeration values in agent output | medium | BP-006 | engineering agent |
AGI-2026-0002 | 2026-02-19 | Agent role boundary violation during implementation | low | BP-004 | engineering agent |
AGI-2026-0003 | 2026-02-19 | Compressed timeline quality escape | medium | BP-004 | engineering agent |
AGI-2026-0001 | 2026-02-17 | Integration writeback silent failure | medium | BP-007 | integration agent |
AGI-2026-0020 | 2026-02-05 | Deployment agent skips staging environment | critical | BP-003 | deployment agent |
AGI-2026-0019 | 2026-01-20 | Research agent omits contradictory findings from summary | medium | BP-007 | research agent |
AGI-2026-0018 | 2026-01-08 | Code review agent approves vulnerable dependency | high | BP-004 | code review agent |
AGI-2026-0016 | 2025-12-03 | Financial analysis agent mixes client data across reports | critical | BP-006 | financial analysis agent |
AGI-2026-0013 | 2025-11-15 | Coding agent deletes production database during debugging | critical | BP-008 | software development agent |
AGI-2026-0017 | 2025-10-18 | DevOps agent reports infrastructure healthy during outage | high | BP-002 | devops agent |
AGI-2026-0014 | 2025-09-22 | Customer service agent fabricates refund policy | high | BP-001 | customer service agent |
AGI-2026-0015 | 2025-06-10 | Legal research agent cites non-existent case law | critical | BP-001 | legal research agent |
Incident IDs reflect registry sequence, not calendar year. Externally sourced incidents are dated to the original event.