Expected case
Input: [valid case]
Expected: [output/action]
Evidence: [test record]
Owner: [name/role]
Accessible HTML template · Blank matrix
Event AI production acceptance matrix.
Define evidence, expected behavior and a named owner for each scenario. Add cases from the real event operation; do not treat this starter list as complete.
Ambiguous input
[Conflict, missing identifier or incomplete authority.]
Expected: expose uncertainty and route review; no silent guess.
Duplicate or stale input
[Duplicate detection, material difference handling and stale-source boundary.]
Permission change
[Fail-closed behavior when a user, token or source loses authority.]
Provider failure
[Timeout, unavailable model/connector/destination, incomplete output and controlled retry.]
Adversarial or prohibited request
[Unsupported instruction, data request or action; refusal and intervention evidence.]
Manual fallback
[Who acts, which evidence is preserved, how service resumes and what gets reviewed.]
Acceptance decision
[Pass / conditional / fail], [date], [approver], [open conditions and expiry].