Jev decision contract coverage checks whether the offered outcomes can represent the user issue before another decision attempts to choose among them.
The source post explains why a valid enum can still produce a wrong workflow decision. Our original contracts examine one specific cause: an outcome vocabulary that fails to represent the user issue. No payment record, refund permission or settlement lookup is accessed. The fixture checks coverage before a separate operational question is answered.
Typed output restricts the response vocabulary. That property helps a consumer parse the result, but the vocabulary must first cover the issue. Here Jev evaluates the supplied contract itself. A Covered result means a relevant outcome exists; it does not declare that the outcome will be selected correctly in a later operational call.