Interoperability is an operating model problem before it becomes an API problem

Integration programmes often begin with technology: APIs, gateways, message brokers, data platforms and identity services. These are necessary, but they do not create interoperability by themselves.

Interoperability depends on agreement about meaning, authority, accountability and process. Who owns a data element? Which institution is authoritative? What happens when two systems disagree? Who is allowed to consume the data? What operating rule governs a cross-agency workflow?

These questions sit in the operating model. When they remain unresolved, integration technology merely exposes organisational ambiguity at machine speed.

Architecture should therefore connect technical interfaces to governance, semantics, decision rights and service ownership. APIs matter, but they must sit inside a larger model of institutional trust and responsibility.

The most durable digital-government platforms solve these operating questions explicitly instead of assuming technology will solve them implicitly.

Good technology decisions become stronger when architecture connects them to governance, data, people and measurable outcomes.