A 1 1/2 hour experiment building a tiny admin tool for Kiki’s Kitchen Table revealed a repeatable architectural pattern for sovereign business applications: local editing, deterministic data, template rendering, and static deployment.
On April 19, 2026, I ran a simple but revealing experiment: create and sign a note offline on one machine, move it physically, and publish it from another. No cloud. No sync service. No account login. What happened wasn’t just a workflow—it was proof of a different model for authorship.
Modern tools make it possible to build small sovereign applications extremely quickly, enabling a new model for software development.
Continuum is for people and organizations who need durable authorship, self-custodied identity, and a local-first publishing workflow. It is especially well suited for writers, journalists, researchers, human rights activists, ministries, and developers who want to create, preserve, and publish work without depending entirely on centralized platforms.
At first glance, Continuum may appear unnecessary to people who already write documents locally on their computers. After all, anyone can open Word, Markdown, or a text editor and save files in a folder. But Continuum is not merely a place to store documents. It is a local-first authorship and publishing system built around identity, verifiable authorship, durable archives, and intentional distribution. This article explains why the difference matters.
Zipcar, Uber, and Lyft promise convenience but leave us vulnerable to breakdowns and opaque rules. By imagining a decentralized alternative — built on peer-to-peer listings, portable reputation, and Bitcoin payments — we can see how transportation could become more resilient, transparent, and sovereign.
An exploration of how AI can serve as an amplifier for builders and writers without displacing human authority. This article argues for a sovereignty-first approach to AI, where ownership, authorship, and identity remain centered in the individual.
In Part 1, I described the architecture behind a decentralized publishing pipeline using Nostr, GitHub Actions, and GitHub Pages. In this follow-up, I walk through what it actually took to get that same pipeline working again in a new repository — including authentication issues, workflow permissions, and the small but critical details that make it all run automatically.
Last summer, I built a decentralized blog using Nostr, GitHub Actions, and GitHub Pages. I’m now taking that same idea and applying it directly to Continuum — turning tagged articles into a live, automatically updating site with zero manual publishing steps.