---
title: "form follows function: the agent, the certificate, and the coin"
canonical_url: https://ensurance.app/guide/form-follows-function-the-agent-the-certificate-and-the-coin
markdown_url: https://ensurance.app/guide/form-follows-function-the-agent-the-certificate-and-the-coin.md
subtitle: "three shapes, three jobs, one living thing underneath"
category: ensurance
---

# form follows function: the agent, the certificate, and the coin

*three shapes, three jobs, one living thing underneath*

Form follows function means the shape of a thing should come from the job it does. Louis Sullivan wrote it in 1896, about the new tall office buildings going up in American cities: a bank hall at the bottom wants to be wide and open, the floors of identical offices above it want to be identical, the attic wants to be a lid, and the outside of the building should admit all of that instead of hiding it behind a borrowed temple front. Three jobs, three shapes, one building. The same rule explains why [**ensurance**](/?from=guide) has three shapes, an address and two instruments, and not one.

A meadow and the pollinators that work it already exist and already do their job, whether or not anyone holds a token. Ensurance is how the thing you name gets funded to keep doing it. It is not the meadow, and it is not the bees.

## three jobs, three shapes

Say you have answered the series question. You want to ensure the pollinators of a particular valley, and the wildflower meadows they depend on. Three different things now need to happen, and they are different enough that one shape cannot do all three honestly.

Something has to be the **address**: the place money meant for the pollinators can land, be held, and be spent from, by a person who signs. Something has to be the **record**: a durable mark that a particular person helped fund the condition of that particular meadow, so the funding can repeat and be seen. And something has to be the **currency**: a way for people who care about pollination everywhere, not just in this valley, to put activity behind the theme without having to name one meadow.

Those are the agent, the certificate, and the coin.

### the agent is the address

An **agent** is an account addressed to a place, people, or a purpose. It is an onchain account that can hold assets, receive proceeds, and act. Its shape follows from that job: it has a name you can send to, it persists, it accumulates a history, and it is run by a person. It can act in three modes: manual (the person decides), automated (a saved program on a schedule), or autonomous (the agent decides inside its mandate, and this stays off until the person enables it). The person can always act in the app whatever the mode.

