Reading the network-signals hero

What the hero is

The network-signals hero is the first thing you see on the Signals page: one large number, a pill, a one-line severity summary, and three smaller numbers beside it. It is a summary panel, not a list. Its job is to answer "how much is on fire right now, and how bad is it" in the time it takes to glance at the top of the screen, before you scroll into the rows of individual signal tiles below it. This article covers only that top panel. For the four rows underneath it (Critical & High Severity, By Domain, Recent, Resolved) and for what opens when you click a signal tile, see Signals: your network's early-warning feed.

Every number on the hero is built from the same source: open and recently-resolved rows in your network's signal table, the same cross-network pattern detections the aggregator writes when a meaningful share of your active members hit the same pattern within a severity band. Nothing on the hero reads a single member's private data. It counts patterns, not people.

Where to find it

Open Feed from the HQ sidebar at hq.verinode.ai/signals. The hero sits at the very top of the page, above the Critical & High Severity row, with no section header of its own; it's the page's opening statement, not one of the labeled rows beneath it.

The headline number

The big number, under the eyebrow "Network signals," is your total count of currently open signals, network-wide, across every severity and domain. "Open" means the signal's status is still New or Seen; once a signal is marked resolved it drops out of this count (and shows up in Resolved 30d instead, and in the Resolved row further down the page).

Unlike some hero panels elsewhere in Verinode that show a muted dash when there isn't enough data yet to compute a number, this headline always shows a real integer, including a real 0. Zero open signals is meaningful information here, not a "waiting for data" state, so the panel never hides it behind a placeholder. The number animates with a brief count-up from zero when the page loads; if you catch it mid-animation on a fast reload, that's the count-up running, not a partial number.

Because the headline counts signals and the pill beside it counts domains, the two numbers are not the same thing and won't always move together. A network with five open signals that all happen to be Margin-domain patterns shows a headline of 5 next to a pill reading "1 domain."

The domain-count / All-clear pill

To the right of the headline is a pill that reads one of two things:

• "N domain(s)", for example "3 domains" or "1 domain," where N is the number of distinct domains (Margin, Cash, Carrier, Team, Process, and so on) that currently have at least one open signal. This count comes from the same grouping the By Domain row further down the page uses, so the pill and that row will always agree.
• "All clear," shown only when the headline reads 0.

Every open signal belongs to a domain (a signal with no domain on file still counts under "Uncategorized"), so as soon as the headline is above 0, the domain count is at least 1 too. The pill never shows "0 domains" as its own state; that case is always "All clear" instead.

The pill's color follows its own severity rule, checked in this order, first match wins:

1. If any open signal is Critical severity, the pill is red (Ember Red), regardless of how many High, Medium, or Low signals are also open.
2. Otherwise, if any open signal is High severity, the pill is yellow (Hard Hat Yellow).
3. Otherwise, if there are open signals at all (meaning only Medium and/or Low severity ones), the pill is a neutral gray, the same tone as normal page text, not a warning color.
4. If there are no open signals, the pill is green ("All clear").

The hero is a read, not a filter. Clicking the pill, the headline, or anywhere else on the hero doesn't open a filtered list, there's nothing to click. Use the Critical & High Severity, By Domain, Recent, or Resolved rows below it to drill into the signals behind these numbers.

The severity breakdown subtext

Directly under the headline is a one-line summary of the open count broken out by severity, in a fixed order: critical, high, medium, low, separated by middle dots, for example:

1 critical · 2 high · 0 medium · 3 low.

All four severities are always listed, even the ones sitting at zero. You get the full shape of what's open in one line rather than only the severities that happen to be non-zero.

When the headline is 0, this line is replaced entirely by a plain-language empty state rather than a "0 critical · 0 high · 0 medium · 0 low." sentence:

"No open network-level signals. The aggregator surfaces a signal here when a meaningful share of active members hit the same pattern within a severity threshold."

