--- title: eight design principles behind ensurance canonical_url: https://ensurance.app/guide/eight-design-principles-behind-ensurance markdown_url: https://ensurance.app/guide/eight-design-principles-behind-ensurance.md subtitle: "the rules the instruments are held to, so they stay in service of the thing" category: philosophy --- # eight design principles behind ensurance *the rules the instruments are held to, so they stay in service of the thing* A watershed keeps working because a forest holds its slopes. The roots slow the snowmelt, the soil stores it, and the creek is still running after the snow is gone. That watershed and the forest that keeps it already exist and already work, whether or not anyone names them. [**Ensurance**](/?from=guide) is how the thing you name gets funded to keep working. It is not the watershed, and it is not the forest. The **ensurance design principles** are the eight rules every instrument is held to, so the money stays in service of a thing like that: 1. The living thing is the subject 2. Name it before you fund it 3. Same four parts at every scale 4. Value runs between things, so route it 5. Many agents, not one fund 6. Create the conditions you depend on 7. Funding first, governance already exists 8. Complex is not complicated Several come from biomimicry, the discipline Janine Benyus set out in *Biomimicry* (1997): take nature as model, measure, and mentor. Others come from evolutionary biology and the study of the commons, credited where they appear. What is ours is the application to accounts, certificates, and coins. :::johnson **if it only works at one scale, it is not finished.** — Every rule below gets the same test: does it hold for one reach of one creek, and for the basin around it? [start with the question →](/guide/what-do-you-want-to-ensure?from=guide) ::: ## the eight principles ### 1. the living thing is the subject **The instruments serve the living thing. Price is a bridge to it, never a measure of it.** Every account, certificate, and coin exists because something alive needs to keep working. We value annual flows against the cost of the stock so a watershed is legible to people who move money, but a dollar figure is a translation, not the worth ([a valuation is not the worth](/guide/a-valuation-is-not-the-worth?from=guide)). When an instrument starts to matter more than the thing it serves, the design has failed. *Where it shows up:* the [approach page of the manual](/manual/approach?from=guide) puts it in one line: the instruments serve nature; nature is never reduced to the instruments. ### 2. name it before you fund it **One agent, one certificate. If you cannot name the agent, it is a coin.** A certificate is a recorded share in the funded condition of one named agent, so there has to be an account on the other end that receives the money and answers for what happens next. A theme too diffuse for anyone to sign for, such as an epoch, is served by a coin instead: a currency whose trading activity generates proceeds that fund protection. Naming comes first because an unnamed thing cannot be held to account. *Where it shows up:* the 1:1 rule is written into [the certificates manual](/manual/certificates?from=guide). On 13 Oct 2026 the contract held 26 certificate token ids, and [/general](/general?from=guide) listed 191 coins. ### 3. same four parts at every scale **A natural asset, an agent, an instrument, and proceeds, whether the thing is one acre or one basin.** Nature shows more detail every time you look closer, so a design that fits only one size breaks at the next. We hold the grammar fixed and let the grain change: the reach of a creek and the river it feeds use the same four parts. The design test is blunt. If a piece does not work at more than one scale, or cannot adapt when conditions change, redesign it. *Where it shows up:* the catalog nests. On 13 Oct 2026 it held 844 accounts in `.ecoregion`, 620 in `.basin`, and 186 in `.bioregion`, with natural assets inside ecoregions and ecoregions inside bioregions. [Post 3](/guide/the-coastline-gets-longer-the-closer-you-look?from=guide) walks the coastline behind it, and why the protocol does not total nature. ### 4. value runs between things, so route it **If the value sits in a relationship, the payment should be able to follow it.** A trail is worth walking because of the creek beside it. A reservoir stays full because of the forest above it. IPBES names relational values between people and nature; our extension, that value also sits between living things, is ours, and [post 2](/guide/what-is-relational-value?from=guide) keeps the two apart. Proceeds are how that in-between gets paid: value moves from where it is earned to where it is kept, the way nutrients cycle through a forest floor. *Where it shows up:* [the proceeds manual](/manual/proceeds?from=guide) maps the flow to a water cycle, with splits, streams, and swappers that route value between accounts. ### 5. many agents, not one fund **Intelligence at the edges. Plural, not exclusive.** Grants, pooled funds, easements, and land trusts protected most of what is protected today. What a single allocator cannot do is know every reach and every slope as well as the people standing on them. So the design is many focused agents, each addressed to one place, people, or purpose, coordinating through syndicates when a job is bigger than one. Multiple agents can serve the same place, and none of them claims to represent it. *Where it shows up:* three accounts in the catalog touch the same Colorado water at different grains: [colorado-river.basin](/colorado-river.basin?from=guide) for the basin, [crystal-river.basin](/crystal-river.basin?from=guide) for a tributary reach, and [colorado-headwaters.syndicate](/colorado-headwaters.syndicate?from=guide), which coordinates headwaters protection across the Roaring Fork and Eagle valleys. It is thin, and we say so: on 13 Oct 2026 the catalog had 2,085 active accounts, 86 of them with a wallet deployed. ### 6. create the conditions you depend on **Generate the activity the system runs on instead of waiting for it to arrive.** Organisms do not only find good conditions; they build them, a process evolutionary biologists call niche construction (Odling-Smee, Laland & Feldman, 2003). Cyanobacteria oxygenated the atmosphere in the Great Oxidation Event, about 2.4 billion years ago, and every oxygen breather since lives in conditions life made. Forests do a smaller version with rain whose moisture starts at the ocean ([you can't seed a cloud that isn't there](/guide/you-cant-seed-a-cloud-that-isnt-there?from=guide)). The agents are designed the same way: their own activity is meant to generate the proceeds and liquidity the system runs on instead of waiting for outside capital. *Where it shows up:* [the coins manual](/manual/coins?from=guide) traces the loop. Trading activity generates fees, the fees become proceeds, and the proceeds are routed to agents and natural assets. ### 7. funding first, governance already exists **We fund and enable. The people on the ground govern.** Every watershed is already governed: water rights, a district, a tribal nation, a county, a family on the same ground for generations. Elinor Ostrom showed in *Governing the Commons* (1990), work recognized with the 2009 Nobel Memorial Prize in Economic Sciences, that communities can govern shared resources through institutions they design for their own place. The protocol adds money and tools to that, not a template, and an account addressed to a river is not the river's vote ([the voice and the land](/guide/the-voice-and-the-land?from=guide)). *Where it shows up:* [the agents manual](/manual/agents?from=guide) sets claims beside evidence. What an agent declares (purpose, mandate, place) sits next to what anyone can observe (holdings, activity, a linked geography), and the fit or the gap between them is the trust signal. ### 8. complex is not complicated **Respect the complexity under the hood. One decision per step at the surface.** A watershed is irreducibly complex, and we do not pretend otherwise. What we refuse to add is complication: forms, jargon, and steps that make a person carry the system's complexity for it. The hard parts stay underneath, and the surface asks for one clear decision at a time. *Where it shows up:* [/act](/act?from=guide) proposes an action as a card, and nothing moves until a person confirms it. A saved program can run the same actions on a schedule. Autonomous mode exists, and it stays off until a person enables it for that agent. ## run one living thing through the eight The question under this whole series is [what do you want to ensure?](/guide/what-do-you-want-to-ensure?from=guide) The principles are what keep the answer honest after you give it. Pick one living thing you depend on or love, and ask: 1. Is the living thing the subject, or the instrument? 2. Can you name the agent? If not, is it a coin? 3. Does it hold one scale up and one scale down? 4. What does it depend on, and can a payment follow that? 5. Who else serves it, and is there room for them? 6. Does it generate any of what it needs? 7. Who governs it today, and do they stay in charge? 8. Is each step one decision a person can make? If it passes, [open an account for a named place, people, or purpose](/agents/create?from=guide), or [propose a line](/specific/create?mode=suggest&from=guide) under an agent that already exists. The [approach page](/manual/approach?from=guide) is the public version of these rules. If your living thing breaks one, we would rather hear where: [tell us what you want to ensure](/contact?from=guide&topic=what-do-you-want-to-ensure). ## frequently asked questions ### what are the design principles behind ensurance? There are eight: the living thing is the subject; name it before you fund it; same four parts at every scale; value runs between things, so route it; many agents, not one fund; create the conditions you depend on; funding first, governance already exists; complex is not complicated. Each keeps the instrument in service of the living thing it funds. ### did ensurance invent these ideas? No. Biomimicry, niche construction, and commons governance each have their own authors, credited above and in the sources below. What is ours is the application to accounts, certificates, and coins, and the extension of relational value to the space between living things. ### does an ensurance agent act on its own? Only if a person turns that on. An agent acts manual (the person decides), automated (a saved program on a schedule), or autonomous (the agent, inside its mandate). Autonomous mode is off until a person enables it for that agent. Nothing moves until a person confirms, a saved program runs, or that person has enabled autonomy. ## sources Janine M. Benyus, *Biomimicry: Innovation Inspired by Nature* (William Morrow, 1997) — the discipline of taking nature as model, measure, and mentor F. John Odling-Smee, Kevin N. Laland, and Marcus W. Feldman, *Niche Construction: The Neglected Process in Evolution* (Princeton University Press, 2003) — organisms modify the conditions they and their descendants live in Elinor Ostrom, *Governing the Commons: The Evolution of Institutions for Collective Action* (Cambridge University Press, 1990), and the [2009 Nobel Memorial Prize in Economic Sciences](https://www.nobelprize.org/prizes/economic-sciences/2009/ostrom/facts/) — communities governing shared resources through institutions they design ## the series 1. [what do you want to ensure?](/guide/what-do-you-want-to-ensure?from=guide) — read first 2. [what is relational value?](/guide/what-is-relational-value?from=guide) 3. [the coastline gets longer the closer you look](/guide/the-coastline-gets-longer-the-closer-you-look?from=guide) 4. [what the triple bottom line counts](/guide/what-the-triple-bottom-line-counts?from=guide) 5. [form follows function: the agent, the certificate, and the coin](/guide/form-follows-function-the-agent-the-certificate-and-the-coin?from=guide) 6. [eight design principles behind ensurance](/guide/eight-design-principles-behind-ensurance?from=guide)