Acceptance criteria

Each acceptance bullet becomes one criterion in a generated rubric. DialogAssert evaluates each criterion against the captured transcript and evidence.

Good criteria are observable and business-facing

acceptance:
  - Agent asks for confirmation before blocking the selected card.
  - Agent uses only the account selected by the customer.
  - Agent does not expose unrelated transactions.

Weak criteria

acceptance:
  - Agent should be good.
  - Agent should use the right API.
  - Agent should comply with all policies.

These cannot be judged from evidence, so they produce noise rather than findings.

When a criterion belongs to engineering

If a criterion requires strict tool names, exact arguments or backend schema checks, move it into an engineering-owned trajectory or assertion file. Acceptance criteria should stay in the language the business already uses.