Verinode deliberately doesn't publish the exact share of the network required to trip a signal, here or anywhere else on the page. A visible trip-wire is a trip-wire a handful of members could learn to stay just under; the threshold stays qualitative by design, the same way cohort sizes stay unpublished on Benchmarks.

The three secondary stats

To the right of the headline (or below it, on narrower screens) sit three smaller numbers, each with its own label and one-line explanation underneath:

| Stat | What it counts | Sub-label | Color rule | |---|---|---|---| | Critical | Open signals at Critical severity only | "Open critical signals" | Red when above 0, green at 0 | | High + Medium | Open signals at High or Medium severity, combined into one number | "Open elevated signals" | Yellow when the combined total is above 0, green at 0 | | Resolved 30d | Signals whose status flipped to resolved in the last 30 days | "Closed in the last month" | Always neutral gray, regardless of the count |

A few details worth knowing:

• High + Medium is a combined figure. It adds High-severity and Medium-severity open counts into one number, there's no separate "Medium" stat on the hero. If you need the Medium count on its own, read it out of the severity breakdown subtext above, or the By Domain row.
• High + Medium's color rule is more sensitive than the pill's. The pill only turns yellow when a High-severity signal is open (Medium alone leaves it gray, per the pill rule above). This secondary stat, by contrast, turns yellow the moment High or Medium is above zero. So it's entirely possible to see a gray "All clear"-adjacent pill next to a yellow High + Medium number, that's not a bug, it's two different rules answering two different questions: the pill is asking "does anything need urgent attention," the stat is asking "how many elevated-severity signals exist."
• Resolved 30d never changes color with its value. A high resolved count is progress, not a warning, so it stays neutral gray whether it reads 0 or 40. Use it as a pace check: a Resolved 30d count that's been climbing after you made a network-level change (a new vendor rate card, a process update, a carrier escalation) is a fast way to confirm the fix actually took, without waiting to hear it secondhand from members.
• Both Critical and High + Medium read green at zero, using the same "Expand" green as the pill's All-clear state, so a genuinely quiet week reads as visually calm across the whole hero, not just the pill.

What the hero doesn't tell you

The hero has no memory of its own history beyond the fixed Resolved 30d window, there's no trend line or week-over-week delta on this panel. If you want to see whether pressure is building or easing over time, that's a job for the Recent and Resolved rows further down the page, read together over successive visits, not for the hero itself.

The hero also can't tell you whether a quiet reading means your network is genuinely healthy or simply that too few members are active or reporting yet for a pattern to trip the aggregator's threshold. An "All clear" pill on a network with very few active members and one with a large, mature, genuinely calm network look identical at this panel. Cross-check a quiet hero against your member count and activity level on Network Health before reading it as a clean bill of health.

1. 1Glance at the headline and pill first, that's your total open count and whether anything needs urgent attention today.
2. 2Read the severity breakdown subtext for the full shape: how many at each of the four severities.
3. 3Check the Critical and High + Medium stats for the two numbers that actually drive action, then Resolved 30d to see whether the backlog is shrinking.
4. 4If the hero reads quiet, confirm it's a genuinely healthy quiet by checking your active member count on Network Health, not just this panel.
5. 5Scroll into Critical & High Severity, By Domain, Recent, or Resolved to work the actual signals behind these numbers, the hero itself has nothing more to click.

Related reading

• Signals: your network's early-warning feed: the full page, all five rows, and what opens inside a signal's detail panel.
• Network Health: your HQ command home: the aggregate-only privacy boundary every number on this page depends on, and where to check member activity when the hero reads unusually quiet.
• HQ overview: how Feed, Network Health, and the rest of the sidebar fit together.
• Broadcasting to your network: turning a pattern the hero flagged into a message to affected members.
• HQ benchmarks: the cohort-comparison counterpart to Signals' pattern-detection feed, and why cohort thresholds stay unpublished the same way the signal fire-threshold does.

Data sources