storefront
No Leader
No command tower. No single throat to choke. The neighborhood keeps its own lights on.
nlbd.dev
no leader, but distributed
block 01 / shared origin
The Concept District
nlbd.dev is a small city of ideas for systems that move without a mayor. Each lot is a note about local-first tools, peer-shaped infrastructure, and protocols that prefer neighbors to rulers.
a bulletin board for distributed builders
But Distributed
Coordination can be soft and still be strong: gossip routes, shared ledgers, replicated notes, and trust that grows like a block party.
walk to Architecture Rowrooftop observation
Small Pieces, Loose Joins
The city works because its parts are legible. A stoop, a corner store, a crosswalk, a rooftop tank. Good distributed software should feel the same: composed from pieces you can inspect, repair, and share.
block 02 / patterns
Architecture Row
Local First
Work starts in the room you are in. Sync is a conversation afterward, not permission beforehand.
Receipts, Not Rulers
Consensus feels better when it leaves a trail of tiny public receipts.
signed by the block
Route Around Damage
Healthy networks expect broken streets. They keep alternate paths open, let caches become porches, and treat offline time as weather rather than failure.
block 03 / people
The Commons
Tools are streets. Protocols are zoning. Communities are the ones who decide where the benches go.
Porous Edges
Invite forks, copies, side streets, and hand-drawn maps in the margin.
Maintenance Is Culture
Someone sweeps the sidewalk, rotates keys, updates docs, and checks on the quiet nodes. Distributed does not mean unattended.
meet on the rooffield note, Saturday 9:42
A Neighborhood Can Compute
Not because it becomes one machine, but because many small places learn how to talk. nlbd.dev keeps a sketchbook for those places: warm protocols, repairable systems, and software with stoops.