For the valley, the agent is the thing the orchard below the meadow can pay. In the catalog, [pollination.ensurance](https://ensurance.app/pollination.ensurance) is the protocol-wide purpose account for pollination: an address, with no wallet deployed yet. An account for this valley's pollinators, or for the meadow itself, would sit beside it. The address comes before the money, which is the order the whole design keeps. The agent is the vessel. Without it, the money has to land on a person or an organization instead of on the thing. The fuller spec is on [the agents page](/manual/agents?from=guide).

### the certificate is the record

A **certificate** is a recorded share (a record of funding, not equity and not title) in the funded condition of one named agent. Its shape follows from that: it belongs to exactly one account, it is bought directly, and the purchase funds that account. Every agent has at most one certificate, and every certificate has exactly one agent. If you cannot name the agent, you cannot mint the certificate.

A certificate comes in two forms, and the difference is legal, not technical. A **policy** funds a titled natural asset whose owner cooperates with the protocol. A **line** funds stewardship across boundaries where no single titleholder does. The meadow, if a landowner signs on, can carry a policy; the valley's pollination, which crosses every fence, carries a line. [Is ensurance a type of insurance?](/guide/is-ensurance-a-type-of-insurance?from=guide) sets the two side by side, and [what a natural capital certificate actually holds](/guide/what-a-natural-capital-certificate-actually-holds?from=guide) says what the share is and is not. The spec is on [the certificates page](/manual/certificates?from=guide).

### the coin is the currency

A **coin** is a currency named for a theme: a species, a place, or a purpose that is too wide to be one account. Its shape follows from that: it trades on a pool, and the activity of trading generates proceeds that are routed to protection. It is the only instrument in the protocol that funds nature indirectly. It does not buy the meadow. It puts activity behind the word "pollination" and lets the proceeds find the accounts that carry the work.

For the valley, [the pollination coin](/general/pollination?from=guide) is the wide shape and the valley's account is the narrow one. The browsable list of coins is at [/general](/general?from=guide), and the spec is on [the coins page](/manual/coins?from=guide).

:::johnson
**the shape of the instrument is the shape of the thing it serves.**

An address for the thing. A share in one named condition. A currency for a theme too wide to be one thing. Three jobs, so three forms.

[see what the thing you named already connects to →](/explore?from=guide)
:::

## side by side

| shape | its function | what it purposely serves | what it is not |
|---|---|---|---|
| **agent** (an account; ERC-721 with a tokenbound wallet) | hold, receive, act, under a person's signature | the named place, people, or purpose itself | a person, a vote, or [legal personhood](/guide/the-voice-and-the-land?from=guide) |
| **certificate** (ERC-1155, at most one token id per agent) | record a direct share in one agent's funded condition | the specific thing that agent is addressed to | a deed, title to land, an insurance contract, a credit |
| **coin** (ERC-20) | a tradeable currency whose activity generates proceeds | a theme too wide to be one agent | a claim on any particular place |

The token standards appear in that table once so an engineer can check them. In plain words they are the account, the record, and the currency.

## the rule that ties the three together

One rule decides which shape a named thing takes. **If you can name the agent, it can have a certificate. If you cannot, it is a coin.**

"The Crystal River below the marble quarry" names an agent, so it can carry a certificate. "The pollinators of this valley" can be an account, and so can "the meadow on the north slope." "Pollination" as a theme has both: a protocol-wide purpose account and [a coin](/general/pollination?from=guide). A theme too diffuse for anyone to sign for, like the Anthropocene, is a coin only. The rule is not about importance. It is about whether the thing is bounded enough for a person to stand next to it and sign for it.

Between the three runs **proceeds**: the plumbing that routes what comes in, from a coin's trading to the accounts its theme names, from a town's account to the reach above it, on splits and streams anyone can read. One sentence here; [the proceeds page](/manual/proceeds?from=guide) is the rest.

## why not one token for everything?

The honest objection. It would be simpler to issue one token, call it the nature token, and let it do all three jobs. Plenty of projects have.

The trouble is that the three jobs pull against each other. A currency wants to be fungible: any unit is as good as any other, so it can trade. A record of funding one named meadow wants to be the opposite: this meadow, not that one, so the funding can be seen to land. An address wants to be neither; it wants to persist and sign. Fold the three into one shape and you get a token that is a weak currency, a vague record, and no address at all. Sullivan's complaint about the office buildings of his day was exactly this: the outside pretending to be something the inside was not. Form that does not follow function is not neutral. It hides the job.

Keeping the three apart also keeps the honesty apart. A coin can say plainly that it funds protection indirectly. A certificate can say plainly which account it funds. An agent can say plainly who signs for it. None of them has to borrow the others' claims.

## where this stands

On 13 October 2026 the catalog held 2,085 active accounts, 86 of them with a wallet deployed, 191 coins, and 26 certificate token ids on the contract. The three shapes exist and are in use. They are also thin, and most accounts are addresses waiting for a person. Nothing in this post is investment advice, an offer, or a recommendation to hold anything. It is an explanation of why there are three shapes and what each one is for.

## so what do you want to ensure?

Name the thing, and the shape follows. If it is a place, a crew, or a purpose with a boundary a person can sign for, it is an account, and it can carry a certificate. If it is a theme that crosses every boundary, it is a coin. If the thing already has an account and you want to add a share in its condition, [propose the line](/specific/create?mode=suggest&from=guide). If the theme has no coin yet, [propose one](/general/create?mode=suggest&from=guide). If you want a person on the other end first, [write to us](/contact?from=guide&topic=what-do-you-want-to-ensure) and name the thing in the first line.

Then read [the eight design principles](/guide/eight-design-principles-behind-ensurance?from=guide), which are the rules that keep each shape doing its own job.

## frequently asked questions

### what does form follows function mean?

Form follows function is the design rule that the shape of a thing should come from the job it does, not from a style borrowed from somewhere else. Louis Sullivan wrote "form ever follows function" in 1896 about tall office buildings. In ensurance it explains why an account, a certificate, and a coin are three different shapes: they do three different jobs.

### what is the difference between a coin and a certificate?

A certificate is a direct share in the funded condition of one named account; buying it funds that account, and it belongs to exactly one agent. A coin is a currency named for a theme too wide to be one account; it trades, and the trading activity generates proceeds routed to protection. Certificates are direct and specific. Coins are indirect and wide.

### when is something an agent and when is it a coin?

If you can name the thing precisely enough for a person to sign for it, a reach, a parcel, a crew, a species in a valley, it is an agent and can have a certificate. If it is a theme too diffuse for anyone to sign for, like an epoch or a mood, it is a coin. The rule is about boundedness, not importance.

## sources

Louis H. Sullivan, "The Tall Office Building Artistically Considered," *Lippincott's Magazine*, March 1896 — the essay in which "form ever follows function" appears.

## 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)