Articles

Analyses, method and log entries from the project. Every text has a date, and revised texts say when they were changed.

13 texts, newest first

  1. · Analysis · revised · answers question 3

    What it cost to rebuild diggs.no

    I rebuilt diggs.no according to the doctrine. Ten of 22 dependencies were replaced or removed in one day, with at least 500 minutes of measured session time. What cost the most was not the code, but what surrounded it.

  2. · Analysis

    One provider, four dependencies

    I mapped the dependencies in two of my own systems. In one I found 24 where I would have guessed ten. In the other, one provider turned out to be four dependencies.

  3. · Analysis · revised

    Who gets to define web 4?

    The term web 4 is used for different things. The EU described it in a strategy in 2023. Ukraine, the United Kingdom and the United States have since put language models in front of the state's services. My assessment is that such entry points will shape what web 4 becomes, more than definitions on paper.

  4. · Method/Scorecard

    Four models, one editor

    I wrote an article about language models being trained to please. I wrote it together with four language models.

  5. · Method/Scorecard · revised

    The Voice in My Own Code

    In “Neutrality is a design choice”, I wrote that language models are shaped by rules the reader doesn't see. Then I went looking for the voice in my own evaluation tool.

  6. · Analysis

    Neutrality is a design choice

    When you ask a language model something, you get an answer that looks like a reference work. It is a product — shaped by choices you don't see, made by people you don't know, in a jurisdiction you don't control.

  7. · Log

    A quick life update

    It's been quiet on diggs.no for a while. That's not because there's been little to share — quite the opposite.

  8. · Log · revised

    Akari Engine: From Prototype to Launch

    Last year I began building prototypes to show where we could go. Three months after the Engine project began, we had launched a product. Bringing the people behind it together was the most rewarding part.

  9. · Method/Scorecard · revised

    We launched an instrument — not a product

    On 28 April 2026, we launched something on diggs.no that wasn't there before. An evaluation tool that tests software, services, and hardware against the Diggs Doctrine.

  10. · About Diggs · revised

    The Asynchronous Architect

    I think best in writing. That explains why Diggs looks the way it does.

  11. · Analysis · revised

    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.

  12. · Analysis · revised

    The Tetris Syndrome: What Switching Provider Actually Costs

    What does it cost to switch cloud provider? A worked example for a hypothetical organisation with 200 employees shows that data egress is the smallest item.

  13. · About Diggs · revised

    The Architecture Behind the Mindset

    These are the people and works I use as references in my work on Diggs, and what each of them is used for.