Most enterprise AI pilots do not fail because nobody ran an eval. They fail because the eval had no authority.
A team runs a few golden prompts, checks that the assistant sounds reasonable, screenshots the result into a launch document, and moves on. Two weeks later the retrieval index changes, a model route is updated, a tool schema adds a field, a policy prompt is edited, or an upstream document owner reorganizes a knowledge base. The workflow is now different, but the evidence still describes the old system.
An eval gate is the opposite pattern: a release control that decides whether an AI workflow may move from draft to pilot, pilot to production, production to expanded authority, or production back to containment.










