The functional axis

Twelve archetypes describe any organisation.

A Function Dimension isn't an industry or a domain label. It's an ontological archetype — a small, universal set of categories that, together, classify every meaningful element of any organisation without overlap and without gaps.

The shift

What is a Function Dimension?

Most metadata models classify assets by domain — data, governance, business, technology. That works for a catalog, but breaks the moment you need one classification to cover a factory-floor asset, an AI model, a legal regulation and a sales process with equal precision. Nodwise classifies instead by what something fundamentally is and does in any organisation. That is the Function Dimension — and when a node is assigned one, it inherits a semantic contract: the universal relationships and behaviours every instance of that archetype shares.

from

"what sector does this belong to?"

to

"what does this fundamentally do?"

A Table and a finished good are different sectors — but both are Resources, and both behave like Resources in the model.

Not instead of — across

Domain didn't go away. It became the other axis.

Every node type in Nodwise is filed twice, and the two filings answer different questions.

Where it lives

One of ten Organization Dimensions, which owns its governance and its lifecycle.

Strategy & Impact · Human Resource · Business · Governance & Compliance · Data & Knowledge · Application · Technology · Physical Assets · External Entities · Artificial Intelligence

What it fundamentally does

One of twelve Function Dimensions, which gives it its semantic contract.

The twelve are named below. Neither is derivable from the other, and that is the point.

node type

organisation

function

function category

Technical Skill

Business · Actor Skill

Skill & Features

Skill

Core Capability

Business · Business Capability

Skill & Features

Feature

Read one way they are neighbours. Read the other they separate cleanly — a Technical Skill is something an actor holds; a Core Capability is something an offering has. One axis says who governs them. The other says how they behave. Two axes, because one of them was never enough.

The boundaries

Two of the twelve are poles.

Every other element exists in the space between what cannot be done and what the organisation is pursuing — and is accountable to both.

Motivation

"For what end?"

The articulated purpose — forward-looking, teleological. Every element should trace back to at least one, or it is organisational debt.

GoalPrinciple

Constraint

"What cannot be done?"

A standing condition that permanently limits or prohibits what is possible — continuously in force until revoked.

Regulatory RestrictionTechnical LimitationFinancial LimitationContractual Restriction

constraint  ———  the organisation operates here  ———  motivation

The ten between the poles

What everything else fundamentally is — and its categories.

Each dimension is the archetype; beside it sit the categories that refine it. Twelve dimensions resolve into twenty-eight categories (the two poles' categories are shown above).

Actor

01

Does it act?

Someone or something with agency — it initiates and executes action.

Not a passive item used or owned — that's a Resource; not the place it operates in — that's an Environment.

PeopleEngineOrganization

Task

02

Is it done?

An activity done to achieve a purpose — it transforms inputs into outputs.

Not the result of work — that's an Event or Resource; not the offering delivered — that's a Service.

Simple TaskProcess

Resource

03

Is it used or consumed?

Something of value that is used, consumed, or transformed — passive, acted upon.

If it acts on its own → Actor; if it's an intangible action offered → Service.

Physical ResourceVirtual Resource

Service

04

Is it provided or obtained?

An intangible action with a direction — provided to a consumer, or obtained from a provider.

Not the process that delivers it → Task; not the tangible item handed over → Resource.

Physical ServiceVirtual Service

Environment

05

Does it host others so they can operate?

A context that hosts actors and resources — it enables by providing the space they operate in.

Not the resources inside it → Resource; not the actors within → Actor; not a set that merely gathers its members → Group — an Environment is infrastructure: it supplies the place, the power or the compute that lets others work. A Group supplies nothing; it only names the set.

Physical EnvironmentVirtual Environment

Event

06

Does it occur / trigger?

A discrete occurrence in time — a trigger or signal that marks a transition.

An ongoing activity → Task; a condition that stays in force → Constraint.

Internal EventExternal Event

Information

07

Does it describe facts?

Structured, communicable representations of facts — exists independently of any actor.

Once internalized into understanding that shapes action → Knowledge.

ConceptDataReference

Knowledge

08

Does it enable understanding?

Internalized understanding — information processed, validated and applied. It enables, not just describes.

Raw, uninterpreted facts → Information; the ability to apply it → Skill & Features.

Explicit KnowledgeTacit Knowledge

Skill & Features

09

Does it enable action?

An ability that enables tasks to be performed — held by an actor, distinct from the actor itself.

What an actor knows → Knowledge; the whole offering → Service.

SkillFeature

Group

10

Does it organise others?

A universal organiser — its one relation is groups. It collects and structures any element of any dimension; it doesn't act, host, or constrain by itself.

An internal unit that only collects its members is still a Group — it's an Organization (Actor) only if it acts as one entity; an Environment if it supplies what they need to operate — physically or virtually.

Conceptual GroupConcrete Group

The completeness test

Eight questions. No gaps.

Together the twelve answer every fundamental question about any organisational element. The most important one — "for what end?" — earns its own dimension.

Question

Answered by

Example

Who?

Actor

Person, ERP System, RPA Bot

What?

Resource · Information · Knowledge

Product, Dataset, Policy

How?

Task · Skill & Features · Service

Process, Capability, API

Where?

Environment

Factory floor, Cloud Environment

When?

Event

Milestone achieved, Endpoint trigger

Why?

Information / Concept

Regulation, Market trend, Risk

For what end?

Motivation

Goal, Mission, ESG Mandate

What limits us?

Constraint

Compliance rule, Rate limit, Budget cap

"Why?" is causal and backward-looking — Information suffices. "For what end?" is purposive and forward-looking — it needs a dedicated Motivation so the model can answer the deepest governance question: can every element be traced to an explicit purpose?

The grammar

The twelve connect through one closed grammar.

Archetypes don't just sit in a list — they relate through a fixed vocabulary of typed relations. Each relation is a verb with a real-world reading, so any organisational question becomes a single model traversal.

relation types, grouped by subject

Actor

generates → Knowledgestores → Knowledgeconsumes → Informationdefines → Taskexecutes → Taskoversees → Taskholds → Skill & Featuresis hosted on → Environmentpursues → Motivation

Task

requires → Skill & Featuresrequires → Resourcerequires → Environmentproduces → Resourceproduces → Eventproduces → Informationprovides → Servicetriggers → Actorfulfills → Motivation

Service

produces → Eventrequires → Resourceprovides → Informationdelivers → Motivation

Resource

is hosted on → Environmentprovides → Information

Event

interrupts → Tasktriggers → Actorproduces → Informationsignals → Motivation

Information

improves → Knowledgeclarifies → Knowledgeclarifies → Task

Knowledge

improves → Skill & Featuresinterprets → Constraint

Skill & Features

enhances → Task

Motivation

drives → Taskdrives → Actorjustifies → Resourceshapes → Knowledgeshapes → Information

Constraint

bounds → Motivationapplies to → Resourceconstrains → Actor

Try it on your own material

Classify your first dimension this week.

Bring a slice of your organisation — systems, processes, people — and watch each element land on its archetype, with the grammar already connecting them.

without us

Open the demo

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

Open the demo

with us

Become a Design Partner

Your own environment, your data in the model, and a solutions architect modelling your first dimension alongside your team.

Become a Design Partner