Analysis

From Königsberg to Kongsberg: The Categorical Imperative in System Architecture

Kant's categorical imperative offers a precise test for architectural choices: can the principle behind a solution apply to all actors at once? The lock-in model cannot.

· version 2026-09-27 · Norsk

Revised 27 September 2026: The argument has been tightened, and Kant is used as an analogy, not as proof.

Immanuel Kant was born in Königsberg in 1724, and I was born 260 years later in Kongsberg, which was given the name Konningsberg, the king's mountain, when Christian IV founded the town in 1624 (lokalhistoriewiki.no).

This article uses Kant's categorical imperative as an analogy for architectural choices. The analogy proves nothing, but it provides a precise test: can the principle behind an architecture apply to all actors at once?

§ 1

The universalisation test

Kant's best-known formulation of the categorical imperative reads: “Act only according to that maxim whereby you can at the same time will that it should become a universal law.”

Translated into system architecture, the question becomes: what happens if every provider builds according to the same principle? A model based on closed APIs, proprietary data formats and unilateral control over access presupposes asymmetry. It works because one party can shut the others out. If every actor did the same and locked their users in, systems would stop being able to talk to each other, and the ecosystem everyone depends on would break down. The lock-in model therefore cannot be universalised without interoperability disappearing.

Open standards and data portability pass the test. If everyone follows them, systems can still talk to each other, and every actor can switch provider.

§ 2

Architectural autonomy

For Kant, autonomy is the ability to give oneself laws based on reason. I call the equivalent property for an organisation architectural autonomy: the ability to define the framework for its own technology operations, without being at the mercy of third parties' political or commercial decisions.

My assessment is that this autonomy is weak for most European organisations in 2026. Amazon, Microsoft and Google account for 70 per cent of the European cloud services market (Synergy Research Group, 2025). Organisations therefore operate within frameworks set by others, on infrastructure that can be restricted from another continent.

The work for digital sovereignty can therefore be read as a Kantian project: choosing architectural principles that can apply to everyone, and which thereby preserve each actor's freedom to act.

§ 3

What the test means for an architectural choice

In practice, the universalisation test can be put as a single question before an architectural choice: if every provider in this category did what this one does, could I still move data and services to another?

The question is closely related to the exit test in the Diggs Doctrine: can the system be migrated away from within a defined time and cost? The exit test concerns one specific system today. The universalisation test concerns the principle behind it. A service can pass the exit test because its competitors use open formats. If the service itself is built on a principle that would make exit impossible if everyone followed it, that is a warning sign about the pattern over time. That is what the pattern rule in Pragmatic Patriotism is meant to catch.

In concrete terms, this means three requirements for every choice:

  • Data is stored in formats other systems can read.
  • Integrations go through documented, open interfaces.
  • The agreement gives the right to retrieve all data within a fixed deadline.

A choice that meets all three has a good starting point for passing both tests.

Cite as

Bjerke, Kenneth Bæver (2026). From Königsberg to Kongsberg: The Categorical Imperative in System Architecture. Diggs, version 2026-09-27. https://diggs.no/en/insights/from-konigsberg-to-kongsberg-the-categorical-imperative-in-system-architecture

Licence: CC BY 4.0.

Versions

  • The argument has been tightened, and Kant is used as an analogy, not as proof.
  • Published.