Computing as a public utility, without losing your freedom

A handful of companies control most of the software the world runs on. Operating systems, browser engines, and file formats are owned by a few vendors who profit from subscriptions and built-in obsolescence. The obvious alternative - a government-run, one-size-fits-all system - has its own problems. The answer is to split the difference: make standards public, and leave software choice to everyone else.

Why monocultures fail

When everyone runs the same stack, one mistake breaks the world. Recent years have shown this clearly: a single flawed kernel update brought down millions of machines across industries at once. Monoculture turns a technical bug into a systemic crisis.

Corporate coding has its own costs. Locked file formats tie your documents, photos, and work history to one vendor. Subscription cycles convert what you own into what you rent. Planned obsolescence forces hardware upgrades long before the hardware truly dies.

Why a state-run system fails too

The sci-fi answer looks clean on screen. In Star Trek, LCARS presents a uniform system the state runs for everyone, guaranteeing equity and frictionless access. But making that real would just swap one monopoly for another.

A single, government-mandated operating system creates three predictable failures:

• Stagnation, because technocrats decide what software is allowed to become
• Poor fit, because niche workflows in science, art, and engineering get ignored
• A single target, because one codebase everywhere is a golden prize for attackers

Standards as the true public service

The fix is to change what counts as public infrastructure. The state shouldn't ship programs. It should mandate protocols and substrates; and build them openly.

This is the Public Civic Substrate: open, non-proprietary standards the government maintains and everyone can use for free.

Interoperability is what makes this layer valuable. If formats are open, the market must compete on quality instead of lock-in. If APIs are standard, a hospital system can talk to a public health database without paying a middleman.

The innovation layer built on top

Above the substrate, freedom survives intact. The Private Innovation Layer lets companies, open-source communities, and individuals build whatever they want—custom operating systems, professional creative tools, game engines, new hardware.

A gamer doesn't want a municipal desktop. Neither does a film editor running a specialized color pipeline. Because the underlying protocols are fixed and open, none of that choice threatens public access. Think of a library card: it gets you through the door, but it doesn't pick your book.

What changes in daily life

Small but real differences follow. You could leave a vendor's platform and carry your documents with you. A startup could sell a phone that talks to government services because the protocols are public. LibreOffice, an open format suite, is a concrete model: it exists because the ODF standard made non-proprietary documents possible.

The point isn't that government software becomes everyone's software. It's that no one can hold your public life hostage to a paid upgrade.

The layered model in one view

This is the core argument of the multilayered model: computing becomes a true utility - stable and equitable at the foundation, endlessly varied at the personal edge. Equity doesn't require uniformity. It requires open doors.