The facts

Years of curated assets.
That work is not a sunk cost.

The domains, the glossary, the classifications, the owners you argued about for two years — they are the hardest part of a model to produce, and you already produced them. Nodwise reads them in and gives them somewhere further to go. Keeping your existing catalog running as a data source is your option, not a requirement.

What comes in

The facts do not start blank. They start with what you already have.

Three sources cover most of an organisation's typed reality, and none of them has to be authored by hand:

01

Your data catalog

Domains, assets, glossary terms, classifications and the responsibilities already assigned to them — arriving as typed nodes with their owners intact.

02

Your HR system

People, departments, positions and reporting lines. This is what makes a responsibility resolvable to a person who is actually still employed.

03

Your identity provider

Groups, roles and entitlements — how the model tells an assigned owner from an owner who can actually reach the thing they own.

All three arrive through Remote Services — and where it runs is your call.

source behind the firewall

Runs inside your network and dials out. No inbound port, no firewall exception, no credentials handed over — Nodwise never needs a way in.

your network→ out →Nodwise

source reachable over the internet

Skip the deployment and run it in the Nodwise cloud instead. Same component, same connectors.

your SaaS source← to ←Nodwise cloud

Every connector works either way. The only question is which side of your perimeter the source sits on.

And because those nodes are read rather than authored, they cannot drift from their source. When something disappears upstream the node is demoted to Missing from Source — not left standing as a fact that quietly stopped being true.

Where your catalog ends

A catalog governs the data. An organisation is more than its data.

Strategy & Impact

Human Resource

Business

Governance & Compliance

Data & Knowledge

Application

Technology

Physical Assets

External Entities

Artificial Intelligence

This is not a gap your catalog failed to close. It is the edge of what it was built to cover, and it was the right edge to draw. Data & Knowledge is one of ten organisation dimensions, and it is the one your catalog does well.

The other nine are where the questions live that nobody can currently answer: the machine on the factory floor, the legal obligation, the sales process, the model in production, the person who is the only one who knows how any of it fits together. They are not badly governed. They are not in a model at all.

Nodwise takes what your catalog knows as the starting point and extends the same typed grammar across the other nine — so a question can cross from an asset to the process that consumes it, to the person who owns that process, to the obligation it satisfies.

What becomes answerable

The same facts, in a model that can be traversed.

Nothing new was authored. The questions below are answerable the day after the import, because each one is a path across nodes that were already there — they were simply in three systems that could not see each other.

Which critical task can only one person perform?

HR gives the people, the catalog gives the assets, the responsibilities connect them. The answer is a count, not an investigation.

Which certified assets are owned by someone who has left?

The question the catalog cannot ask, because employment status is not one of its fields.

If this system goes down, what stops — and who needs to know?

Crosses from technology to process to the people accountable for it. Three dimensions, one traversal.

Who approved this, and did they hold the mandate at the time?

Not who is listed now. Who held it then — which is a different question, and the only one an auditor asks.

None of these is a report you commission. They are queries against a model that already holds the answer.

The third term

Facts alone do not act.

A model built from three systems is accurate on the day it is built. What keeps it true — and what turns it from something you query into something that reaches you — is the third term.

read next

The agent — what keeps it true

The part that watches the model, notices what changed, and reaches the person who needs to act.

The agent →

or see it running

Open the demo

A fully modelled organisation, one click with your work account. No form, no call.

Open the demo