Skip to main content
← Back to Articles

The Structure the Machines Do Not Know They Want

24 July 2026 · Ben Visser · 4 min read

At a glance - TL;DR

A management system is a web of relationships, but we store it as disconnected tables, which forces anything reasoning across it, a person or an AI, to rebuild the connections first: slow, costly, and quietly incomplete. Holding governance as connected knowledge instead turns a cross-cutting question into a fast, complete traversal, and the context compounds as the structure grows. The paradox is that this connected shape is the one AI reasons over best yet is least fluent in, because today's models were trained on relational tables; the builders who most need reliable AI already ground it in exactly this kind of ontology.

Key takeaways

  • A management system is a web of relationships, not a stack of registers, and tables are the shape that throws the relationships away.
  • When the connections are not stored, anything reasoning across the system has to reconstruct them first, which is slow, expensive, and quietly incomplete.
  • Held as connected knowledge, a cross-cutting question becomes a traversal that is faster, cheaper, and complete, and the context compounds as the structure grows.
  • The connected shape is the one AI reasons over best but is least fluent in, because today's models were trained overwhelmingly on relational tables.
  • Grounding AI in an ontology is how the most reliability-critical builders make it dependable, and a management system is an almost perfect candidate.

There is a question a good management system ought to answer in seconds. If this one risk changed tomorrow, which objectives would it touch, which measures would need rethinking, which controls suddenly matter more? It is not an exotic question. It is close to the whole point of having a management system. And it is exactly the sort of question you would expect an AI to be brilliant at: joining the dots across everything you hold, instantly.

So it is worth understanding why, today, it would not be. Point a capable model at a typical management system and the thread it needs, from that risk to the objectives to the controls, is not actually in the data. The relationships are implied, scattered across columns in separate registers. So the model does the only thing it can. It hauls whole tables into its context, tries to reconstruct the connections on the fly, makes several passes, burns a startling number of tokens, and keeps you waiting. Then it returns something confident, fluent, and quietly incomplete, because somewhere in the reconstruction it inferred a link that was not there and missed one that was.

That is not the model being weak. It is the model being handed the wrong shape. And I have been sitting with a suspicion that the shape is about to change, and not in a small way.

From Filing to Reasoning

So what is the right shape? A management system is not really a set of registers. It is a web of relationships. An objective exists to serve an aim. A measure exists to tell you something about an objective. A control exists because a risk justifies it. A change exists to move one of them along. The value lives in those connections, and a stack of tables is precisely the shape that throws them away, keeping the rows and discarding the lines between them. That is why anything reasoning across the whole thing, you or a model, has to rebuild the web before it can use it.

When the connections are kept instead, when the whole chain is held as connected knowledge, something shifts that is hard to overstate until you have felt it. That expensive, half-blind reconstruction simply does not need to happen. "What does this risk touch?" stops being a scavenger hunt and becomes a walk along relationships that were there all along. It is faster, it is cheaper, and, the part that matters most, it is complete. And the context compounds: every connection you add makes the next answer richer, because the structure itself is generative. A table sits there. A connected structure gets more useful the more of your world it holds.

That is the tangible shift, and it has almost nothing to do with databases. It is the difference between a management system you maintain and one you can reason with.

Trained on the Old Filing System

Here is where it gets strange, in a way I find genuinely funny.

This connected structure is not only better for humans. It is the shape an AI reasons over best. Give a model a defined web of things and relationships and it can traverse it, follow the implications, and answer the question you actually asked. Give it a pile of loosely related tables and it does roughly what we do: reads the one in front of it and guesses at the rest.

And yet today's models are, if anything, worse at the better shape. They were raised on the old filing system. The overwhelming majority of what they learned to write is SQL, the query language of relational tables, so that is what they are fluent in. The languages that walk a graph of relationships are comparatively rare in their training, so they handle them more clumsily. The substrate that would serve an AI best is the one it is least practised at. It would suit the machines beautifully. They just do not quite know it yet.

I think that gap closes, and closes quickly, because the pull is structural rather than fashionable. But it is a real paradox worth naming: for a while, the AI-native way to model your governance will feel like the road less travelled, precisely because the AI was trained on the road everyone else took.

How Serious AI Already Gets Built

If that sounds speculative, look at where reliability actually matters most.

The teams building AI that has to be dependable, where a confidently wrong answer is not an amusing screenshot but a genuine problem, have largely converged on the same move. They do not point a model at raw data and hope. They ground it in an ontology: a defined model of the entities in their world, the relationships between them, and the actions that can be taken on them. Palantir is the best-known example, and it has built much of its platform on precisely this idea. The model does not reason over tables. It reasons over a map of what things are and how they connect, and that grounding is what makes the output reliable enough to act on rather than merely interesting.

Read that back with compliance in mind and the fit is almost uncanny. A management system is already an ontology waiting to be written down: aims, objectives, measures, controls, risks, and the relationships that bind them into a whole. We have simply been storing it in a shape that hides the relationships rather than one that makes them the point. The move that makes serious AI dependable is the same move that makes a management system something you can reason with, and I do not think that is a coincidence. It is where we find ourselves being pulled at Askara Solutions, and we are still working out how far it goes.

The Filing Cabinet Was Never the Point

For thirty years the goal was a tidy record: everything filed, everything findable, ready for the auditor. That was the best a management system could be when the connections could only live in someone's head, or in a diagram nobody kept up to date.

It was never really what anyone wanted. What you want from a management system is to be able to think with it: to ask a hard question about your own organisation and get an answer that holds the whole picture at once. That was impossible to build and expensive to fake, so we settled for the filing cabinet and called it governance.

We may not have to settle much longer. The interesting question is no longer how to store what you did. It is what you will finally be able to ask.