Click here to download the full series in PDF format.
When, in the second part of this series, we reached the point of dismantling the state’s digital structure, and then, in the third part, translated that dismantling into an operational pulse, nothing remained in the path of digital transformation that could be attributed to a lack of tools, weak platforms, or insufficient connectivity. It had become clear that the state—from the standpoint of technical capability—now possesses what qualifies it to build. The issue is no longer the question of “How do the systems work?” but a more precise and more dangerous question: how is the state governed when it operates digitally?
Here, digital transformation reaches its most sensitive stage. Technology, once mature but left ungoverned, does not produce a smart state; it produces a state faster at reproducing its own imbalances. Automation without strict governance does not end disorder; it accelerates it. It does not unify truth; it multiplies its versions. It does not reduce the burden on the citizen; it turns that burden into a silent dispute between systems that have no reference point and no authority to regulate them.
Accordingly, this fourth part does not address “Sahel” as an application, nor digital transformation as a technology project, but the state itself when it speaks in the language of the machine: who owns the truth? Who sees performance? Who governs the rule? And how do entities become equal before it? These questions are not administrative or technical; they are sovereign in origin and governance-related in their consequences.
Fragmented Data Sovereignty: When “Truths” Multiply Within One State
The first governance challenge, and the most consequential for automation and decision-making, is the fragmentation of data sovereignty within the machinery of the state. The issue—despite its precision—does not lie in the scarcity of data, nor in weak access to it, but in the absence of a decisive answer to a question that appears simple in wording yet is extremely dangerous in its implications: who owns the truth?
In the current landscape, each government entity treats its data as operational assets belonging to its own system, not as a component of “one national truth” managed at the level of the state. Thus, the sources of a single data point multiply, its update mechanisms differ, and entities dispute the “latest version” rather than the “sovereign version.” As a result, the state can no longer build an automated decision, a proactive service, or even a unified service pathway; because automation, in its essence, does not operate on assumptions or probabilities, but on truths that do not accept multiplicity and cannot tolerate contradiction.
In previous parts, we referred to the concept of the “data sovereignty authority,” and explained that the transition from the “image of the document” to the “data of the document” cannot be completed unless ownership of the data is settled sovereignly. Yet this idea, despite its engineering importance, remains incomplete unless translated into a binding governance policy, not an organizational interpretation or a technical directive open to interpretation.
The solution here is not to unify databases, nor to create massive centralized repositories that reproduce the same problem in a more complex form. Rather, it is to establish a national data sovereignty policy that defines—explicitly and without ambiguity—the entity that owns the original truth for each data point, the entity authorized to amend it, the entities permitted to consume it, the limits and purpose of that consumption, and the requirements of traceability and accountability when deviation occurs. Such a policy must not be left to the discretion of ministries, nor separated from the “general protocol for smart government”; it must be integrated into it as a governing clause from which no linkage or automation is exempt.
This integration requires the creation of a national registry for the sovereignty of data assets—not as a data warehouse, but as a sovereign map of truth. For each data point, it should define its meaning, format, owner, sensitivity level, the entities authorized to access it, the legitimate purpose for invoking it, and its validity period. Without this registry, the state will continue to address data conflicts after they occur, rather than preventing them before they arise.
At the operational level, this conception turns into a radically different mode of work: instead of asking the citizen for a document, the “status” is invoked from its sovereign source; and instead of transferring data between systems, data is summoned when needed, with precise authorization and an auditable record. Only then do data move from being “stored files” to becoming “national functions,” and each data point—however simple it may appear—becomes part of a sovereign fabric through which the affairs of the state are managed, not merely a field to be filled in an electronic form.
The Absence of a National Performance Mirror: When the State Cannot See Itself
No less dangerous than fragmented data sovereignty is the absence of what may be called the “national performance mirror.” A state that cannot see its performance moment by moment cannot govern it, reform it, or hold it accountable. As long as performance measurement in the digital system is based on scattered reports, local indicators, or delayed readings, digital transformation remains an administrative improvement project, not an institutional leadership project.
The technical structure presented in the third part made it possible to track service journeys, broadcast events, connect statuses, and record transitions. Yet this capability—if not invested in through governance—remains disabled. The issue is not the collection of data, but who sees it, when, under what authority, and for what purpose.
The absence of a unified national dashboard showing the actual time required to complete services, points of disruption, and responsibilities for delay makes accountability impossible. How can an entity be held accountable for performance that is not measured according to one national standard? And how can a reform decision be made without real-time visibility into what is happening deep within the system, not merely on its surface?
The solution here is not to add more reports or intensify meetings, but to create a sovereign national performance mirror, automatically fed by the events of the “protocol,” and showing the state as it actually operates, not as it is administratively narrated. This mirror should not belong to an operating entity, nor be managed with a media-display mentality. It should be linked directly to the highest decision-making center and used as an instrument of governance and accountability, not as an instrument of decoration or justification.
This mirror must be founded on mandatory standards of observability, so that no national service is approved for publication or expansion unless it proves its traceability from beginning to end, through a unified national transaction identifier, consistent error semantics, and time indicators that are not open to interpretation. When the continuity, automation, or upgrading of any digital service becomes tied to published performance indicators, improvement becomes an institutional necessity rather than an administrative option. The smart state is not managed by impressions, but by visibility.
Confusion Over the Center of Decision: Who Governs the “Digital Constitution”?
If data sovereignty and the performance mirror represent “what is governed,” the more dangerous question remains: who governs? Who has the authority to define the digital rule, impose compliance with it, manage its versions, and resolve conflicts when they arise?
In the current reality, the center of decision is confused among operating entities, technical entities, and oversight entities, without a clear sovereign owner of the “digital constitution.” Rules are interpreted differently, exceptions are managed through discretion, and technology is sometimes placed above governance rather than the other way around. This confusion—though it may appear organizational—empties the “general protocol for smart government” of its sovereign substance, turning it from a binding rule into a moral agreement that can be bypassed. In the second part, we explained that the “protocol” is not a programming guide, but a sovereign framework, and that it cannot stand unless it has an authority that governs it, not merely an authority that manages it technically. The difference is vast between those who write the lines of code and those who possess the right to impose the rule by which those lines are written.
From here, the governance solution is not to strengthen operating teams or expand the powers of platforms, but to establish an independent sovereign digital governance authority. This authority should not perform a service role, should not participate in implementing services, and should not compete with entities. Its exclusive tasks should be to approve the “protocol,” manage its versions, impose compliance, resolve conflicts, and suspend or revoke any connection that does not comply with the rules. Its reporting line must be directly to the highest decision-making center in the state, not to any executive body, so that governance does not become a party to the dispute instead of the judge over it. The digital state is not managed by coordination committees or governed by temporary balances, but by a standards authority that manages versions, imposes compatibility, prevents sudden breakage, and protects national consistency over time.
Divergent Operating Cultures: When Entities Are Not Equal Before the Rule
The fourth governance challenge remains one that cannot be solved by technology or legislation alone: the divergence of operating culture among entities. No matter how mature the “protocol” becomes, and no matter how complete the tools are, the state does not operate according to its highest logic, but according to the weakest link in its commitment. Differences in readiness, divergent understandings of compliance, and implicit resistance to transformation all produce exceptions that detonate the system from within.
An uncontrolled exception is more dangerous to automation than an explicit failure, because it preserves the form while emptying the substance. Therefore, operating culture is not a matter of training or awareness, but a matter of compliance governance. In other words, compliance with the “protocol” and with performance indicators must not be an administrative option, nor treated with advice alone; it must be linked directly to leadership evaluation, institutional accreditation, and funding priorities.
Just as an entity should not be financially licensed without accounting compliance, it should not be digitally licensed without compliance with digital governance. This requires turning compliance from a binary state—compliant or non-compliant—into declared maturity levels that show the extent of each entity’s adherence to standards, reveal exceptions, and prevent them from turning into parallel rules. When entities become equal before the rule, integration is no longer a burden and automation is no longer a risk; discipline becomes a condition for remaining within the system, not an additional virtue.
Governance: Where Automation Is Decided
This dimension makes clear that governance challenges are not a later detail of digital transformation, but its beating heart. There is no digital sovereignty without data sovereignty, no accountability without a performance mirror, no automation without a center of decision, and no integration without a culture of compliance. The structure has been built, the technology has been organized, and only one thing remains: for the state to be governed as it operates, not as it used to operate. The smart state is not measured by the speed of its interface, but by the strictness of its rules; not by the smoothness of its experience, but by the clarity of its sovereignty; and not by the advancement of its tools, but by its ability to see itself, hold itself accountable, and impose discipline upon itself.
In the next part of this series, we will move from the question “How is the state governed digitally?” to an equally dangerous complementary question: how is this state used? And how does this structure—if sound—reflect on the experience of the citizen and resident, not as users of an application, but as partners in a state whose logic is changing?
O Allah, ordain for this nation a matter of right guidance.