Incident chronicle: documented consequences, not forecasts

Our chronicle collects cases where an AI system left a documented consequence: a court ruling, a fine, a ban, an official statement. Every entry links to a primary source.

An incident is a card, not a verdict An incident is a card, not a verdict
An incident is a card, not a verdict

An entry is included only if a document exists. Consequences without a record are not counted, and cases where the link to AI is asserted only by a journalist are marked as such or left out.

The scope is narrow on purpose: this is a Russian-language record of documented cases, not a global registry and not a forecast. Where an area is empty in public records, we say so instead of filling it with estimates.

The data is published with identifiers so that others can re-check it. Corrections are published as corrections, with the date and the reason, rather than edited quietly.

Materials on this topic

Other topics

AI red teaming: what a test shows, and what it does notAI standards: where the rules actually applyAI supply chain: what enters before the model runsMulti-agent systems: behaviour between the agentsBehavioural audit: how agent behaviour drifts over timePrompt injection: where text becomes an instructionRussian practice: who is held responsible for AIMethodology: how the Institute tests AI systemsData and benchmarks: what our conclusions rest onSociology of AI: relations between the agentsGovernment customers: how to commission a testGovernance and funding of the InstituteCases: scenarios of work and what they show

Page updated 02 November 2026 · site build 2026.11.13 · ANO «ISAIS»