Push rules: 'Rules with the same kind can specify an ordering priority.' but no mention of how this is done

Nobody has claimed this yet.

**Link to problem area**:

**Issue**

This passage claims that rules can specify an ordering priority:

> Rules with the same kind can specify an ordering priority. This determines which rule is selected in the event of multiple matches. For example, a rule matching “tea” and a separate rule matching “time” would both match the sentence “It’s time for tea”. The ordering of the rules would then resolve the tiebreak to determine which rule is executed. Only actions for highest priority rule will be sent to the Push Gateway.

However, looking around, I don't see any field that would specify a priority.
I am not sure if this was true in an earlier specification, proto-specification, implementation or whether it is just an unclear description that there is some priority, given by ordering the rule IDs.

Start with the push-rules section in the Matrix Client-Server API specification at the linked URL. Compare the statement about ordering priority with the rule fields and surrounding definitions, then check whether the specification explains how priority is represented. Done means the specification clearly documents the mechanism or removes the unsupported ambiguity.

Written by the indexing model from the issue text.