This is the tier that crosses the boundary. Tool, report and Jira embed all resolve to these. Read every specimen as glyph + label first, colour second.
Rule 02 makes the glyph the primary encoding, so it cannot be a Unicode character borrowed from the font. Hestia’s Icon set is mounted directly wherever it has an equivalent. It was authored for a marketing site, so it carries no staleness, source or matcher marks — those are drawn here in the same convention and recorded as an extension, exactly as the dark theme is. One equivalent was considered and declined: Icon.loop is the brand’s two-loop process motif, a rectangular circuit standing for a cycle that runs. Regressed means a fixed finding came back, which is a reversal rather than a cycle, and the circuit’s four subpaths mush at the 10px the list gutter uses. It is drawn as a circular return arrow and recorded below.
24×24 box, 1.5px stroke, round caps and joins, no fill — Icon’s own drawing convention, so the two sets sit together without a seam. Inside a chip the glyph scales to its text and the stroke scales inversely, so the drawn weight holds at 11px instead of thinning to a hairline.
Severity and match confidence are not icons; they are readings. They stay filled segments on a fixed geometry, because a meter has to be countable at a glance and comparable down a list — the same reason the focus map keeps filled nodes. Fixed pixels, not em, so the bars align across rows whatever type size the chip uses.
The system restricts Unicode marks to schematic arrows in mono contexts, and rules out filled consumer-app forms. The four filled marks this page started with are gone; every state icon is now a 1.5px line drawing that inherits its text colour and scales with the chip. Two things stay filled on purpose, and both are declared above: the measurement marks, which are readings rather than icons, and the focus map’s diagram nodes, which the system draws as schematic SVG by design and which the legend keys in their own colour.