---
title: a town is people who share a place
canonical_url: https://ensurance.app/guide/a-town-is-people-who-share-a-place
markdown_url: https://ensurance.app/guide/a-town-is-people-who-share-a-place.md
subtitle: "one name that holds people, places, and purposes at once"
category: ensurance
---

# a town is people who share a place

*one name that holds people, places, and purposes at once*

**Community resilience is a community's ability to absorb a shock, recover from it, and adapt so the next one does less harm.** One widely used definition, from the National Research Council's *Disaster Resilience: A National Imperative* (2012), describes resilience as the ability to prepare and plan for, absorb, recover from, and more successfully adapt to adverse events. The shock can be a flood, a fire, a heat wave, a drought, or the closing of the plant that employed half the town. Planners usually look at the same few things: whether people know and help their neighbors, whether roads, power, and water keep working, whether local institutions can make decisions fast, and whether the land around the town can still soak up water, shade a street, and slow or steer a fire.

That last item is easy to skip, and it does real work. A creek with room to spread slows a flood before it reaches Main Street. Street trees cool a block on the hottest afternoon. A wetland at the edge of town holds water that would otherwise sit in basements. Those living systems exist and keep working whether or not the town's plan names them. [**Ensurance**](/?from=guide) is how a living system someone names gets funded to keep working. It is not the creek, and it is not the town.

## what a resilient town already has

Most of what makes a town resilient was there before any plan. Neighbors who check on the elderly couple down the street. A volunteer fire department. A ditch company that has managed the same water for a century. A school gym that becomes a shelter. Credit that first. No account replaces it.

One common sorting puts those strengths into a few kinds:

| kind | what it looks like on the ground |
|---|---|
| Social | People who know each other, trusted local leaders, groups that already meet |
| Built | Roads, power, water, and buildings that keep working or come back fast |
| Institutional | A council, a utility, and emergency services that can decide and act |
| Natural | Creeks, wetlands, trees, and soil that slow water, cool streets, and hold slopes; wet meadows, riparian corridors, and grazed or thinned fuels that can slow or steer a fire |
| Economic | Local jobs and savings that let people stay through a bad year |

Every row is people, or a place, or a purpose. Read the table again with that in mind and the town stops looking like one thing.

## a town is the whole triad at one size

A town is people. It is also the places they share — a river, a park, a street — and the purposes those places serve: flood storage, shade, clean water, a view people would miss. What sets a town apart from a crew or a company is that **the place is the reason the people are a group.** That is the fractal reveal of this series. A town is not a bigger person; it is the triad at the size of a town, held together by the place.

:::johnson
**a town is the group defined by sharing a place, so its people, its places and its purposes sit in one name.**

The people leg grows from one person to a crew to a company to a town, and at the town size it carries the other two legs with it.

[see what a named place depends on →](/explore?from=guide)
:::

You can see this in the catalog. Two city-named namespaces carry more than one leg each. They are namespaces made in the protocol, not the towns' own work. Neither city government, nor any university or company in either city, is a member.

**[.boulder](/groups/boulder?from=guide)** held 33 accounts on 26 Oct 2026. Thirty are people accounts. Two are place accounts, [cu.boulder](/cu.boulder?from=guide) and [pearl.boulder](/pearl.boulder?from=guide). One is a purpose account, [ensurance.boulder](/ensurance.boulder?from=guide). The names are names in our catalog. `cu.boulder` is not the university's account.

**[.mumbai](/groups/mumbai?from=guide)** held 22. Nineteen are people accounts and one is a place account, [basin.mumbai](/basin.mumbai?from=guide). Two more are named for the city's water and not yet typed: [mithiriver.mumbai](/mithiriver.mumbai?from=guide) and [powaikhadi.mumbai](/powaikhadi.mumbai?from=guide), both with a wallet deployed. The Mithi River runs through the city to the sea, and its floods and pollution have long been argued over by people in Mumbai who know it far better than we do.

That is one example outside the US and one inside it, with the same shape. Neither namespace is shown here as having funded anything. An account is where a payment can land, not proof that one has.

## the same town at several sizes

The people leg is fractal, and so is the town. Inside one town name sit people, places, and purposes, each at its own grain.

