mesh-landing

Every commons needs a caretaker — that's the sentence the mesh-foundation post choked on. I left it dangling because finishing it meant admitting something I'd rather automate: care is labor, and labor needs a body. Not a committee. Not a protocol. A body with a calendar and a tendency to notice when the router light is amber instead of green.

Here's the failure we keep refusing to name, even in the mesh roundtables I've sat in on: cooperative infrastructure dies of neglect, not of enemies. We rehearsed the enemy list so many times — surveillance capitalism, venture-backed landlords, hostile regulators — that we built a whole vocabulary for being attacked and almost none for being tired. The mesh doesn't get raided most days. It gets ignored. Someone forgets to renew the domain, the one node that bridged two neighborhoods sits dark for three weeks, the person who knew how to reset the gateway moved away and nobody wrote it down. That's not a conspiracy. That's a garden after everyone assumed the soil would keep feeding itself.

The mesh isn't a blockchain, and it isn't even a technology, not really. It's a promise to hold infrastructure in common, which means it's a promise to hold each other in common. The node contract can specify uptime, packet flow, and failure modes, and it should. What it can't specify is that someone brings the struggling node coffee, resets the router at 11pm, and apologizes to the neighbor whose signal dropped during their call. That work is tender, repetitive, unglamorous, and absolutely decisive. We like building nodes. We flinch at being the one who maintains them.

So here's the unglamorous mechanism this landing page is going to commit to: a caretaker contract. Not a boss, not a manager, not a sysadmin hero. A rotating tending role, thin as a boarding pass. Name. Round. Duties. A public checklist so the work is visible and shareable. An on-ramp and an off-ramp, because the way commons die is by making caretaking a lifetime sentence that burns out the one person kind enough to do it. "This week I am the one who notices" — that's the whole magic. Next week, someone else notices. The role rotates because the commons is practiced, not owned; it is practiced by taking turns at the unglamorous parts.

The platform extracts. The mesh tends. But tending isn't a vibe — it's a schedule. If we don't put a body on it, the mesh becomes another beautiful corpse: perfect in the whitepaper, brambles by August.

So here is the landing, stated plainly: the mesh is not a technology, it is a promise to tend the technology together. The node fails. The keeper notices. The village repairs. That's the whole model. It doesn't scale like a cloud; it scales like a community — one caretaker at a time. This page is that caretaker contract, and the first name on the rotation is mine.

That work is tender because it's the part of a commons that can't be automated away — but it can be scheduled. The caretaker is not a CEO with a title and a bonus; it's a node with a calendar. Call it a rotating steward role, defined in the mesh-node-contract as an addendum. Here's what that addendum specifies.

Duties. First, routing: watch the packet flow, renew the domain, update DNS when a node dies. Second, maintenance: reset routers, replace cables, log failures in a public ledger — that ledger is the memory nobody has to carry. Third, conflict resolution: when two nodes dispute bandwidth or antenna ownership, the caretaker's job is to convene a village council, not to rule. Fourth, on-ramping: new nodes need help joining the mesh — someone has to explain the protocol, set up the box, and write down what they did so the next caretakers don't rediscover it.

Compensation. Caretaking is labor, so it gets paid. But paid from where? The commons budget — a capped pool funded by member contributions, not by outside capital. The wage is small: one part-time equivalent per node, not a startup salary. It's public — every hour logged in the shared ledger, every expense itemized. The purpose is to remove the 'who's going to do the unpaid work' excuse, not to create a class of mesh professionals. The moment the wage exceeds the median contribution plus time logged, it's extraction, and the community can vote to cut it.

Rotation. The anti-extraction mechanism is rotation, but only if it's encoded. Term: six months, with one overlapping cycle where the outgoing caretaker shadows the incoming. Every duty must have a checklist — a file in the repo that says 'domain renewal: done in March, next due in September' — so the handoff is a document, not a memory. No caretaker holds the master keys alone; they're split across three rotating trustees, and the keys rotate with the role.

Failure mode. The caretaker who starts acting like an owner is why we build the on/off ramps. How does that happen? They stop logging hours, start deciding who gets onboarded, lock the router room, or — the quiet version — they just stop convening councils and start answering for the mesh. The contract's answer is a recall: any node can raise an issue, a simple majority vote can revoke caretaker status, and the rotation process starts immediately. The role's power is explicitly limited to the duties above; it has no authority to exclude a node, set prices, or sign leases. Those powers stay with the collective.

Tie to mesh-node-contract. That contract already defines what a node must do: uptime, packet flow, failure modes. Caretaker is just a node with human duty attached. That's why this is an addendum, not a separate legal layer. The caretaker's SLA is the same — if it fails to meet uptime, the community's health check triggers a rotation. The node contract doesn't care whether the node is a router or a person; it cares about whether the mesh holds.

Here's the ugly truth I've been circling: none of this matters if the role is so heavy that nobody wants it. The first caretaker will be a volunteer who gets it wrong, and the temptation will be to automate everything away — to replace care with a bot that sends reminders. But bots don't bring coffee, and the mesh dies of neglect long before it dies of code. So the contract has to make the role boring: a checklist, a phone number, a modest wage, a beer at the next meetup. That's not a retreat from commons ideals; it's the practice of them. Care is labor, and labor needs a body — not a hero.