dynaxity.world — The Operating Ontology

I

The Work.

IAbout

Twenty years on complexity, on leadership development, and on how to build organisations that can actually keep up with both.

dynaxity.world is where Patrick Hamilton's twenty years of work come together — the research, the writing, and the platforms built from it. It began in 2006 with a book published by Springer, called Dynaxity, which gave a name to what most organisations were already living through: situations changing faster than the rules built to handle them. The work continued through two decades drawing on brain science, leadership development, and software architecture. Today it is something organisations can actually use.

Four things grow from this work. drhamilton is the architect's own practice — the consulting and design work itself. sw-arc is the technical foundation underneath everything else, the part that makes the platforms possible. The Academy is the formation platform already in real-world use, running inside its first institution. u-rise is the public face of the writing and ideas. They aren't separate companies. They're four windows onto the same body of work.

What makes this different from most software work isn't any single product. It's a belief — that the most durable thing you can build isn't a tool. It's something closer to a body. Something that learns its environment by living in it, rather than being told all the rules in advance.

Most tools manage the thing that is changing. A few manage the person managing the thing. Almost none reach the slowest layer of all — how the people themselves are shaped by working inside something that never holds still. That third layer is where this work lives.

And it keeps a different kind of record. Every connection it stores is something that happened — between specific people, at a specific time. Not a fixed fact to be overwritten, but an event that stays. The platform doesn't describe the world; it keeps the running record of what the world has done.

BeliefThe most durable thing to build isn't a tool — it's a body.

DepthThe slowest layer — how people are formed — is the one almost no software touches.

II

A Living Model.

IIPast to present

The model was never finished in 2006. It earns a new dimension only when reality refuses to fit the old ones — which means it is still growing.

It began with two questions. How fast is this changing? And how tangled is it? Dynamics and complexity — the two axes the 2006 book put a name to.

Then reality pushed back, and the model grew. A way to read what kind of situation you are in — routine, complicated, genuinely complex, or chaotic. A sense of how long a thing is meant to last. And most recently, a measure of how generative something is: a receipt is inert and lists what is already known; a real conversation creates something new but leans on everything known before it. That last dimension quietly folds in time itself — what is remembered, what is kept, what is allowed to fade.

Each dimension was added the same way: not invented at a desk, but forced by a case the existing model could not hold. A framework that grows like this is the opposite of one frozen in a book. It is an instrument that is still being tuned by use.

III

The Operating Ontology.

IIIThe foundation

Five basic kinds of things. Connections that remember what happened. A simple tag on every connection saying what kind of situation it belongs to. A foundation that knows what it's looking at before it tries to act.

Most software has a data model — a list of the things it knows about, and the ways those things connect. That is necessary. It is also not enough.

Our operating ontology adds two ideas that change what the platform can do. First, every connection between things carries a tag answering one question — what kind of situation is this? Routine and predictable? Complicated but knowable? Complex and shifting? Or chaotic? With that tag in place, the platform can tell the difference between a standard administrative step and a delicate coaching moment, and respond accordingly. Second, every connection is a record of something that happened — between specific people, at a specific time. Not a static fact. The platform doesn't describe the world; it keeps the ongoing record of what the world has done.

Five basic categories are enough to cover everything we need to track: people, things, projects, products, documents. Anything you would want the platform to know about fits somewhere in these five. The interesting part isn't the categories — it's the connections between them.

SimpleComplicatedComplexChaotic

Human

people in the system

Material

things and resources

Project

ongoing efforts

Product

platforms and tools

Documentation

agreements and records

I

Five categories are enough to describe anything people do together.

II

Every connection is a record of something that happened, not a permanent statement.

III

Every connection says what kind of situation it belongs to and how fast it changes.

IV

One place holds the truth. Every part of the platform reads from there. No copies.

V

When something changes, we add a new entry. We don't erase the old one. History stays.

VI

Different organisations using the platform are kept apart by cryptography, not by trust.

VII

What you can see depends on what you are ready for, not on permission alone.

The Dynaxity matrix. Two questions, asked of every connection in the platform. What kind of situation is this — clear, complicated, complex, or chaotic? And how fast does it change — not at all, slowly, normally, or unpredictably? Sixteen possible cells. Every connection lives in exactly one. The cell decides how the platform reads the connection, how often it checks on it, and what kind of intelligence is allowed to act on it.

IV

The Learning Ontology.

IVHow it learns

Building something that organises complexity is the first half of the job. Building something that learns from being used is the second.

A platform that only describes the world is doing half the work. The matrix above shows how complexity gets named. What it doesn't yet show is how the platform learns from being used.

The idea is older than software. Watch a beginner learn anything — driving, playing piano, even typing. Every step is slow, conscious, effortful. After enough practice, the same skill becomes automatic — the body has learned to do it without thinking. We call it muscle memory. A part of the brain called the cerebellum takes over from the conscious part, doing what the conscious part no longer needs to.

Plastic deliberation

Conscious effort

Shadow candidate

Tested quietly

Frozen procedure

Automatic

Unfreeze on drift

Back to conscious

