Cross-domain stacks and the synthesizer

What a cross-domain stack is

Most compliance signals are single-domain: an exposure on one policy, an audit coming due, a regulation you're not yet compliant with. A cross-domain stack is different. It's what Verinode's compliance synthesizer finds when several of those single-domain signals share one underlying cause, for example a lapsed certification that is quietly driving an exposure gap, a carrier-program audit risk, and a state-licensing question all at once. Instead of showing you three disconnected findings and leaving you to notice the pattern, the synthesizer packages them into one card: a headline, a root cause, and a specialist-by-specialist action sequence spread across the next 30, 60, and 90 days.

Verinode doesn't act on any of this for you. It reads your exposures, audits, and regulation records, finds where they connect, and lays out a sequence you can hand to the right specialist. You decide what to run with.

Where to find it

Open Compliance from the sidebar (/compliance). Cross-domain stacks show up in two places on that page:

• The Cross-Domain Stacks tile, in the Explore row. It shows a count and a short bar preview, one bar per open stack.
• The Findings tab inside the Compliance card, opened by clicking that tile (or the Cross-Domain Stacks tile takes you straight there). Stack cards render above the regular findings grid, so they're the first thing you see when open stacks exist.

The Cross-Domain Stacks tile

This tile lives in the Explore row alongside Shield Score, Open Exposures, Next Audit, Regulations, Regulatory Autofeed, and Specialist Activity.

• Value: the number of open cross-domain stacks.
• Sub-label: "open N stack(s) from the synthesizer" when there's at least one, or "no stacks, clean posture" when there are none.
• Color: copper when a stack is open, green when the count is zero.
• Preview: a bar for each open stack (capped at 8 bars).
• Click: opens the Findings tab, where any stack cards render above the findings grid.

A clean read here (green, zero) means the synthesizer hasn't found any signals worth connecting into a pattern right now. That's a genuinely good state, not a sign the synthesizer hasn't run.

The stack card, field by field

Each open stack renders as its own card above the findings grid. Above the cards, a line reads "N cross-domain stack(s) this sweep," telling you how many the synthesizer surfaced in its most recent pass.

Header row. Three things sit across the top of every card:

• CROSS-DOMAIN STACK, the eyebrow label identifying the card type.
• "$X/mo cost of inaction", shown only when the synthesizer has a dollar figure for what leaving the pattern unaddressed is costing you every month. If there's no figure, this is omitted entirely, not shown as a dash.
• "N linked signals", on the right, the count of individual atomic signals (the separate exposure, audit, or regulation findings) that this stack pulled together into one story.

Headline and synthesis. Below the header, a bold headline names the pattern in plain language, followed by a paragraph explaining what the synthesizer found and why the pieces belong together. This is the narrative: it's what turns three isolated data points into one decision.

Root cause. An italic line reading "Root cause: ..." names the single underlying driver the synthesizer traced the pattern back to, for example a specific lapsed requirement or a documentation gap. This line is only shown when the synthesizer identified a root cause; some stacks surface the pattern without pinning down a single driver, and the line is simply absent in that case.

Action sequence. This is the core of the card: a numbered list of steps, each showing a horizon and a specialist assignment.

• Each step has a number (its position in the sequence).
• A horizon chip (30d, 60d, or 90d) shows when that step should happen relative to today. Steps are ordered so the nearest-term move comes first.
• A specialist chip names which of Verinode's compliance specialists is best suited to that step, for example Insurance, Regulatory, Cert Renewal, Program Eligibility, OSHA, State Licensing, Carrier Program, Contract, Audit Simulator, or Environmental Disposal. This tells you exactly who to route the conversation to instead of leaving you to guess which of the compliance specialists on standby is the right one.
• The action text itself describes the concrete move for that step, written the way you'd hand it to a colleague.

The sequence is intentionally short-to-long: 30-day steps are the ones you should not sit on; 90-day steps are the ones that close the loop once the near-term moves land.

Actions. Four controls sit at the bottom of every card:

• Act: the primary button. It logs that you acted on the stack and takes you straight to that stack's page in the decision workspace, where you can work the sequence.
• Not now: parks the stack. It disappears from the Findings tab immediately and Verinode brings it back later on an escalating schedule (sooner the first time you park something, further out if you keep parking the same one), so it isn't gone, just out of your way for a while.
• Ignore: dismisses the stack outright and records that you dismissed it. It also disappears from the Findings tab, with no future resurfacing built in.
• Acknowledge with note: opens a dialog where you can leave a short note and pick a reason: Mitigation planned, Accepted as risk, False positive, Already resolved, or Deferred. Use this when you want the stack on record as handled (or knowingly deferred) without routing through the decision workspace at all, for instance when you've already dealt with the underlying issue outside Verinode.

Once you click Not now, Ignore, or save an acknowledgment, that card is removed from view for the current visit. Clicking Act navigates you away to the decision workspace.

How the synthesizer builds a stack

The stacks you see are the output of a background synthesizer that looks across your open compliance signals, exposures, audits, and regulations, for cases where multiple findings trace back to one cause. When it finds one, it writes a single signal of its own (distinct from the individual findings it's built from), carrying:

• the headline and narrative you read on the card,
• the root cause, when one is identifiable,
• the 30/60/90-day action sequence with per-step specialist routing,
• a monthly cost-of-inaction figure, when the underlying signals support one, and
• the list of the individual signal IDs that were linked together to build the story.

A stack only shows up on the Findings tab while it's still open, meaning it hasn't been acted on, parked, or dismissed. Once you've worked through or set it aside, it stops appearing here (though, as noted above, parking brings it back on a schedule rather than clearing it for good).

Empty states

• Zero open stacks, Cross-Domain Stacks tile: the tile shows 0 in copper-free green with "no stacks, clean posture." This means the synthesizer currently sees no signals worth connecting, not that it hasn't examined your data.
• Zero open stacks, Findings tab: the stack section above the findings grid simply doesn't render (no header, no "N cross-domain stacks this sweep" line, nothing). The findings grid below it still shows your regular single-domain findings, or its own empty state ("No decisions for compliance right now. As your agent finds patterns, they'll appear here.") if there are none of those either.
• No compliance data at all: if you haven't sent Verinode any compliance data yet, the Compliance page's Take Action row shows a setup prompt ("Get your compliance posture on the radar") rather than any findings or stacks, prompting you to upload a COI or carrier-program audit, forward an audit notice or regulator email, or paste in a regulation update or compliance memo. Cross-domain stacks can only form once there's more than one domain's worth of data to connect.

Best-practice example

Say the Cross-Domain Stacks tile reads "1, open 1 stack from the synthesizer" in copper. You click through to Findings and see a card headlined around a lapsed certification. The synthesis explains that the same lapse is behind an open exposure gap and an upcoming carrier-program audit risk, the root cause line names the specific certification, and a cost-of-inaction figure puts a monthly number on leaving it as is. The action sequence gives you three steps: a 30-day move routed to Cert Renewal, a 60-day move routed to Insurance, and a 90-day move routed to Carrier Program. Rather than working three separate findings in three different tabs and hoping you notice they're related, you click Act, land in the decision workspace for that stack, and start with the 30-day step. If you're mid-renewal on the cert already and just need it off your plate for a couple of weeks, Not now is the right call instead: it'll resurface once there's been time to make progress.

Related reading

• The decision workspace, for what happens after you click Act.
• Connecting your data, for the fastest ways to get compliance data flowing in.
• Forwarding documents, for routing audit notices and regulator emails automatically.
• How benchmarks work, for how Shield Score and framework completeness compare against peers.