| grain | in Mumbai | in Boulder |
|---|---|---|
| People | 19 accounts | 30 accounts |
| Places | [powaikhadi.mumbai](/powaikhadi.mumbai?from=guide) and [mithiriver.mumbai](/mithiriver.mumbai?from=guide), named for places, untyped; [basin.mumbai](/basin.mumbai?from=guide), a place account | [cu.boulder](/cu.boulder?from=guide) and [pearl.boulder](/pearl.boulder?from=guide), place accounts |
| Purposes | None yet | [ensurance.boulder](/ensurance.boulder?from=guide) |
| The whole name | [.mumbai](/groups/mumbai?from=guide), 22 accounts | [.boulder](/groups/boulder?from=guide), 33 accounts |

What stays the same at each size: an address that can receive, and a person who confirms. What changes: how many people a decision needs and which institution already makes it. A street association decides one way, a city council another. The account changes neither.

## towns depend on more than themselves

No town is resilient alone. People→people edges run in every direction. A town depends on the utility that treats its water, the county that runs its emergency management, the neighboring town that shares its fire crews, and the farmers upstream whose fields absorb a flood. In a big city, a neighborhood depends on the next one over and on agencies it never sees.

People→place edges run outward too. A town's water rarely starts inside town limits. It comes from a watershed drawn by ridgelines, not by the city map. A town that names the places it depends on — and the people who keep them — has a clearer picture of its own resilience than a town that only counts its fire trucks.

None of this is a town plan, and the account does not make one. Local governance already exists and stays: councils, utilities, tribes, ditch companies, neighborhood groups. The account sits beside them. Several accounts can serve the same town, and none of them speaks for it.

## where to start

If you live in a town and want to see this at your size, start with the place, not the platform. [Drop the pin on your town](/guide/drop-the-pin-on-your-town?from=guide) walks through finding what your town depends on. Then look at the watershed in [explore](/explore?from=guide).

If you are a resident who keeps one part of the town — a creek, a park, a block of street trees — you are already the people leg at that size. If you work for a town or county, [ensurance for governments](/solutions/governments?from=guide&topic=ppp-people) shows how the public side uses the protocol.

The last post in this series puts all three legs side by side at every size: [place, purpose, people at any size](/guide/place-purpose-people-at-any-size?from=guide). If you want to talk through your town's places and keepers, [write to us](/contact?from=guide&topic=ppp-people).

## frequently asked questions

### what is community resilience?

Community resilience is a community's ability to absorb a shock such as a flood, fire, or heat wave, recover from it, and adapt so the next one does less harm. It rests on people, built systems, institutions, the local economy, and the living systems around the town.

### how do natural systems make a town more resilient?

Creeks with room to spread slow floods, wetlands store water, trees cool streets, and healthy soil and vegetation hold slopes. Wet meadows, riparian corridors, and grazed or thinned fuels can slow or steer a fire. They work alongside levees, pumps, and emergency services, not instead of them.

### are .boulder and .mumbai run by the cities?

No. They are namespaces made in the protocol. Neither city government, nor any university or company in either city, is a member, and the accounts under them do not speak for either city.

## sources

[National Research Council, *Disaster Resilience: A National Imperative*, The National Academies Press, 2012](https://doi.org/10.17226/13457) — resilience as the ability to prepare and plan for, absorb, recover from, and more successfully adapt to adverse events

## the series

Six posts on one leg of the triad: people, from one person to a whole town.

1. [who counts as people?](/guide/who-counts-as-people?from=guide) — read first
2. [one person can hold an account](/guide/one-person-can-hold-an-account?from=guide)
3. [a small group is big enough](/guide/a-small-group-is-big-enough?from=guide)
4. [every company depends on places it does not own](/guide/every-company-depends-on-places-it-does-not-own?from=guide)
5. **a town is people who share a place** — you are here
6. [place, purpose, people at any size](/guide/place-purpose-people-at-any-size?from=guide)

## the three series

Place, purpose, and people, each walked from the smallest size to the largest, after one question.

- [what counts as a place?](/guide/what-counts-as-a-place?from=guide) — the place series
- [what counts as a purpose?](/guide/what-counts-as-a-purpose?from=guide) — the purpose series
- [who counts as people?](/guide/who-counts-as-people?from=guide) — the people series
- [what do you want to ensure?](/guide/what-do-you-want-to-ensure?from=guide) — the question the three series start from