buildtall.systems
Tools and patterns for the data sovereign.
Termites build cathedrals without architects. They leave traces in the environment, and the structure emerges. Complex systems like markets and software protocols evolve the same way.
The old way
A platform decides what you see, who you reach, and what your data is worth. A company controls the servers, the algorithms, the terms. When it dies or changes direction, everything built on top of it dies too.
Centralized coordination is fragile. It requires permission and produces dependency.
The alternative
What if coordination didn't require a coordinator? What if the right structures could emerge from simple traces left in a shared environment—no central authority, no single point of failure?
This is how the most resilient systems in nature already work. And it has a name.
The foundational idea
Stigmergy
Stig·mer·gy — coordination through traces left in a shared environment. An ant leaves a pheromone trail. Another ant follows it and reinforces it. No ant plans the route. The path emerges.
In software: you publish a relay list, and clients know where to find you. You curate a feed, and others subscribe. You leave structured data on open protocols, and systems self-organize around it. No platform required. The traces are the infrastructure.
The Traces We Build
Each tool creates a different kind of environmental trace—structured data on open protocols that others can build on, route through, and extend.
stigmergic.dev
Live markdown renderer for developers. Write locally, see changes instantly with syntax highlighting, LaTeX, and Mermaid diagrams. Your working documents rendered as you think.
stigmergic.dev →Cascade Engineer
Network Wars strategy game. Five factions compete on a network graph—pure HTML and CSS, optional Nostr identity for persistent stats. Playable in any browser.
cascade.engineer →npub.dev
Configure your relay list. Client-side only, no server touches your keys. Your relay list is a trace that tells the network where to find you—and where you want to be found.
npub.dev →DRSS
Bridge RSS feeds to Nostr. Your blog becomes addressable events on relays you choose—discoverable, cacheable, portable. The feed is the trace. Anyone can follow, mirror, or build on top of it.
drss.io →npub.blog
Read Nostr long-form articles. Local-first, client-side rendering with IndexedDB caching. No server between you and the relays.
npub.blog →Blog
Long-form writing published to Nostr, rendered from relays. Ideas as environmental traces—findable, linkable, impossible to deplatform.
https://buildtall.systems/blog →Why It Matters
The material means of information production are in the hands of billions: your device, your network connection, your computing power. The question is whether we build commons-based systems with symmetric access, or recreate the old asymmetries through proprietary control.
Stigmergic systems are structurally resistant to capture. There's no center to seize, no API to revoke, no terms of service to change. When coordination happens through open traces on shared protocols, the system belongs to everyone who participates—and no one who doesn't.
Why "buildtall"?
In Tetris, there's a strategy: leave one column empty, stack the blocks, wait for the long piece. When it comes, you clear four rows at once. Low time preference. Sacrifice immediate small wins for compounding returns. In data sovereignty, that means protocols over platforms, standards over shortcuts, infrastructure that compounds over deep time. The blocks pile up. We're building tall.