Definition
Acceptance criteria are explicit conditions an outcome must satisfy before it can be accepted, promoted, released, or declared complete. They translate intent into evidence that a reviewer or automated gate can inspect.
Strong criteria cover behavior, quality, risk limits, and side effects. They name the environment, inputs, tolerances, and required artifacts. They also include non-goals where a system could appear successful by doing extra work that was not authorized.
Not every criterion can be reduced to one test, but every criterion should have a verification method and an accountable decision owner. If an agent writes the criteria, performs the work, and judges the result without independent evidence, the process can certify its own misunderstanding.
Distinguish it from nearby terms
Requirements express what stakeholders need. Acceptance criteria state the observable conditions for accepting an outcome. Tests execute some of those checks. A definition of done may also include process obligations such as documentation or review.
Check your understanding
"The page loads" is not enough for a checkout change. Acceptance may also require correct totals, accessible controls, no duplicate charge, an audit event, and a rollback path.