Andrew G. Stanton - April 10, 2026

One thing that became clearer to me today is this:

the software is beginning to catch up with the book.

When I wrote Building Continuum: Local Authority in a Networked World, I was trying to describe a different way of thinking about software and authorship.

Identity, Keys and Drafts should remain local.

Publishing should be explicit.

Those are not just product decisions.

They are first-principles decisions.

But as I have been building Continuum, I have also felt the gap between the architecture and the user’s first experience.

The internal model has been strong for a while.

The local-first structure.

The explicit signing flow.

The scheduler.

The relay model.

The archive.

The durable draft philosophy.

All of that has been there.

But what happens before someone even reaches those ideas?

They need to download, install trust and run it.

That path matters.

And I think for a while I mentally separated that from the “real work.”

I do not think that anymore.

All of these are part of the product:

• The release path
• The build artifacts
• The zip structure
• The hashes
• The native apps

This week really reinforced that.

The macOS and Windows builds were a huge step.

The Docker path remains important.

And now the local-host zip path makes it easier for people working in Linux or Mac terminal environments.

That is not glamorous work.

But it directly affects whether the ideas in Building Continuum can be experienced.

The book can explain the why all day long.

But if the install flow is too difficult, most people never make it to the first meaningful interaction.

That is where the software has to support the argument.

Today it feels like the software is finally starting to do that better.

The build and distribution work is helping the software embody the same seriousness as the book.

That matters to me.

Because I never wanted the book to stand alone as theory.

I wanted it to be grounded in something real.

Today feels like progress in that direction.