Compliance
Kepatuhan
Meeting the legal rules that apply to what you built, in the place you built it.
Compliance means the system you built obeys the laws of the jurisdictions it runs in. For AI that usually means a mix of general data protection law, sector rules, and newer AI-specific regulation.
The obligations that reach engineering teams most often are transparency about automated decisions, a way for a person to contest an automated outcome, and documentation of what the system does. These are mostly design requirements, not paperwork: a system that can explain a decision and route it to a human is compliant in a way one that cannot is not.
Two practical notes. Rules differ by country, so a system built for one market often needs adjusting for another. And the obligations scale with how consequential the system is: a tool that summarises meeting notes and one that decides who gets fired are not in the same category.
Related terms
Data Privacy
The rules about whose personal data you may hold, and what you must do with it.
Guardrails
Checks that stop or constrain an action before it happens.
Human in the Loop
A person who reviews, approves, or corrects the agent's work at key points.
PII
Information that identifies a person, directly or through a combination of details.
AI Act
The EU's rules for AI, tiered by how risky the system is.
Want this working inside your team?
It starts with one conversation about your workflow.