Every community of people is different. These are patterns, not a finished shape — we’ll work with you to fit them to your needs.

Pattern · Organization
Built with you— or on your own, if you would rather
members, and coordinators a node a node a node the layer between them we build this with you members their week leadership for funders the only shape with a layer
What’s in the box
Nodes
One eachOr start with two or three coordinator nodes
A way in
Either laneDirect, or through the app you already keep records in
From us
The layerMatching, combining, and a floor under every number
From you
Two weeksDeciding what to try, before anything is built
Running in
90 daysScoped to your organization, and yours at the end
The hypothesis

That an organization can coordinate better without anyone giving up their private context. This is the one we genuinely do not know the answer to, and ninety days is what it takes to answer it in your place.

Many people, many nodes.

Members hold their own. Coordinators bring in what people tell them face to face. Everyone gets a read of their own week — and leadership gets the same quarter as counts, for the donors they have and the application nobody has started.

The situation

Someone needs a ladder this weekend. Someone else has one in the garage that hasn’t moved since spring. Neither knows about the other.

Nothing is broken. Nobody did anything wrong. The information simply existed in two heads that never touched — and the same is true of the taxes, the garden, and the truck two groups booked for the same Saturday.

Meanwhile a report is due, the programme did good work all year, and the only way to describe it is to ask six people to remember March.

The organization already knows all of this. It just doesn’t know that it knows — and it cannot prove any of it.

TODAY needs a ladder has a ladder kept books 15 years needs tax help wants a garden wants a garden wants a garden has a truck WITH A NODE EACH needs a ladder has a ladder kept books 15 years needs tax help wants a garden wants a garden wants a garden has a truck
0 needs met. Same people, same week. 3 needs met. Nobody posted anything. Nobody was read.
The flow

All six components, and two ways in. The amber one is what we build for you — it is the only reason this shape is different from the other two.

TWO WAYS IN — pick per group, or run both A · DIRECT 1 · a member with their own node says it once, in the car B · MEDIATED members a coordinator Notion, a sheet, a form the app they use raw text stays there 4 · CONNECTORS voice notes calendar messages Notion 3 · THEIR TOPOS NODE, ON THEIR MACHINE needs a post-hole digger STANDING · never repeated the fence posts rotted invoices went out Tuesday ingested through B, the raw text also sits in that app — outside this line WHERE IT RUNS · pick one, per person co-located Topos-hosted local + shared GPU 5 · COMMUNITY INTELLIGENCE WE BUILD THIS WITH YOU indexes and matches across nodes a third party, or their own “someone needs one” “someone has one” no source · no reason · no name a need, no reason a capability, no inventory 1 · ANOTHER MEMBER has a post-hole digger mentioned it in March. Never again. 3 · THEIR NODE · THEIR MACHINE has a post-hole digger STANDING · never repeated lent the mower in June free Saturdays until noon same two ways in — A or B, their choice WHERE IT RUNS · not your decision Topos-hosted 6 · THE FEEDBACK LOOP — two audiences, one set of facts The member’s own read in the app, or as a notification — their week, and the matches worth making Back inside that same app the Notion page, the board, the group chat — where lane B came from 2 · THE COORDINATOR who routes all of this by hand today — gets a summary, not a queue LEADERSHIP, AND THEIR FUNDERS the quarter, as counts — for the donors they have, and the application nobody has started WHAT NEVER CROSSED THE LINE — the note it learned it from — why either of them said it — who any count is made of — anything at all, to us

Drag sideways to read the whole diagram →

  • 1Individual users — the people the value is for
  • 2Coordinators — organizers, managers, whoever routes today. In lane B they are also the way information gets in
  • 3The Topos node — one per person. Co-located, Topos-hosted, or local data with a shared GPU
  • 4Connector applications — what brings data in, whether that is a voice note or a Notion workspace
  • 5Community intelligence — the layer that indexes and matches across nodes. Third-party, or the community’s own
  • 6The feedback loop — how an answer gets back to whoever wanted it, including back into the app it came from
