Everything the semantic layer defines meets here. The card carries eleven distinct signals; the design problem is ordering them so an operator triaging four hundred findings by keyboard reads the right one first.
For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set.
For all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set.
The list pane is where an operator spends the day. Each option keeps every signal reachable and differs only in how many it shows before you ask. Pick one as the default — the other two can stay as a view control.
Severity as a bare meter, status and staleness as two mono glyphs. Roughly 30 findings visible at once. Everything else on selection, in the detail pane.
Title first, badges as a second line that wraps. Around 12 findings visible. The compromise option: labels stay legible, criterion and page stay on the row.
A fixed 68px gutter holds severity and status in a constant position, so the eye tracks one column down the list. Metadata collapses to one mono line. Around 17 visible.
Findings bind to captured evidence, never to what someone remembers seeing. The viewer's job is to make the binding obvious, and to keep snapshot and live modes impossible to confuse.
Mode is a two-state control, not a checkbox: the active half is a filled ink block reading SNAPSHOT V4. In live mode the same block turns amber and the viewport takes a 2px amber frame — the one place the alarm colour is allowed to describe a mode rather than a change.
2.4.3 evidence, and the thing no competitor ships. Every focus stop in order, the travel between them drawn to scale, and traps marked where the path closes on itself.
The signal bundle is stored rather than hashed, so the SME can always see why two findings were linked. Both of these components exist to make a machine judgement inspectable.
One definition of the sign-off gate, stated the same way everywhere it appears: the manual lanes are empty and the manual track's coverage is complete for this version. Nothing else closes it.
The capture engine may run on another machine, so a failure has to be diagnosable without shelling into a container. The panel's hard rule is on its face: bundles carry logs, never captured client evidence.