AI standards: where the rules actually apply

Regulation moves slower than deployment. We map what is binding today, what is still a draft, and where the two diverge, so a team can plan against the text rather than the headline.

You compare against a reference, not an opinion You compare against a reference, not an opinion
You compare against a reference, not an opinion

Our map separates binding acts from guidance and drafts. Each entry carries the article, the date it takes effect, and what it obliges in practice: documentation, disclosure, or a risk assessment before deployment.

The gap we see most often is not in the rules but in the reading. A requirement written for providers is assumed to bind deployers, or a voluntary code is quoted as a legal duty. We mark that difference explicitly.

This is a map, not legal advice. It shows where a requirement exists and what evidence would satisfy it. The compliance decision stays with the organisation and its lawyers.

Materials on this topic

Other topics

AI red teaming: what a test shows, and what it does notAI supply chain: what enters before the model runsMulti-agent systems: behaviour between the agentsIncident chronicle: documented consequences, not forecastsBehavioural 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»