you can only protect what you can name

Roughly half the rain that falls on São Paulo started as water the Amazon breathed out days earlier and a thousand miles away. The forest exhales moisture; the wind carries it; it comes down as someone else's rain. Cut the forest, and a city that never touched it loses its water.

We have a map for the river on the ground. We don't have one for the river in the sky.

That gap is not really a science problem — the science is decades deep. It's a naming problem. You cannot fund, protect, or route value to something that has no address. And most of nature's most important systems still don't have one.

the thing most conservation finance can't do

Ask who pays to keep the Amazon exhaling, and the honest answer is: no one, on purpose. The forest supplies rain to farms, cities, and reservoirs that sit in entirely different watersheds — even different countries. Everyone downwind depends on it. No one has a line item for it. The dependency is real; the address is missing.

This is the same failure that leaves headwater meadows, migration corridors, and soil fungi unfunded. They deliver something everyone relies on, and because they cross the boundaries our maps draw — property lines, watershed lines, borders — no single budget owns them.

ensurance closes that gap with a simple, repeatable structure. Give the system a name, and the money has somewhere to go.

how the naming works

Three layers. That's the whole idea.

A watershed becomes colorado-river.basin. A bird migration route becomes americas.flyway. A restoration strategy that spans many places becomes water-cycle.syndicate. Each name tells you what kind of thing you're looking at, points to the specific one, and gives value a place to land.

The power isn't the naming itself — it's what the naming unlocks. Once a system has an agent, every party that depends on it can fund their share of the same thing at once: the insurer, the utility, the city, the farm downstream. Not another one-off grant. A shared account for a shared supplier.

the same pattern flexes four ways

Not every kind of thing gets named the same way, and that's the point — the structure bends to the reality.

Fixed lists you map onto. Some groups mirror the world's existing classifications, so you route value to what's already defined rather than inventing geography. Bioregions follow One Earth (~185). Ecoregions follow WWF's roster (~846). Flyways follow the international bird-conservation frameworks. You don't mint new ones; you fund the right existing one.

An open backbone with rules. .basin is extensible — new watersheds get added — but disciplined: every name carries a water feature, like roaring-fork-river.basin. Water-defined places, where the on-the-ground measurement lives.

Permissionless identity. City groups like .mumbai let anyone mint an agent — a neighborhood, a project, a person. Empty names stay empty and irrelevant; the ones doing real work accumulate a track record that speaks for itself.

Cross-cutting coordination. .syndicate carries a strategy that refuses to sit in one place — mangrove.syndicate, pollinator.syndicate, wildlife-corridor.syndicate. When a kind of thing doesn't have its own group yet, a syndicate holds the work until it earns one.

worked example: giving the sky river an address

Back to the Amazon exhaling into São Paulo. Here's how that dependency gets fundable in our system — starting with what already runs today, not a someday.

Today, it coordinates through a syndicate. water-cycle.syndicate exists to fund the function — moisture recycling, forest cover, the pump itself — across whatever watersheds it touches. It doesn't need a perfect global map of sky rivers to start routing value.

The measurement anchors on the ground. The forest and floodplains that reload the moisture are real places with real parcels: amazon-river.basin, madeira-river.basin, and the downwind places that receive the rain. Certificates attach to these named assets; that's where protection actually happens.

A dedicated group comes when the map is ready. Flying rivers don't yet have an agreed global roster the way flyways do. When one firms up, a .flyingriver group can name the corridors directly — amazon-atlantic-andes.flyingriver — the way .flyway names a migration route. It would sit alongside .basin, not replace it: the ground river and the sky river, each with an address.

That map is closer than it sounds. A colleague of ours is building exactly it — a project called Fluvion that models the atmosphere's moisture flows as a living graph of sources and sinks. The science to draw the sky river's boundaries is arriving fast; what we're describing here is the layer that sits on top, turning those corridors into something the people who depend on them can actually fund. This post is partly an open invitation to build that layer together.

The sequence matters: coordinate now with a syndicate, anchor on named basins, graduate to a dedicated group when the science gives us a roster to stand on. We don't wait for perfect to start funding.

water is irreducibly local — even when the supplier is upwind and the people who depend on it are a country away. every claim traces to a specific place.

other systems waiting for an address

The test for any new group is one question: does this name tell you what kind of thing it is, without duplicating something we already have? Run that test and a lot of overlooked systems line up.

Fungi and soil crust are a telling case. They aren't a place and they aren't one species — they're the connective tissue running underneath forests and deserts, holding everything else together. They don't fit a watershed or a bioregion. A .fungi group could one day name them directly; until then, a syndicate carries the work. Same story as the sky river: name the kind of living thing, fund the specific instances, and let the structure grow into a dedicated group only when the world is ready to define the roster.

Iconic species — whales, salmon, bears — tempt everyone toward their own group. The bar stays high on purpose: a real list, real governance, real funding demand. Until then, a syndicate does the job without cluttering the map.

how the money moves (the same way, everywhere)

Groups and agents are the address book. Instruments are how value actually travels — and they behave identically no matter what's being funded.

A city coin funds civic work. A flyway agent receives funding for its stopover wetlands. A water-cycle.syndicate certificate can back headwater storage in Colorado or forest cover in the Amazon. The system doesn't care whether the dependency runs along the ground or through the sky — only that the place is specific and the people who depend on it can finally pay for it.

the real unlock

Most nature finance dies on a single question: who pays? Naming answers a better question first — what kind of thing is this? — and the payors fall out of the answer.

Trace inward from what you depend on. Trace outward to everyone else who leans on the same thing. Give it a name. Fund the source, not just the symptom.

The map on the ground was never the whole map. The rivers in the sky, the networks underground, the routes across the horizon — they can all have an address now.

If you're the one mapping a system the rest of us can't see yet — a moisture graph, a mycelial network, a migration nobody's funded — consider this an invitation. You bring the frontier science; we bring the rails that turn it into something fundable. Let's give it an address together.

explore what's already named → · bring a system that isn't →