When the towers go down, the neighborhood still talks.

CommuniMesh is a communication system for communities, built for the day power, internet, and cell service fail at the same time. Residents reach loved ones outside the dark area — in plain words, over whatever path still works.

Text only — words cross, nothing else needs to
Phones people already own
One hub serves a whole neighborhood
Satellite reach when every local path is down

The problem

On 9/11, and again in hurricane after hurricane, the same failure repeats: at the exact moment people most need to reach each other, the networks they depend on are down, overloaded, or dark. The federal government answered that failure for first responders — it built them a dedicated network. Nobody has built the equivalent for the people actually standing in the dark neighborhood: residents trying to tell their families they are alive.

It does not take a disaster. In November 2026, an ordinary carrier outage in North Texas left phones with no service for days whenever they left home Wi-Fi. No storm, no attack — just gone. Outages like that are getting more common, and they cluster: the day the grid fails is the day the towers fail.

The primary use case is simple to state: a national-scale emergency. A neighborhood is dark. The people in it need to contact loved ones outside — people whose names nobody in the neighborhood knows — and the only thing that can cross is text. CommuniMesh is designed for that day first, and useful every ordinary day after.

How it works

You talk normally. Codes do the traveling.

Every phone carries the system's intelligence: a codebook of the things people actually need to say, the community roster, and the local places. You speak or type a normal sentence — “We need a few bottled waters at the pool, urgent” — and your phone turns it into a 9-character packet. Only the packet crosses the scarce links. The receiving phone turns it back into a plain sentence.

ME  2A  1000  A
→ “We need a few bottled waters at the pool — urgent.”

Household · place · message · how many and how urgent, in nine characters. Facts — who, what, where, how many, how urgent — always render exactly. The packet itself is the permanent record: relays forward it untouched, so a message can never drift the way a re-told sentence does.

The layers, cheapest first

And when words don't fit the book

The codebook covers the predictable 95%. For everything else there is a built-in failure mode: your exact words go out as clear text, untouched, marked as free text. The system never guesses at a meaning it isn't sure of — it asks, or it sends your words as you said them.

The website: the rendezvous that (almost) never goes down

communimesh.com is hosted in the cloud, far from any single neighborhood's outage. It is the system's switchboard and memory. For each community individually, it holds:

Each community gets its own public page here — for example, Deer Valley's page — and working accounts live in the portal.

How someone outside contacts in

Discovery is solved before the emergency. When you join, you register your outside contacts — the sister in Ohio, the son in Seattle. The site tells them, once, in peacetime: “You're listed as an emergency contact. If their area loses service, reach them at communimesh.com, or text the community's number.”

When the day comes, they write in a plain web form or text the number. The form teaches the rules before they type: text only, keep it short, delivery may take hours. Their message waits in your mailbox here until your community's hub syncs, then rides the mesh to your phone. Your reply comes back the same way. Members who prefer not to be listed in the public directory simply aren't — they can be reached only by the contacts they registered.

Community to community

Communities on CommuniMesh talk to each other through the site — neither one has to reach the other directly. Think of the community as the area code: inside your community, messages need no community address; a message leaving gets its destination community stamped on by the hub. You just pick “my cousin — Seattle” from your contacts.

Seattle is down. Deer Valley, Texas is up.

A Seattle resident says “tell my family in Texas I am safe.” Nine characters cross Seattle's mesh to a hub, ride its scarcest working path — satellite, in a blackout — and land in the family's mailbox here. Deer Valley is up, so delivery is ordinary: site, hub, mesh, phones, plain speech.

The reply waits in Seattle's mailbox until Seattle's hub syncs again. If Seattle has no path for a while, nothing is lost — the site holds the mail. In this system, late is not lost.

Up communities are infrastructure for down ones. Their status rolls up into one shared picture: “Seattle — 62% of households checked in safe. Hub on battery. Next sync 18:00.” One bit per household is all it takes — a whole neighborhood's status fits in a single short message.

Built to degrade, not to die

A fair challenge: isn't one website a single point of failure? It would be, if the site were the system. It isn't — it's a rendezvous, not a road. Everything the site holds exists somewhere else first: the books live on every phone, the queues live on every hub, and the site itself can be mirrored on independent hosts. So failure degrades service one layer at a time:

Full service

Site, community numbers, directory, federation — everything working.

Any one mirror alive

Mail flows again through any surviving copy of the site. The rest catches up.

No site at all

Hubs text each other directly by satellite — coded batches, welfare and bulletins only. Slow and small, but Seattle still reaches Deer Valley with the entire web layer gone.

Local mesh only

The neighborhood talks to itself: needs, offers, check-ins, status held for later delivery. This layer depends on nothing outside the neighborhood at all.

And the floor is honest: an event that kills every layer at once leaves no electronic system standing. The codebook's last defense is that it doesn't care what carries it — nine characters ride anything that moves characters, including amateur radio and LoRa mesh. The book outlives any network built under it.

Open by design

If this becomes public infrastructure, it cannot be a black box. So it isn't one — by design, not by promise:

Messages on this network can be read by the operating authority.

What an emergency operations center actually gets is the picture: which neighborhoods are safe, which need help, which are evacuating — from places that are otherwise completely dark. That feed exists nowhere else.

Communities that don't want that trade run the same system under a community profile, with local control. The protocol doesn't care. The choice is declared, never smuggled.

The record, and the gap

The federal government has paid for exactly this category before — twice, at two different scales:

FirstNetAfter the 9/11 Commission found responders couldn't communicate, Congress created a dedicated public-safety network in 2012: $7 billion in initial funding, a 25-year build contract, 30,000+ agencies today. It serves first responders — and it still rides on towers.
goTennaA mesh-texting company founded after Hurricane Sandy knocked out a third of New York's cell towers. It pivoted to government and accumulated roughly $72.8 million in federal contracts selling hardware radios to professionals.
CommuniMeshThe layer neither one covers: residents. Ordinary people, on phones they already own, talking to their families and their neighboring communities when the infrastructure is down — not prioritized on it, independent of it.

The pattern in the record is consistent: the money follows systems that are proven in the field. Which is why the next step is not a proposal. It's a pilot.

The pilot: Deer Valley, Texas

The first community runs free, as a test pilot and a public proof: Deer Valley, a neighborhood of about 255 homes in the Fort Worth area. The staged plan:

Where it stands today

Read the codebook Download it (CSV)

The codebook, in one minute

Every message is one of over 2,000 phrases, each with a 4-character code. The code is a tiny address: first digit the family, then the group, the item, the variant.

CodeMeans
0000I am safe
1000Need: bottled drinking water
1030Need: ice
8500Urgent: water flooding inside my home
9010Pool is closed

Needs and offers mirror each other, so a neighborhood's needs and its spare capacity match up mechanically. Assignment is deliberately sparse — most possible codes mean nothing, so a garbled digit lands on an empty code and gets flagged instead of silently turning into a wrong message. The book covers status, needs, offers, reports, requests, movement, questions, replies, emergencies, neighborhood operations, lost & found, utilities, weather, work crews, bulletins, and a control layer that can chain messages into lists, conditions, and logic.