Chapter 23. Memory

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 chapter

• Why organisations forget what matters while AI tools keep too much in the wrong place
• How each branch's five documents are written as the work happens, and who can read them
• What's sealed to a seat or a person: boards, personal notes and conversations with Wise-Eye
• What's never kept, or kept only for a while, from the Clearing to outsiders' details
• What stays and what goes when someone leaves, and what's unresolved about erasure

There are two fears about memory, and most people hold both at once.

The first is old. Organisations forget everything that matters. The person who knew why the contract was written that way leaves, and the reason leaves with them. A decision made eighteen months ago gets made again, from scratch, by people who never heard it was made. The minutes exist somewhere, but nobody reads minutes, and they never said why anyway.

The second is new. AI remembers far too much. Every half-formed worry typed into a chat window, every name, every bad day, sits on a server somewhere, kept by default and read by who knows what. Bring an AI companion into an organisation and it seems you get the worst of both: the organisation still forgets what matters, and the machine remembers everything that doesn't.

The sceptic's conclusion is reasonable. Memory is either lost or hoarded. Pick your poison.

What forgetting costs

James Walsh and Gerardo Ungson, writing about organisational memory in 1991, pointed out that an organisation keeps what it knows in a handful of places: in people, in its culture, in its routines, in its structure, in its physical layout, and in its records.¹ In most workplaces, the one that holds the most is people. It's also the one that walks out of the door.

Everyone has watched this happen. Someone hands in their notice and the next four weeks become a frantic attempt to get what's in their head onto paper. The handover document runs to twenty pages and misses the one thing that mattered: who to call when the supplier goes quiet, or why the pricing has that odd exception. Linda Argote's work on organisational learning found that what organisations learn depreciates, sometimes quickly, and that turnover is one of the main reasons.² The business pays twice: once to learn it, and again to learn it over.

The people pay too. The ones who stay become the organisation's memory by default. They're the ones everyone asks. They can't take a holiday without their phone. Their knowledge is valued and also a trap, because it's held nowhere but in them.

The usual remedies don't help much. Minutes record what was said in a meeting, not what the work needed. A shared drive fills with documents nobody can find. A wiki is written enthusiastically for a month and then left to rot. All of them ask people to stop working and write about their work, and people, sensibly, would rather work.

AI tools have flipped the problem without solving it. Many keep everything, in private chats, attached to one person. What the organisation learns in those conversations stays locked inside them, while what the person said about their health or their marriage on a bad evening is kept just as carefully. The memory is enormous and in the wrong place.

Memory as the work goes

Ikujiro Nonaka and Hirotaka Takeuchi drew a distinction that helps here: between what people know and can say, and what they know but would struggle to put into words.³ Their insight was that organisations learn by moving knowledge back and forth between the two, in the middle of the work, not in a separate act of documentation afterwards.

That's the turn. What if the organisation's memory were written as the work happens, by something that was there, in a place everyone can read? And what if what's about a person, rather than the work, went somewhere else entirely, somewhere only they can open?

In an organisation on The Grove, memory is split by whose it is. What the organisation knows is shared. What's about a person is sealed to them. And some things are never kept at all.

What the organisation keeps

Every branch has five standing documents. Its intent: why it exists, in the words of the people who started it. Its offer: what it offers, to whom, how a day of it runs, and what's still unknown. Where we are: what's decided, what's open or parked, and where it's heading next. People: who's involved and how, a name and a connection and nothing more personal than that. And decisions: a dated line for each thing that changed and why.

Nobody sits down to write these. Wise-Eye, the AI companion in every organisation on The Grove, keeps them as it works alongside whoever holds the branch. Every few turns of a conversation, it folds what's been said into the documents: it rewrites the living ones whole when the conversation has moved them, and adds a dated line to the decisions. When it starts a new conversation, it reads them first. So does a new person taking up the branch. Wise-Eye's memory of the work isn't in a private chat. It's in the same documents everyone else reads.

