When I describe our work, I often say that we help governed ecosystems become interoperable. The phrase usually earns a polite nod, and sometimes a puzzled one. People in ministries and companies tend to picture an ecosystem as something that happens elsewhere, in data spaces or on the web, until they start listing the organisations their systems exchange data with every day.
That list is usually longer than expected, which shows how invisible these circles are to the people inside them. Most organisations live in several governed ecosystems at once, and the way they manage meaning changes once they can see them.
What makes a circle a governed ecosystem
A governed ecosystem has four features, and none of them depends on sector or size. The first two are what make it governed. The other two are what make convergence inside it something you can see and steer.
The first is rules that bind the parties. Something sets the terms between them: a regulation, a contract, a consortium agreement, the governance framework of a data space, the data governance policy of an enterprise. Those rules say who belongs, what each member commits to and how shared decisions are taken, and they usually name a body that takes them, such as a working group, a steering committee or a data governance board.
The second is parties with roles in the shared models. You can name who is in, and each party holds a recognisable role towards the models the circle depends on: one authors a specification, another owns and publishes it, others maintain it, contribute to it or implement it. Those roles make every modelling decision attributable. When a party builds on a shared model, maps its own terms to it or goes its own way, that choice is a governance decision with a name attached.
The third is a shared purpose with a boundary. The parties exchange data for particular reasons, such as paying a pension across a border, tracing a batch through a supply chain or closing the books across business units, and you can say which concepts that work depends on and which it does not. Drawing that boundary is itself an act of governance, and it rarely comes out right on the first attempt.
The fourth is a real cost when models diverge. If one party models a concept differently, someone else in the circle pays for it, in a mapping, a failed exchange or a manual reconciliation. Because the parties and their roles are known, that cost can be traced back to a decision.
Where all four are present, you are in a governed ecosystem, whether or not anyone has used the word.
Where governance meets convergence
The rules and the behaviour of the parties are two different sources of direction, and a healthy ecosystem keeps both in view. Governance expresses what the circle has decided: a required standard, a preferred registry, a regulatory obligation, a strategic priority. Convergence is what the parties actually do within those rules, visible in which models they build on, map to and run in production.
Most of the time the two agree, and the rules simply confirm where the members were already heading. When the evidence leaves two options level, the rules are the right way to choose between them, and the choice is explicit. When the rules point one way and the members’ systems point another, the ecosystem has learned something important, and that is precisely the conversation its governing body should be having. A circle that watches only its rules will miss the drift; a circle that watches only behaviour will lose the reasons behind its choices.
Four places you will find one
Public administrations that take part in cross-border services form one: each administration is the authoritative publisher for a class of transaction, and the purpose is set by the service they deliver together.
An enterprise forms one internally. Finance, logistics, sales and research each maintain authoritative records for their domain, and shared data governance sets the rules between them. Many companies discover this only when two functions report different numbers for the same customer.
An industrial or supply-chain consortium forms one when it defines shared requirements for exchanging data between its members.
A data space forms one by design. Its governance framework assigns roles such as data holder, data recipient and intermediary, and the EU Data Act, which has applied since September 2025, now gives roles like these legal weight in many sectors.
The open web is the instructive exception. Anyone can publish there, membership has no boundary, nobody holds a defined role and no body sets rules between publishers. Methods that suit the open web, such as waiting for the most popular vocabulary to win, carry over poorly into circles where the parties and the costs are known.
Why naming it changes your work
Once you see the ecosystem, interoperability becomes a relationship you can manage, with partners you can name. You can ask which of your peers you most need to understand, on which exchanges, and you can look at what they have already modelled before you build your own version. You can see when a decision in your team will create work in someone else’s, and decide knowingly.
It also changes who you talk to. In a governed ecosystem, the most valuable modelling conversation is often with a peer organisation, before either side commits, rather than inside your own team after the fact.
Are you in one? A short test
- Can you name the organisations, or units, your systems must exchange meaning with? Write the list.
- Does each of them hold a role you could describe in one line?
- Can you name the exchanges that matter, and the concepts they depend on?
- When two of you model a concept differently, who pays, and could you trace it?
- Is there a body, a contract, a regulation or a working group that sets rules between you?
If you answered yes to most of these, you are in a governed ecosystem, and probably in more than one.
Seeing the circle
Naming the ecosystem is a small act with large consequences. It turns a vague aim into a set of relationships, each with a purpose and a cost, and it gives every modelling decision a referent. Helping organisations see their circles, and the convergence happening inside them, is where our work at METALEVELS begins.
If you would like to map the ecosystems your organisation already lives in, start a conversation with us.