Everyone already has a way they hold work in their head. Some people pin things up. Some people write a list and cross it off. Some people keep everything and search it later. None of them are wrong, and none of them are going to change because a piece of software asked.
So Relay doesn't ask. The substrate is fixed and opinionated — objects, edges, provenance, a fail-closed visibility rule. The surface is not. Below is one set of material rendered five ways. Switch between them and watch the counter: the objects and the edges never change. Only the render does.
Fourteen objects from a week of real-shaped work — platform relays, a client thread, brand research, two personal notes — and the eight provenance edges between them. Every surface below draws all fourteen and all eight. The fingerprint is computed from what actually got drawn, read back out of the page after each render, so a surface that quietly dropped something would show it.
The framing work so far names two ways a user is plural. This is a third, and it is the one a person actually notices on day one — see hats & lenses for the first two.
| Axis | What varies | What it needs | The one-word version |
|---|---|---|---|
| Hat | Which identity you're in — employer, client A, personal | Separation, enforced, fail-closed | Walls |
| Lens | Which role you're reading as — reviewer, implementer, strategist | Projection, not duplication | Windows |
| Surface | Which shape you already think in — board, list, pile, ledger | Rendering, not configuration | Furniture |
Hats are walls. Lenses are windows. Surfaces are furniture — and you brought your own.
The substrate is the room. It has to be the same room, or the walls don't mean anything."It can be whatever you need" is one of the most dangerous sentences in software. It is what Notion, Airtable, and Obsidian all say, and all three charge the same price for it: the user has to build the thing before it does anything. Flexibility gets paid for at the door, in setup, by someone who hasn't seen the value yet.
“Assemble your own workspace from primitives.” That is a blank canvas with extra steps, and it is a different product with a different buyer.
A blank canvas asks you to have already decided how you work, and then do the labour of expressing it.
The structure already exists, because the graph is built as a by-product of using the tools you already use. The surface is a render of structure that's already there, not a container you fill.
Picking a surface is picking a view. It costs one click and nothing is lost by changing your mind.
Because of how the substrate is shaped: first contact writes an edge, every touch after is timeline, and every surface is a projection of those two tables through the visibility rule.
That is already the architecture. Five surfaces isn't five features — it's the same query, laid out differently.
This claim is only safe while the substrate stays fixed and opinionated. The moment a surface needs its own fields, its own ordering rules, or its own permissions, it stops being a render and becomes a product — and then there are five products to maintain and the promise inverts. The discipline is that a surface may only choose what to show and how to lay it out. It may never choose what exists.
This is the strongest form of “nobody invented the send.” People already pin, list, pile, and file. Relay doesn't introduce a habit — it renders the one you have, and makes it survive a session boundary.
A vividly-metaphored name prescribes a surface. If the product's claim is “whatever shape you need,” a name that commits hard to one shape argues against it — which sharpens the case for arbitrary marks over evocative ones.
It also puts a caveat on the substrate-side pass: Archive, Ledger, Vault, and Register are containers, and a container is a surface. The starter worked because it persists without implying a shape.
Because a pinboard app gives you a pinboard. The same objects can't also be an archive when you need to find something in eighteen months, and they can't come with you when you change tools.