These documents are open to every member by default. A document can be placed in a locked domain (an area of the organisation's work held by one branch), and then only that branch's holders can read it. Others can see that it exists and why they can't open it. The lock lives on the domain, not the document, and it changes only by a proposal in the forum around its branch's parent. No steward can quietly hide what the organisation knows. An open document can't be slipped behind a lock; that takes a proposal too.

Each document keeps its last sixty versions, with who wrote each and why. Deleting a document archives it; nothing is destroyed. When Wise-Eye writes a version that someone takes straight back out, its words go from the document and from its history, and a line remains saying only that a version was withdrawn.

Alongside the documents sits the rest of the record. Every proposal is kept: its tension, its change, what it expected, the advice it was given, each consent and concern, and the review that comes round weeks later to ask whether it worked. A concern that let a proposal lapse stays on the record, and so does the tension behind it. Every act that changes the work, the organisation's knowledge, its connections or the outside world leaves an entry on an append-only trail, and any member can read it. And each branch's playbooks, the steps Wise-Eye follows when it does work for the branch, grow by lines learned when someone corrects it, each one accepted, edited or dismissed by whoever holds the branch.

None of this asks anyone to stop and write. It's what the work leaves behind.

What's sealed

Some things belong to a seat, and some to a person.

Each branch has a board: the lists of what its holders are doing next, waiting for, or might do someday. The board is sealed to the seat. It's encrypted in the browser of whoever holds it, with a key the Internet Computer derives only for the current holders, so the system storing it holds text it cannot read. The parts of the system that route work, read the organisation's health or gather the Field never look inside. When the holders change, the board moves to a new term with a new key. The new holder can open every earlier term, so the board passes to them whole. The person who left the seat gets no key at all, and what's written after they left is under a key they never had. While a seat is empty, the holders of the nearest branch above hold the board, so it's never stranded. When Wise-Eye lands a card, it lands through the holder's own browser.

What Wise-Eye learns about a person, rather than the work, goes to that person's own notes. Their runway, the day job, a worry, a side idea for something else: none of it lands in a branch's documents. The notes are sealed to the person and travel with them. A future co-founder reads the branch's intent, not the founder's worries at one in the morning.

The same goes for a person's conversation with Wise-Eye. There's one per organisation, and Wise-Eye keeps a running summary of it, written for itself: how they like to work, what's been asked and answered, what's still open. That summary is sealed to the person, so the relationship survives a closed tab or a new device. It's shown to them, under "what Wise-Eye remembers from before", and they can have it forgotten at any time. Forgetting the conversation clears that memory. It never touches what was written into the branch's documents, because that was the organisation's.

So when Wise-Eye works out something about the work that nobody actually said, it keeps that in its own summary, as its own reading. A document holds what was said or decided, never a guess.

What's never kept

The Clearing, the space set aside for people to be together without an agenda, is off the record. All that's kept is when and where a gathering meets, who holds it, and for each time it met, how many checked in. Nothing said there is kept. No names, no list of who came, nothing that feeds any reading. If someone stops coming, nobody else is told; only they notice. Wise-Eye never carries anything from the Clearing into a document, even when someone mentions it elsewhere.

Personal details of people outside the organisation don't go where the whole organisation reads. A playbook that holds an email address, a phone number or the name of someone who wrote in on the branch's work is refused, with a plain word about where it belongs instead: the person's details with the work they wrote in on, and a reminder to get back to them as a card on the board with its day. Wise-Eye can't bring someone's contact details into a branch's documents either. We added this after seeing Wise-Eye write a customer's details into a playbook as a note to get back to them, which was the right impulse in the wrong place.

And some things are kept only for a while. A branch that keeps records with personal fields (an order, a booking) gets a locked private part for them, and says how long closed records are kept; after that, they're forgotten. Where a branch's views hold facts about someone, those facts go once the work is closed and the keeping time has passed: the organisation keeps the order and forgets who it was for. People who answer an organisation's test of an idea are remembered until they've been told how it turned out, and a month after; a year at most if they asked to hear; ninety days after the test is decided whatever happens. Their words stay. Who they were doesn't.

When someone leaves

Leaving is a right. Nobody needs permission. When someone goes, they come off every seat they held, their open invitations are withdrawn, and their presence is forgotten. Their sealed notes and their conversations stay theirs; they were never the organisation's to keep.

What stays is what they did. Their decisions, the thanks they gave, the money they recorded, the trail: history isn't rewritten. They can leave a few words of goodbye, and those are kept too. If they're invited back, they return as themselves, with their own record.

And because what they knew about the work was written into the branch's documents as they went, much of it doesn't leave with them. The successor opens the documents, reads where things are, and opens the board their predecessor kept. The twenty-page handover doesn't need writing. It's been written all along.

How we decided

We weighed four ways of remembering. Meeting minutes, which record talk rather than work. A central knowledge base, which nobody writes in. An AI that remembers everything in one place, which is efficient and also exactly the second fear. And forgetting, which is honest but costly.

We chose to split memory by owner. The work is the branch's; the relationship is the person's. That one rule settled most of the rest: where a thing goes depends on whose it is, and Wise-Eye files accordingly. We made the branch documents open by default because an organisation without a boss can't afford knowledge that only some people can see; locks exist, but they're visible and they take a proposal. We sealed boards to the seat rather than to the person, so the work passes to whoever takes it up next.

Viktor Mayer-Schönberger argued that digital systems lost the human virtue of forgetting, and that some forgetting has to be designed back in.⁴ We agree, with a limit. What was decided, and by whom, isn't forgotten, because a self-managing organisation depends on people being able to see how it got here. What's about people who aren't part of it, once the work with them is done, is let go.

What's still uncertain is real. The trail is append-only, and a person's right to have their data erased sits awkwardly with a record that doesn't change. We've designed the answer, keeping personal details apart from the record of what happened so they can go while the fact of it stays, and we've built parts of it, but not all. Duties that differ by country we've designed to be met through each organisation's legal wrapper, and that isn't built. The check that keeps outsiders' details out of playbooks reads names, addresses and numbers; it will miss things written in other ways. Documents keep sixty versions, not every one. And we're still working out how something said in one person's conversation should rise into what the whole organisation keeps, beyond Wise-Eye's judgement about what was said and what was decided. For now, that judgement, and the undo beside everything it files, is what stands between them.

What you might take from this

The question isn't how much an organisation remembers. It's whose memory each thing is, and where it lives. Write what the work needs as the work happens, where everyone can read it. Seal what's about a person to that person. Let go of what nobody needs to keep.

What's known is shared, what's personal is sealed, and some things are never kept.

Notes and further reading