Write measurable acceptance criteria for the approved mission before code changes begin.

Cover expected behavior, accessibility, data integrity, authentication, authorization, validation, error handling, performance appropriate to the mission, observability, and rollback. For every privileged success path, include the corresponding unauthenticated, unauthorized, cross-boundary, malformed-input, missing-resource, and failed-dependency behavior when applicable.

Map each criterion to proposed automated tests, runtime checks, browser evidence, or human review. Identify criteria that cannot yet be tested and explain why. Do not implement the tests or redefine business policy without approval.