rules in themes do not display in their priorities order
Hello @macpheri
This won't be want you want to hear, but your uploaded image shows the Style Editor with rules based on the attribute value "ROADCLASS." How your RULES are applied are determined by their top-to-bottom order in the Style Editor. You can move the rules up or down so one rule takes priority over another. Moving the rules up or down affects how the rules are applied not how the linework is displayed.
Although your rules in the Style Editor effectively isolates each RoadClass and makes sure each individual isolated RaodClass is properly displayed, those same rules don't determine the draw order.
If you want to control the DRAW ORDER then you'll need to do that on the Map Task Pane. This means you'll need to reconnect to the feature class multiple times--once for each individual value of RoadClass. That way the feature class will be listed more than once in the Task Pane. For example, if you have 13 separate connections to the road linework, you can perform Draw Order on those 13 connections.
Additionally, you may also apply different linetypes, different line thicknesses and different line colors for each connection.
Rules work well when you need more sophisticated types of display. For example, if your data includes 'YearLastPaved' and you want to display roads paved 2017 or later, i.e. ROADCLASS>='2017'. When you place this rule is at the top in the Style Editor then all roads paved in 2017 and later could conceivably be displayed Thick Green. These green roads wouldn't care if it were LH, HW, AT, CO, LA, LC, etc., etc. Why? Because the rule is at the top and The Top Rule takes precedence over all other rules. Once all the 2017 and later roads are displayed Green, then your other rules, those that isolate LH, HW, AT, CO, LA, LC, etc., would kick in and be applied.
Chicagolooper