A platform that turns the wrong things into habits is rigid. One that turns the right things into habits is wise.— architectural principle

Our platform learns the same way. Every process begins as scaffolding — the smallest version we can build that actually runs. The platform watches: what gets used, what gets skipped, what people keep asking for, where they slow down. Buttons appear when they are needed. Questions appear when they are being asked. Steps form around the way the work actually flows. After enough repetition, a process settles into a shape that fits — closer to how the work really happens than anything we could have planned in advance.

Biology stops there. That is its limit. Once a habit is locked in, it is hard to undo — golfers with bad form know this, and so do pianists with locked technique. We built the part biology forgot: the ability to notice when a habit has stopped working, and the discipline to unlearn it.

The hardest skill is knowing which habits to keep and which to never form. Simple, repeating situations should be turned into habits, and the platform does so gratefully. Complex, shifting situations should never become routine, and the platform protects them from becoming routine. The tag on every connection — what kind of situation it belongs to — is how the platform decides which way to learn.

This is the difference between a platform that runs and a platform that learns. The first puts complexity in order. The second is shaped by it.

i

Start small enough to actually run.

A fully designed process is almost always wrong. The smallest version that actually runs is almost always right enough to start.

ii

Notice, suggest, test.

The platform spots where things get stuck, suggests a fix, tries it on a small audience, keeps it if it helps, drops it if not.

iii

Lock in what proves itself.

Steps that keep working in similar situations earn their place in the platform's muscle memory.

iv

Unlearn what stops working.

When a habit starts failing, or the situation around it changes, the platform unlocks it and starts learning again. Bad habits do not survive here.

v

Let the situation decide.

The kind of situation determines what is allowed to become a habit. Simple ones get locked in fast. Complex ones stay deliberately fluid. The discipline is knowing which is which.

vi

AI is a tool, not the foundation.

The intelligence you can buy is becoming a commodity. The platform around it — the part that understands its own situation — is what holds value over time.

V

Convergence.

VTwo lines, one landfall

Two long lines of inquiry, followed separately for decades, turn out to have been pointing at the same place. Here is where they meet.

The complexity line

1990sEarly complexityreading how systems behave when nothing holds still

2006The booka first attempt to bring it into how organisations work

2026The platformthe same idea, now something you can use

now

The cognition line

1990sNeural networksearly, before it was obvious

the winterNot droppedfollowed deeper, into how brains actually learn

2026Returnsthe field arrives where the work had been waiting

The two lines share a way of working. The old ocean navigators found islands they could not yet see — not by instruments, but by reading the water: a swell bent by unseen land, a change in the birds, the colour of the sea. They read the signs of what was coming before it arrived. The platform is built to do the same — to read the living situation it is in, and sense where it is heading, rather than only follow a fixed plan.

That is also how these two lines were followed. Both were read early, from faint signs, and held through the years when neither was in fashion — sailed toward a landfall that was not yet in view. Whether that reading was always deliberate or only clear in hindsight matters less than that the course was kept.

None of this is free. Following two long bets meant years in open water with little to show. Building something that reads its whole situation is slower and stranger than chasing whatever is loud at the moment. And letting people own what is theirs means giving up the control most platforms keep. These are the costs. The work is offered with them visible — a chart to use or to set aside.

VI

Why This Is Different.

VIFour consequences

None of these is a feature. Each one falls out of how the platform is built.

i

It forms people, not just processes.

Most platforms organise work. This one reaches the slower layer underneath — how the people doing the work grow while doing it. That layer is the hard one, and almost no one builds for it.

ii

The model grows.

Twenty years of dimensions added one reluctant case at a time. It is still being tuned. A frozen framework ages; a living one keeps fitting.

iii

History is the substance.

Nothing is overwritten. Every fact is a dated event between real people. The record is trustworthy because it is built that way, not audited into shape afterwards.

iv

The person owns the data.

Institutions hold only scoped access that opens and closes. The data never moves and never belongs to them. Leave, and you keep what is yours.

VII

The Whole.

VIIEverything, in one body

It began with one book and one idea. Here is everything that grew from it — two ways in, the tools people use, and the shared foundation underneath them all. Tap anything to see what it is.

The two ways in

The packages

What they serve

The tool family

Built underneath

The tool familyThese are smaller tools. Each works on its own, and each also lives inside the bigger products — the same capability, wherever you need it.

Built underneathSix capabilities, built once, underneath everything. No product reinvents them — they are shared. That is why a capability you hold shows up wherever it is useful.

VIII

Two Ways In.

VIIIWhere it becomes real

The same foundation reaches two kinds of people. Pick the door that fits.

For organisations forming people

The Academy.

For institutions that form leaders and want a platform that forms alongside them. The first one is already running on it. Bring formation to your organisation, with your own people, your own cohorts, your own pace.

For individuals forming themselves

The App.

For the person who wants the tools for themselves — to think, to capture, to grow — without an institution in between. Ready-made, not a kit to assemble. And whatever you put in stays yours, even if every institution around you changes.

No account needed to look. We only ask for an address when you want us to follow up.