Two audiences, one set of facts. Members get a read of their own week. Leadership gets the same quarter as counts — pattern without persons — for the donors they already have and the application nobody has started. Lane A is the strong version; lane B is how most organizations begin, and the trade is in the drawing: through lane B the raw text also sits in that app, outside the node’s line and outside its rules.
The case
Why it gets bought

“For ninety days we find out how much capacity this place already has and isn’t using — and we come out with the number, the mechanism, and evidence a funder will actually read.”

Asking stops costing status

The ask goes to a machine that holds it quietly, not to a room where needing something is a performance in front of people you’ll see on Tuesday.

The quiet stop being invisible

Nobody is silenced to make room. Being known drops from speak up at the meeting to say it once — so volume stops being the measure.

The story stops costing the person it happened to

What reaches a funder is either a count that names nobody, or a story someone released on purpose — for one report, revocably.

The full case
Who it’s worth something to six layers, and the arithmetic you do yourself
The value stack

This is where the six layers come apart most sharply. The person the evidence is about gets the least direct benefit and the person who signs the cheque gets the most — which is exactly why the release has to be real.

Beneficiarythe member What they needed got found, and nobody learned why they needed it. They are counted without being read.
Userwhat they actually do One voice note when it suits them, or one sentence to a coordinator they were going to speak to anyway.
Operatorstaff, coordinators You stop being the person everyone messages to ask whether anybody has a ladder, and you stop reconstructing the year every autumn.
Buyerexecutive director Resources you already paid for get used, requests that land on two staff get resolved between members, and reporting stops being three weeks of archaeology.
Championdevelopment director You have argued for years that this place has more capacity than it uses, and you have never had evidence that was both specific and shareable. This is the first mechanism that produces both.
Economicwhat actually moves Staff hours spent routing and reporting. Utilisation of what you already own. Grant renewal, donor retention, and the applications you didn’t submit because the evidence wasn’t there.
The number, honestly

We will not print a return on investment here. Every figure in it would be invented, and the first person to check would be right. So the worksheet does the half we can do, and the pilot does the half we can’t.

What reporting costs you a year computed in your browser. Nothing is sent anywhere.
What it becomes once this runs the pilot measures it the first report out of it is the measurement, and you keep it.
Ingredients, and what we build what has to be true on day one, and what we build for you
What it takes to install

Who needs a node

Everyone taking part — but not on day one. Lane B in the diagram means you can start with two or three coordinator nodes reading a system you already run, and add member nodes as people want them.

What runs where

Three shapes: a small dedicated machine each; one shared machine holding separate spaces; or hosted, at roughly $20 per person per month. Most places land on a mix — personal information on something you control, heavy work shared.

What staff have to do

Deliberately undecided. The proposal leaves this open on purpose and settles it in the first two weeks, with you, once we know how information already moves here.

What has to be connected

Nothing required. In practice it starts stronger with whatever you already keep records in — that is where the year already is.

What runs, and what we build
You start from this
  • A private node holding one person’s life on their own machine.
  • Voice notes reaching it as a registered source.
  • The four levels, with used but never repeated enforced in the query path rather than in a policy document.
  • Scoped, revocable permission to a named requester, working across the relay proven 2026‑08‑26
  • Aggregate answers at a single node that count without naming anyone.
We build this with you
  • Matching across nodes. The layer that asks many nodes a question and brings the answers back, carrying no source and no reason. The centre of the build.
  • Combining counts across people. One node counts its own owner’s work; this is what turns that into the programme-level number a funder asks for.
  • A floor under every published number, so a count small enough to identify someone never leaves. You set the threshold.
  • Two assemblies off one set of facts — the member’s week, and the quarter leadership sends to a funder.
  • The delivery surfaces you actually use, including the write-back into whatever the place already runs on.

The left column is what a person has on day one. The right column is the ninety days: scoped to your organization, built with you, and yours at the end of it.

The patterns inside this one

The first two are written up in full — they are the two halves this pattern is made of.