The Compositor as a Contract
WEFT OS — Post 4 of 10. Why a Wayland compositor is an authority boundary, and why WEFT treats it as a security contract before it is architecture.
Posts tagged #projects
-
-
Why Servo, and Why Now
WEFT OS — Post 3 of 10. Why Servo is a foundation choice, what it implies, and what it costs.
-
They Were Right, Just Too Early: Firefox OS, Ubuntu Touch, Sailfish
WEFT OS — Post 2 of 10. Firefox OS, Ubuntu Touch, and Sailfish OS were right about the direction of computing — and arrived before the world was ready to pay for it.
-
The Desktop Is a Document
WEFT OS — Post 1 of 10. A desktop shell as an HTML document, and why that is neither a browser skin nor Electron.
-
Karapace: because 'it works on my machine' is not an identity
Why I built a deterministic environment engine, how it compares to Toolbox, Distrobox, Kapsule, mise, and Homebrew, and what 'content-addressed' actually means when you're the one implementing it.
-
Liquid delegation, Condorcet, and a computationally sane Schulze
A practical tour of liquid delegation as a trust graph, the Condorcet paradox, and how to compute Schulze results without hand-waving — grounded in Likwid’s implementation.
-
Dualite: a stereo plugin that refuses to pick a side
A tour of Dualite — an unreleased JUCE multi-FX where left and right get independent lives, plus two parallel lanes and a Mid/Side switch when you want the stereo field to behave like math.
-
OpenLikwid: building governance infrastructure (without building a social network)
A tour of Likwid/OpenLikwid: modular governance, liquid delegation, a plugin-shaped backend, and why I’m building it.