Glossary

A quick reference to the vocabulary used throughout Nomain and this documentation.

Analysis (run / execution)

The process that reads a System's code and documents and builds its model. One end-to-end run is an execution, made up of individual steps ("jobs"). See Running system analysis.

Area

The middle level of the business hierarchy. It is a named grouping of related business processes inside a domain. See Domains, areas & processes.

Business domain

The top level of the business hierarchy, a broad functional grouping such as Account Management. Shown as L1.x chips on a System card.

Business process

A single end-to-end workflow reconstructed from a process document and drawn as a step-by-step diagram (tasks, events, gateways, lanes).

Chat

Asking questions in plain language about a System and getting AI answers grounded in its code and documents. See Chat.

Deep Insight

An optional chat toggle that lets the agent take more time on complex questions. Answers get a Deep Insights badge.

Edge

A line between two nodes on the System map, showing a relationship or dependency.

Execution

A single analysis run. In Job History, each execution groups its steps under one expandable row.

Glossary (in an answer)

A single, de-duplicated list of terms the assistant returns when it searches your documents, so overlapping terminology appears once.

Memory

Durable facts the assistant keeps about you across chats, grouped into About you, Preferences, Projects, and References. See Agent memory.

Member / Admin

The two user roles. Members use Nomain; Admins additionally manage users, SSO, analysis and documents. See Administration.

Node

A single dot on the System map representing one part of the system, such as a program, file, job, copybook, screen map, field, and so on.

Path filter

An optional per-source rule (Include or Exclude, using gitignore-style patterns) that limits which files in a repository are analyzed. See Repositories & sources.

Progressive

A map setting that starts empty and reveals only the parts referenced in your chat answers, for focused exploration.

Reference (in an answer)

An inline, clickable link in an answer pointing to a specific part of the System, so you can trace a claim back to the code.

Repository

A saved connection to where your code lives, either Git or SFTP, defined once and reusable across Systems.

Source

A repository that has been attached to a specific System. A System's sources are the repositories it is built from.

SSO (single sign-on)

Signing in to Nomain with your organization's existing identity provider (Okta, Entra ID, Auth0, Keycloak, and others). See Single sign-on.

System

Nomain's structured model of one of your software systems, built from its code, jobs, copybooks and documents. Formerly called a Knowledge Graph. The central object in Nomain. See Systems.

System map

The interactive graph view of a System: nodes and edges you can filter, drill into and read. See Graph visualization.

Tenant / organization

The customer account that owns your users and Systems. All administration is scoped to your own tenant.

Unused (dead) code

Code that appears to be unused, surfaced by dead-code analysis and shown in the Unused Code statistic and node details.