The card being read, and the lens reading the storeColour is the pillar: amber bottleneck (6), indigo cost (7), teal config (1). Lit rows are rows the rule matchedF breaks the selected rule: it prints an error ticket and the rest still runThe engine runs all 14 rules, in id order, each as one SQL query over the store (tables spans, span_events, events, metric_points, and the views built on them). Every row a query returns is one finding with a severity, an impact, a recommendation and evidence spans; a rule that matches nothing prints nothing. Findings are sorted high, medium, low, then error, and by impact within each. The tickets here are synthetic examples.