Architecture 01 · Matching

The standing need

Someone says once what they need. It stays live. When a person who can help turns up — weeks later, from any direction — the match gets made, and neither of them had to make their life public to be found.

Personal half · shipped Community match · built with you 5 deployments

You start from the private half: a node that holds a standing need and can be asked. The matching layer — the one that carries a need across many people’s nodes and brings the answers back — is what we build for your community. It is the amber box in the diagram below, and it is the work.

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, so one drives to the hardware store and the other one’s ladder keeps sitting there.

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.

Your community already knows all of this. It just doesn’t know that it knows.

The mechanism

The whole information flow, in the six components every pattern in this catalog is drawn from — including the two ways information gets in. The amber one is what we build for you.

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 — it arrives where they already are The Topos app the match, with both buttons “Ask” · “Not now” A notification email, or the messaging app they already read Back inside that same app the Notion page, the board, the group chat — where B came from 2 · AND THE COORDINATOR the person who routes all of this by hand today gets a summary, not a queue WHAT NEVER CROSSED THE LINE — the note it learned it from — why either of them said it — either name, until both agree — 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
Lane A is the strong version; lane B is how most places start. Nobody has to install anything on forty machines to begin. 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. Which lane a community runs, and how far it moves toward A, is one of the things the first two weeks decide.
The case
Read this as
Why it gets bought

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, in the car — so volume stops being the measure.

Offering gets cheap

“I have a truck” said once, to yourself, does the same work as showing up to say it. Most generosity is lost to the cost of announcing it.

The full case
How it works in practice the thirty seconds a member spends, and the two things that come out of it
What a person does
Left in the car, Thursday

“Uh — got the invoices out finally. Still stuck on the back fence, the posts are rotted and I don’t have a post-hole digger. I’ve got the truck free most weekends if anyone needs a hand moving something. Oh, and the Tuesday meeting moved to Thursday.”

28 seconds. No app opened, no form, nothing sorted.
What their node did with it
  • Just theirsthe invoices went out feeds their own recall. Never leaves the machine.
  • Standing needno post-hole digger stays live. Findable without being readable.
  • Standing offera truck, most weekends same mechanism, other direction.
  • Everyonethe meeting moved to Thursday they’d already said scheduling is shareable.
They didn’t sort any of that, and they didn’t have to say all four. “I need help moving a couch Saturday” is a complete contribution.

↳ voice notes reach the node as a registered source — voxterm_transcripts, schema voxterm.transcript.v1

What comes out Illustrative
To the person — Saturday, 9:12

Someone here has a post-hole digger. Want me to ask?

They’ll only see that someone needs one. Not who, not why, not the fence.

AskNot now

Nobody is named until both sides say yes. “Not now” is silent — the other person never learns a match was refused.

To the community — Sunday brief
Connections worth making
  • Three of you have separately mentioned wanting to start a garden.
  • Someone needs bookkeeping help. Someone else did it professionally for fifteen years.
  • Two projects are planning to use the same truck next Saturday.
  • Someone is looking for a post-hole digger. Two are within a block.
No names. Nobody posted anything. Every line is a match, not a broadcast.

One section of five. The rest: what happened, what people need, what people are offering, what’s coming up.

Who it’s worth something to six layers, the four-part argument, and the arithmetic you do yourself
The value stack

Six people read the same pattern and want six different things. The beneficiary is not the buyer, and the buyer is not the person who has to push for it.

Beneficiarythe member
Userwhat they actually do
Operatorstaff, organizers
Buyersigns the cheque
Championspends the capital
Economicwhat actually moves
Outcome, mechanism, consequence
  1. Outcome

    More needs get met inside the community, and more of what the community already owns gets used.

  2. Mechanism

    A need is a standing fact on a private machine, not a post with a shelf life. Matching happens on signals that carry no source — so being findable stops requiring being visible.

  3. Economic consequence

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 routing costs you a year computed in your browser. Nothing is sent anywhere.
What it becomes once this runs the pilot measures it the pilot produces this number, and you keep it.
The install, and the build what has to be true on day one, what we build for you, and where this pattern runs
What it takes to install

Who needs a node

Everyone taking part. People who don’t take part are unaffected and never appear in anything — there is no shadow record of a non-participant.

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 communities land on a mix — personal information on something you control, heavy work on shared hardware.

What staff have to do

Deliberately undecided. The pilot 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. It works with a voice note and no integrations at all. Calendars, notes and whatever the place already runs on are optional — and which of them we wire up is decided with you in the first two weeks.

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. This is the centre of the build.
  • A floor under every number. Suppression on the emission path, so a count that could identify anyone never leaves. The threshold is set with you.
  • A brief written per person. One brief to many readers already works. Giving each person a different view of the same week is part of the build.
  • The delivery surfaces you actually use. The brief, the notification and the write-back into whatever tool 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 community, built with you, and yours at the end of it.

Where this pattern runs

Each deployment names the buyer, the champion, the economic lever and the ninety days.