Using Nexus

Nexus is the crosswalk tool — where you load regulatory frameworks, map expectations to controls, and make the relationship between obligations and governance visible.

Nexus is where the crosswalk lives. Its job is to make the relationship between external obligations — from regulations, standards, and contracts — and your internal governance controls visible and navigable.

The core workflow is straightforward: load a regulatory artefact onto a board, navigate its structure, map individual clauses and requirements to the controls in the unified framework, and let the crosswalk build up over time. The value compounds as more artefacts are loaded and more mappings are confirmed, because patterns that are invisible when you look at regulations one at a time become legible when they share a common control structure.

The four views

Every board in Nexus has four view modes, accessible from the header:

  • Explore — the interactive node graph. This is the default view when you open a board: the artefact as an expandable tree on a canvas, with domain colour indicators showing mapping coverage at a glance.
  • Crosswalk — a table view that maps artefact clauses to controls and shows coverage state: Gap, Covered, or Implemented.
  • Controls — a filterable list of controls in the unified framework, with their associated mappings.
  • Flow — a Sankey diagram showing how expectations flow through domains and topics. Useful for portfolio-level analysis.

What this section covers

  • Boards — creating and managing boards, loading artefacts, and organising your workspace.
  • Explore — navigating the node graph, reading domain indicators, and filtering the canvas.
  • Crosswalk — the Gap / Covered / Implemented model, how to read the table, and what the coverage states mean.
  • Controls — working with the controls view.
  • Domains & Topics — the twelve governance domains, their colour system, and how topics and controls are organised within them.