Identity Enables Autonomy
Moving a pico from one engine to another looks like a migration feature, but the point is autonomy. Most people will never run their own servers, so freedom online depends on apps and data that can move between hosts, and identity is what lets them move without breaking. This post lays out the argument behind my IIW demo.
Continue reading {Identity Enables Autonomy}
Pico Engine 1.8 Is for Builders
Smalltalk taught a generation of programmers what it felt like to build by conversing with a live system, and Alan Kay hoped it would turn users into builders. Version 1.8 of the pico engine takes both ideas seriously: a better developer UI for people, an MCP surface for agents, and a schema underneath that makes both possible. This post describes the release and why the builders it serves don't all have to be developers.
Continue reading {Pico Engine 1.8 Is for Builders}
Moving Picos from Mesh to Mesh
Software that can’t leave the machine it was born on isn’t really yours. Version 1.7 of the pico engine lets a pico and its subtree move between engines while its relationships keep working, because other picos follow its DID rather than its address. This post describes what moves, why identity is what makes it possible, and what’s still ahead.
Continue reading {Moving Picos from Mesh to Mesh}
Moving My Sensor Network onto Manifold
I moved my working LoRaWAN sensor network onto the new Manifold framework and pointed Home Assistant at it as the interface. The port went smoothly until the OAuth protection on the mesh blocked the inbound webhooks Helium uses to deliver readings. The fix was to let a mesh owner scope access channel by channel, and the pico engine now supports it.
Continue reading {Moving My Sensor Network onto Manifold}
A Map of the Manifold Environment
A reader asked for a map of the whole Manifold environment and the functional capabilities of each part. I have described this system across three posts, a piece at a time, but never in one picture.
Continue reading {A Map of the Manifold Environment}
Using Home Assistant with Manifold
Manifold is evolving into a proper framework for building meshes of picos, and Home Assistant gives those meshes an interface. A new Home Assistant integration proves out three pieces at once: an OAuth workflow on the pico-engine that lets outside software into the mesh on the owner's terms, a mature interface rather than a custom one, and a pattern that lets specialized communities extend the platform.
Continue reading {Using Home Assistant with Manifold}
A System Ruleset for the Pico Engine
I made a small change to the pico engine recently that has big implications for how we monitor, control, and configure it.
Continue reading {A System Ruleset for the Pico Engine}





