Control over functionality. A solution that offers higher performance but less control must be rejected. Functionality is not an argument for accepting dependency.
DIGGS — Digital Independent Governance & Grounded Sovereignty
The DIGGS Doctrine: The Need for an Independent European Infrastructure
Europe does not have a technology problem. It has an architectural problem.
Europe does not have a technology problem. It has an architectural problem.
The digital infrastructure we rely on is built by actors whose business models presuppose lock-in, and whose jurisdiction lies outside our control. That critical systems can be restricted or, in the worst case, shut down from another continent follows from how the architecture is designed. The result is a form of silent asymmetry: the systems are operational, but only partly controllable.
The dependency works through concrete mechanisms. Jurisdiction: the US CLOUD Act can compel US providers to hand over data they control, wherever that data is stored. Exit cost: proprietary data formats and integrations that have to be rebuilt make moving expensive. Unilateral control: the provider can change prices and terms, or shut down APIs, without the customer having any say.
The mechanisms are not hypothetical. After the United States imposed sanctions on the Chief Prosecutor of the International Criminal Court (ICC) in 2025, he lost access to his Microsoft email (Lawfare). Microsoft disputes that the court’s services were stopped (heise). The ICC has since decided to switch from Microsoft Office to openDesk, an open-source suite (The Register). The mechanism is the same either way: sanctions against one person, the provider complies, the user loses access.
The flaw in today's approach
European attempts to solve this have followed two tracks: copying existing platforms under new names, or trying to regulate their way out of the problem. Both fail because they do not change the mechanisms that create dependency. Copies reproduce lock-in in a new form. Regulation presupposes control over infrastructure one does not control. Thus, the dependency remains intact.
Open alternatives are often technically competitive, but lose on distribution and adoption. My assessment is that the problem is rarely the technology. Distribution, adoption and usability are treated as afterthoughts, something added once the architecture has been decided.
The Principle
A sustainable solution must be a set of architectural principles that make dependency unnecessary in the first place. A product alone cannot solve this. This means open standards right down to the root level, the freedom to move data and services without structural lock-in costs, and commercial usability built into the architecture from day one.
We cannot be religious open-source fanatics. But we must be pragmatic patriots. Digital sovereignty is an architectural requirement for systems that must function under real geopolitical uncertainty, whatever one's ideology.
Two levels: the target and the everyday rule
The doctrine has two levels. The Operational Doctrine is the reference standard and the target: a system is sovereign only if it can survive fully operational without external control. Pragmatic Patriotism is the everyday rule. Diggs is about making dependency a deliberate choice with a plan for exit, including when the infrastructure is non-European.
A solution that does not meet the reference standard can be accepted temporarily only when all five conditions are met:
- The dependency is explicitly documented.
- The criticality level is defined.
- The exit plan is concrete, realistic and funded.
- The time frame is set: at most 24 months for Level 1, at most 60 months for Level 2. Level 3 has no fixed time frame, but exit must be possible.
- Responsibility for implementation is assigned to a named owner.
If there is no realistic way out within the time frame, the answer is “not acceptable”, however practical the solution is. If any condition is missing, it is postponement.
Both standards are published in full below, in version 1.1. The Scorecard evaluates against them. Version 1.1 will be used when the Scorecard reopens.
Why I am doing this
I am product manager at Akari and built Akari Engine, and I have worked with systems and commercial operations for more than 25 years, from the Linux community in Kongsberg in the 1990s to SaaS and B2B migrations. In that work, I have seen good technical alternatives lose on distribution more often than on technology. Diggs is my attempt to make dependency measurable, and to find out what it takes for the alternatives to actually be adopted.
Digital sovereignty is not established through declarations. It is built through architecture. Or not at all.
Standard 1 · v1.1 ·
The Operational Diggs Doctrine v1.1
Changed from v1.0 (2026-04-28): “a deliberate result of the business model” is now “a direct consequence of the business model”, and the section on deviations now refers to Pragmatic Patriotism. First English version.
Purpose
European digital infrastructure must be able to be developed, operated and maintained without critical dependency on actors outside European jurisdiction. Systems that do not meet this requirement are temporary by definition. They must be treated as technical debt and phased out.
This document is not a goal to strive towards. It is a yardstick to measure against.
Understanding of reality
Digital infrastructure is not neutral. It reflects the power, incentives and control structures of those who built it. Dependency does not arise as an error or an exception — it follows from architectural choices, and is in many cases a direct consequence of the business model.
This means that dependency cannot be regulated away. It cannot be circumvented through rebranding. It cannot be solved by copying existing systems under new names. It can only be eliminated through structural properties built into the system from day one.
Definitions
- Dependency: A state in which a component cannot be replaced within acceptable time, cost or legal risk.
- Structural lock-in: Architecture that systematically prevents switching provider, technology or infrastructure.
- Sovereignty: The ability to maintain full operation and control independently of the will, jurisdiction or business model of external actors.
- Reversibility: The ability to replace a component within a predefined time and cost, without loss of critical functionality.
- Critical layer: Any layer of the infrastructure where failure or external control would cause operational disruption, data loss or legal exposure.
Core principles
The principles are binding and not open to negotiation. They are ranked. In case of conflict, the highest-ranked takes precedence without exception.
Openness in critical layers. All critical layers of the infrastructure must be based on open standards: data formats, protocols and interfaces. Proprietary solutions can only be accepted in non-critical layers, and only where they do not create structural lock-in upstream.
Reversibility as an absolute requirement. All architectural choices must be reversible within a predefined time frame at acceptable cost. Components without a realistic exit option must not be used — regardless of their other properties.
No external control. No external actor may be able to deactivate the system, restrict access or change terms unilaterally. Components that make this possible are unacceptable, regardless of how likely it is to actually happen.
Distribution as an architectural requirement. A system nobody uses solves nothing. Adoption, accessibility and usability are first-class architectural choices — not afterthoughts. Systems that are not adopted without coercion or subsidy are considered architectural failures.
Decision logic
All technology choices — software, services and hardware — are evaluated through four tests in a fixed order. A single failure is enough to reject the solution.
Kill switch. Can an external actor stop, restrict or degrade the system? Yes → reject.
Exit. Can the system be migrated away from within a defined time and cost? No → reject.
Transparency. Are the system's critical functions documented and understandable to independent actors? No → not permitted in critical infrastructure.
Adoption. Will the solution be adopted without coercion or sustained subsidy? No → redesign before implementation.
Priority rules
In case of conflict between considerations, the following ranking applies without exception:
- Sovereignty
- Reversibility
- Adoption
- Functionality
- Optimisation
Prohibited patterns
The following are not permitted under any circumstances:
- Rebranding existing lock-in-based solutions as “European alternatives”
- Proprietary standards in critical layers
- Dependencies defined as “temporary” without a concrete, funded exit plan
- Architecture that legally or technically presupposes control over external infrastructure
- Open-source solutions without a realistic distribution strategy
Minimum requirements for approved systems
A system can only be approved if it:
- Can run on alternative infrastructure without extensive rewriting
- Uses open and documented interfaces in all critical layers
- Has a realistic and funded migration strategy
- Can be understood, maintained and further developed by independent actors
Handling deviations
This doctrine allows no exceptions. Deviations are technical debt. Technical debt accumulates structural risk. Structural risk is what the doctrine exists to eliminate.
The reference standard is the target. Temporary acceptance is assessed under Pragmatic Patriotism, on the conditions set out there.
Systems that do not pass are not bad systems. They are dependent systems. The distinction matters: a dependent system can be excellent — and still unacceptable.
Closing principle
A system is not sovereign because it is built in Europe, operated by European companies or funded by European money.
It is sovereign only if it can survive — fully operational and uncompromised — without external control.
Everything else is a declaration, not a property.
Standard 2 · v1.1 ·
The Diggs Doctrine: Pragmatic Patriotism v1.1
Changed from v1.0 (2026-04-28): Level 1 and condition 4 are aligned, Level 3 now requires a documented dependency and a possible exit, and two language errors are corrected. First English version.
Starting point
The strict doctrine states what full sovereignty requires. The pragmatic version states what is acceptable on the way there — and on exactly what conditions.
This is not a softer standard. It is an operational standard. The difference is that it can be used today, in real organisations, with real budgets and real constraints — without giving up the direction.
Pragmatic patriotism does not mean that everything is permitted if it is practical. It means that temporary dependencies are accepted — but only when they are explicit, time-limited and actively reduced. A dependency without an exit plan is not pragmatism. It is capitulation with a clear conscience.
The four tests
The tests are identical to those in the reference standard. What sets this version apart is that a failure is not automatically disqualifying — instead, it triggers an assessment of the conditions for temporary acceptance.
Kill switch. Can an external actor stop, restrict or degrade the system? Strict conclusion: reject. Pragmatic assessment: What is the likelihood, and what is the consequence? Is the system critical infrastructure or a support function? Is there a concrete plan to eliminate the dependency?
Exit. Can the system be migrated away from within a defined time and cost? Strict conclusion: no means reject. Pragmatic assessment: What is a realistic time frame? Have resources been allocated? Is the migration plan documented, with clear ownership — or is it a non-committal wish?
Transparency. Are the system's critical functions documented and understandable to independent actors? Strict conclusion: no means not permitted in critical infrastructure. Pragmatic assessment: Which layer is opaque? Is it a critical layer or a peripheral one? Can it be isolated so that the dependency is limited?
Adoption. Will the solution be adopted without coercion or sustained subsidy? Strict conclusion: no means redesign. Pragmatic assessment: What is the obstacle — UX, integration, training? Is it a solvable problem, or a structural market problem?
Criticality levels
Not all systems have the same consequences if they fail or are compromised. The doctrine is applied more strictly the higher the criticality.
Critical infrastructure. Systems where failure causes operational disruption, data loss or legal exposure. The reference standard is the target and applies without compromise. A solution that does not meet it can only be accepted temporarily when all the conditions below are met, with exit within at most 24 months.
Important support systems. Systems that are significant but not business-critical. Pragmatic exceptions can be accepted with a documented exit plan, with exit within at most 60 months.
Peripheral systems. Systems with low impact if they fail. The dependency must be documented and exit must be possible, but there is no fixed time frame. The pattern is monitored.
Conditions for temporary acceptance
A solution that fails one or more tests can be accepted temporarily if all of the following conditions are met:
- The dependency is explicitly documented — not implicitly accepted
- The criticality level is defined
- The exit plan is concrete, realistic and funded
- A time frame for independence is set — at most 24 months for Level 1 and 60 months for Level 2. Level 3 has no fixed time frame, but exit must be possible
- Responsibility for implementation is assigned to a named owner
If any of these conditions is missing, it is not pragmatism. It is postponement.
The pattern rule
Individual choices are rarely the problem. The pattern is.
If a portfolio shows over time that dependency is increasing, that temporary solutions are becoming permanent, or that every choice points towards one external actor — that is not an individual problem to be solved. It is a direction that must be changed.
The pattern rule overrides individual case assessments.
The principle of pragmatic patriotism
We cannot be religious open-source fanatics. Europe does not have a complete sovereign stack ready to take over tomorrow. Those who wait for perfection before acting do not act.
But nor can we let pragmatism become a permanent state. Temporary dependencies that are not reduced are not pragmatic choices. They are structural risk that accumulates quietly, quarter after quarter, until the cost of changing course has become too high to bear.
Pragmatic patriotism is not an ideology. It is a governance mechanism. It says: we know what we are giving up, we know what it costs us in future freedom, and we have a plan to pay down the debt. Everything else is self-deception with good rhetoric.
Closing principle
Sovereignty is not established through intentions. It is established through consistent technical choices over time — choices that can withstand being measured, challenged and documented.
This doctrine is an instrument for exactly that. Not a guarantee. Not an answer key. An honest mirror.
Frequently Asked Questions
What is digital sovereignty?
In the doctrine, a system is sovereign only if it can survive fully operational without external control. That is tried with four tests: whether an external actor can stop the system, whether it can be left within a defined time and cost, whether its critical functions are documented and understandable to independent actors, and whether it will be adopted without coercion or sustained subsidy.
Why does European infrastructure matter?
Because jurisdiction follows the provider. The US CLOUD Act can compel US providers to hand over data they control, wherever that data is stored. The provider can also change prices and terms, or shut down APIs, without the customer having any say. The doctrine does not require all non-European infrastructure to go. It requires dependency to be a deliberate choice with a plan for exit.
What is Diggs?
Diggs is a research and development project that I run in my spare time. I am investigating how European organisations can measure how dependent they are, and how that dependency can be reduced. The solution has not been worked out yet. The Scorecard, which tests systems against the doctrine, is a prototype and is paused while the rules are being fixed.
What are the long-term goals?
The goal is a research project together with universities and European suppliers. Nothing has been formalised. In terms of substance, the goal is to make dependency measurable, and to find out what it takes for the alternatives to actually be adopted.
The Scorecard tests systems against these two standards. It is paused while the rules are being fixed.
Cite this version
Bjerke, Kenneth Bæver (2026). The Diggs Doctrine, version 1.1, 2026-09-27. Diggs. https://diggs.no/en/doctrine
Refer to a part with its anchor, for example https://diggs.no/en/doctrine#p3 for P3.
Licence: CC BY 4.0.
Versions and revisions
- v1.1. Changed from v1.0 (2026-04-28): “a deliberate result of the business model” is now “a direct consequence of the business model”, and the section on deviations now refers to Pragmatic Patriotism. First English version.
- v1.0. First version of both standards.
Revisions of the essay
- The answers under “Frequently Asked Questions” have been rewritten.
- My job title has been corrected from “Chief Product Officer (CPO)” to “product manager”.
- Title updated.
- The language has been tightened, and pragmatic patriotism is described as a separate level. The principle is unchanged. The standards have been raised to v1.1: language about intent has been removed, the time frames per level have been clarified, and Level 3 now has a rule. Egress has been removed as the main example of exit cost, cf. The Tetris Syndrome.