Interlude. One Tuesday

A working draft, November 2026. This book is being written while The Grove is being built; expect it to change. Checked against the build as it stood on 1 November 2026.

In this interlude

One ordinary working day in a small bike workshop whose organisation runs on The Grove
How a customer's email finds the right branch, and a drafted reply waits for a person
How work passed back and forth shows up as a tension that blames nobody
How a promise gets a name and a day, and a proposal runs on clocks, not meetings
How the change is looked back on four weeks later, and which chapters explain each step

Before we go inside, piece by piece, here is one ordinary working day. Nothing dramatic happens in it. That's the point.

Kestrel Cycles is a small workshop in a market town. It mends bikes, sells refurbished ones, and runs evening classes for people who want to look after their own. Ruth started it and still holds the root, the part of the organisation that holds the whole. Beneath it sit three branches. Repairs is held by Tomasz, with Jun and Sam as his crew. Sales is held by Ade. Classes is held by Lena. Six people in all, and a purpose they wrote together: keeping bikes on the road.

Twenty to eight

An email arrives from a customer called Amira. She bought a refurbished bike from Kestrel three weeks ago. The gears have started slipping, she's riding to the coast on Saturday, and could someone look at it before then?

It comes in through the same door as everything else that reaches the organisation. Wise-Eye reads it first, and asks what the work is rather than what it mentions. It mentions a sale, and Sales is right there. But what it asks for is a repair, and Repairs has written down that it answers for repairing customers' bikes. That's this. So it lands on Repairs in one step, as a match, not a guess.

Wise-Eye drafts a reply beside it. It knows Amira's name and when she bought the bike, because the organisation already has her earlier messages. What it doesn't know is when anyone can look at it, and it doesn't make that up. Where the day should be, the draft says [a day we can look at it], in square brackets, and waits for a person.

Nine o'clock

Tomasz reads it over his first coffee. Between them, he, Jun and Sam have already said yes to more than they comfortably can this week. And a bike three weeks out of the shop feels to him like Sales' to look after. So he passes it on to Sales, with a line saying why.

Nobody hands it to Ade. It sits on Sales, where whoever holds Sales can take it up.

Eleven

Ade sees it and passes it straight back. It's a repair. Sales doesn't have the stand or the tools. He says so, kindly, in a line of his own.

Both of them are right. That's what makes it worth noticing.

The email has been passed on once and come back. On its own, one trip there and back wouldn't show as anything. But a bike sold in September went the same way a fortnight ago, and recent passes weigh more than old ones. Taken together, it's enough. The next morning, in the heads-up waiting for each person in the forum that covers both branches, there's a new line. Here that forum is the root's: Ruth, Tomasz, Ade and Lena. The line says, more or less, that work keeps passing between Sales and Repairs, and the line between them may be in the wrong place.

Notice what it doesn't say. Nobody dropped anything. Nobody was slow or awkward. A tension like this is read as the map being wrong, never as a person, and none of them has to defend themselves before they can think about it.

Half past eleven

Back on Repairs, Jun opens the draft again. If Amira brings the bike in on Thursday, Jun can come in early on Friday and have it ready by noon. Jun fills the gap, reads the reply once more, and sends it.

That sending is the moment a promise is made. It belongs to Repairs, because Repairs answers for the work. It's carried by Jun, because Jun approved it, and a promise is carried by whoever made it. It has a day, Friday, and a step with a latest start worked back from that day. If the start passes and nobody has the bike in hand, the step reads as at risk and says so, once, in the root's conversation, where anyone holding the branch above may step in. Nothing buzzes on anyone's phone. Jun doesn't need it to. Jun's name is on it, and Jun feels that.

On Friday, a little before noon, Amira wheels the bike out. Jun marks the promise kept.

Wednesday

Tomasz has a seat in the root's forum, because Repairs sits beneath the root. Reading the line in his heads-up, he recognises it. He drafts a proposal.

The tension, in his words: bikes we've sold have nobody to look after them once they leave. The change: a new accountability for Repairs, looking after bikes we've sold, in their first three months. He tries to send it without saying how they'd know it worked, and it won't go. A new accountability has to name a measure it expects to move, and it can't be one the change moves just by being made. He names one: customers chasing us about a bike they bought here, expected to go down.

Ade checks its shape that afternoon. Not whether it's a good idea, only whether it's clear and does what its words say. It's someone other than Tomasz, as it has to be. He agrees it.

Then advice. Tomasz sets three days, the shortest a proposal can. It's put to Jun and Sam, because it changes the branch they hold, and to the people the organisation knows to have skill in how its parts are shaped. Advice would close sooner if everyone asked had answered. Sam takes the full three days, and asks whether three months should be six. Tomasz thinks about it and keeps three, saying why: start small, and let the review tell them. Had he reworked it, it would have gone back to be checked and advised again. Advice is there to be heard, not obeyed.

The vote

The forum that decides is the one around Repairs' parent, the root: the people who hold the root's seat and the seats of the branches grown from it, Repairs, Sales and Classes. So Tomasz, who holds Repairs' seat, takes part as a person in deciding a change to his own branch. Adding an accountability is a low-impact change, so it passes when the people consenting carry a fifth of the forum's trust in this kind of matter and no concern stands. In a forum of four, one person's word could be enough on its own. That's exactly why the vote stays open for two days whatever happens: nobody can pass a change the moment it opens.

Ruth, Ade and Tomasz consent on the first day. Lena says nothing. She's busy with a class and has no harm to name. When the two days end, enough of the forum's trust has said yes and no concern stands, so the change is made. Lena's silence didn't block it, and it didn't count as a yes either. It doesn't wait any longer than that. Only a high-impact change waits out a three-day timelock first, and this isn't one.

Nobody held a meeting. Nobody needed to.

Four weeks on

Twenty-eight days after the change is made, its review comes round, open for a week. Everyone who took part is asked the same questions. Did it land? What did we learn? Keep it, change it, or stop it?

Beside the questions sits the measure Tomasz named at the start. Customers chasing about a bike they'd bought have gone from a handful a month to one. The line about Sales and Repairs has stopped showing. Sam notes that two of the bikes that came back were just past three months, and wonders again about six. They keep the accountability as it is, and what Sam noticed goes into what they learned, where it'll be found if the question comes back.

That's the whole of it. An email, a pass and a return, a promise with a name and a day, a tension that blamed nobody, a change that ran on clocks rather than meetings, and a look back that asked whether it worked.

Each of those steps gets its own chapter in Part three. How a branch says what it answers for is Chapter 9, The branch. How work finds the part of the organisation that answers for it is Chapter 13, Work that finds its way. How a proposal moves through its clocks is Chapter 11, Making decisions, and the trust that weighs the consent is Chapter 12, Trust. The measure as a bet to be tested is Chapter 14, Vision as hypothesis, and the promise and the person carrying it are Chapter 15, Promises. How the organisation read the tension in the first place waits for Part four.