What Does Governance Govern?
A thought inspired by the report: Foundations of Digital Sovereignty
More often than not, I read something that doesn’t change my mind so much as force me to ask a better question.
That happened recently while reading Foundations of Digital Sovereignty from the Canadian Shield Institute. It is an excellent paper, and I found myself agreeing with almost all of it. Its central argument—that Canada has invested heavily in infrastructure while underinvesting in governance—is both persuasive and overdue. Sovereignty is not created merely by owning compute, storing data within national borders, or building domestic cloud infrastructure. Institutions matter. Law matters. Procurement matters. Governance matters.
I don’t think the report overstates that case. If anything, it understates how important governance has become. And yet, by the time I reached the final page, I found myself returning to a question that has been quietly following me through the last few essays I have written.
What exactly does governance govern?
At first the question seems almost absurd. Governance governs AI. Governance governs digital identity. Governance governs data. Governance governs platforms. Governance governs institutions. The answer appears self-evident. But the more I thought about it, the less satisfied I became.
Those are specific domains; they are not architectural concepts.
Over the last several months I have unintentionally found myself writing a series of essays that all seem to be circling the same idea. Who Controls the Record? asked whether we have overlooked the simple question beneath electronic transferable records and digital assets. Recognizable, Not Readable argued that the significance of a record comes not from its readability but from its correspondence with something beyond itself. My most recent piece suggested that architecture often advances not by inventing new things, but by drawing clearer boundaries between existing ones.
Reading Foundations of Digital Sovereignty, I began to suspect these were all really the same essay. The report argues, quite rightly, that infrastructure without governance is insufficient. My own question is simply whether governance itself rests upon something even more fundamental. Before institutions can govern anything, there must first exist something whose state can be established, whose continuity can be maintained, and whose significance can ultimately be recognized. Governance rarely governs infrastructure directly. More often it governs the relationships represented by records, such as titles, permits, credentials, contracts, warehouse receipts, passports, licenses, and countless other documents that connect the internal world of information with the external world of people, property, and obligations.
At this point I should probably apologize. I appear to have become that person who eventually explains everything using football. I promise this wasn’t intentional. But once the analogy occurred to me, I couldn’t quite let it go.
A football match is governed by FIFA, yet FIFA does not decide whether the ball crossed the line. The referee does not award the World Cup. The players do not maintain the official score. Somehow the game works because each participant occupies a remarkably well-defined conceptual space.
It can almost be reduced to three simple questions.
Who has the ball?
Who counts the score?
Who wins the Cup?
The first is a question of correctness. The second is a question of control. The third is a question of effect. The elegance of football is not that these responsibilities have been centralized. It is that they have been separated.
The players establish the state of play.
The referee maintains the official record.
The governing body recognizes the consequence of that record.
None attempts to become the others.
The more I think about it, the more I suspect this is what good architecture looks like. Good architecture is not a collection of sophisticated components. Good architecture is a collection of clear boundaries.
Perhaps that is why so many digital systems feel unexpectedly complicated. Whenever the boundaries between concepts become blurred, governance begins compensating for the uncertainty. Assurance frameworks appear. Accreditation bodies emerge. Trust registries multiply. Policies become thicker. Governance expands because the architecture beneath it has left too much undefined.
This is not a criticism of governance. Quite the opposite. Institutions exist precisely because ambiguity exists.
But architecture has a different job.
Architecture removes ambiguity before governance ever encounters it.
That is why I find the distinction increasingly important. When we ask whether Canada needs stronger digital sovereignty, or whether AI requires better governance, or whether digital identity needs more trust, we are asking entirely legitimate questions. The report makes a compelling case that the answer is yes.
My own question simply comes one step earlier. Before governance can determine rights, responsibilities, liabilities, or national interests, what exactly is the object over which those decisions are being made?
For centuries we barely noticed the answer because paper quietly collapsed everything into a single artifact. A bill of lading, a bearer instrument, a warehouse receipt, or a passport combined correctness, control, and recognition into one physical object. Possession was visible. Control was implicit. Recognition followed naturally.
Digital systems have forced us to pull those concepts apart again.
Perhaps that is why governance suddenly appears so much harder.
Not because governance itself has failed, but because the architecture beneath it has changed.
One of the things I admire about Foundations of Digital Sovereignty is that it argues convincingly for stronger institutions without pretending that infrastructure alone is sufficient. I agree completely. My only observation is that governance may not be the foundation after all. Governance itself may depend upon an architecture that is only now beginning to emerge.
If that is true, then perhaps our task is not simply to build better governance. Perhaps it is to build clearer boundaries beneath governance.
I’ve started to suspect that this is how architecture always progresses. Not by making systems more elaborate, but by making concepts easier to separate. The best architectural boundaries eventually become invisible, much like the white lines on a football pitch. Nobody watches a World Cup Final to admire the painted lines, yet without them there is no game, no official score, and ultimately no champion.
Perhaps governance is much the same. It is indispensable. But even governance needs something to govern.
And perhaps that is the architectural question we are only now beginning to ask.