Stories A told story · drafted 2026-09-28

The Circle Around One Person

Give every person one key, a journey they and the people around them can see and replay, and a circle of people and assistants who can reach them directly or through each other — measured at every step.

The seven beats

World
One group around one person, everyone with an assistant
Cast
The person; the people around them; an assistant each; a chairman; a chief who routes
Knock
The operator, 2026-09-28: from love; starts with a key; a journey that connects
Want
One key, a journey seen and replayed, and two ways to reach each person
Way
Signals kept; the key opens; assistants carry; the meeting walks the circle; every step counted
Turn
The meeting that runs while someone watches
Lesson
Open — not learned yet

A key is small.

It fits in a sentence. Twenty-four words, written on paper, kept in a drawer. It opens one person's record, and the record opens onto everyone who has ever tried to help them.


There is a plan for a child. It has sections. It names the people around him: a father, a mother, a keyworker, a tutor, a doctor, a caseworker. Each of them sees one part of him. None of them sees all of it.

Each of them has an assistant now. The assistant knows what its person knows, and a little of what the others know, and nothing it was not given.


The same shape holds for a student with a course, and for a customer with a need.

A person at the centre. People around them. An assistant for each.

The record used to be a list of what happened to the person at the centre. It becomes something else: the journey they are on, where they stand in it, and who is walking beside them.


A message can travel two ways.

It can go straight to the person, in the words it was written in. Or it can go to the assistant who knows them, who decides whether the person needs to see it now, and in what words, and on which channel.

Both are honest only if the person can tell them apart. A message sent in someone's name says so.


Once there was a meeting that needed a room, a date and a chair.

Every day, the same people said the same things to each other, out of order, and the person at the centre heard about it afterwards.

Until one day the meeting ran by itself. A chairman opened it. A chief asked each voice in turn. Each assistant answered for its person, and each person could step in and say it themselves. The person at the centre could read every word.

Because of that, nobody had to remember who had said what.

Because of that, the next meeting started where the last one ended.


Every step is counted. How many people were given a key. How many used it. How many moved from each step to the next.

Winning is not a trick. It is making each step a little easier than it was, and knowing that it was.


The key is still small.

It opens more now.


Where the metaphor stops being true

  • "Each of them has an assistant now." True for the ten people in group:ehc (on dev). NOT WIRED for any other group: no door mints a personal assistant when a person joins a circle.
  • "A message sent in someone's name says so." NOT WIRED. The composer's left control is the + (AddMenu.tsx), and no thread row records "sent by an assistant on your behalf".
  • "The meeting ran by itself." Partly. meeting-handoff exists in lib/workflow-templates.ts, and the chairman and CEO agents exist. Nothing walks a group's members in turn and asks each assistant to speak.
  • "Every step is counted." Marketing stages are counted per group (chapter two). EHC plan stages and learning stages are not joined to the same rail.
  • "It opens onto everyone." Only within consent. Chapter one's cards 7, 25, 26 and 27 hold that line, and 26 (forget) is in flight on the secure lane.

Sentences that would be false if shipped

  • "Every person in your CRM has a personal assistant."
  • "Meetings run themselves."
  • "Your customer can see everything we know about them." (Chapter one card 27 is red.)
  • "One key works everywhere." (The key restores only at one.ie until the recovery tool ships, text/key.md deliverable 10.)

The family this story generates

File What it holds
text/crm-journey-story.md this story
text/crm-journey.md the promise — chapter three
text/crm.md · text/crm-learns.md chapters one and two

Connected to

Every link here was checked against the repo when the page was built. 3 names the story uses could not be found and are shown without a link.

People

  • the person at the centre
  • their family and the professionals around them
  • the operator
  • a client's team

Agents

Each opens a chat with that agent.

Skills

Each opens the skill's page.

  • meeting
  • storytelling
  • promise-make

Paths

The flows this story walks — trigger → step → step.

  1. trigger: the operator writes to a person with the toggle on the assistant → agent: the person's assistant drafts → condition: does it need the person's own eyes? → human: human:notify → tool: entity:reply
  2. trigger: a meeting is called → agent: chairman opens the thread → agent: ceo asks each member's assistant in turn → agent: each assistant answers → human: the operator may step in → tool: the ledger closes the thread

Tools

Receivers and scripts it signals.

Promises

What it holds; a told promise opens its own story.

Events

Every event is a signal; each names the path it marks or warns.

  • entity:reply · from the operator, directly operator → person tags: crm, messages
  • human:notify · from the person's assistant operator → assistant → person tags: crm, assistant
  • thread:append · from chairman, ceo, and each assistant in turn each voice → the meeting's thread tags: meeting

Transactions

  • the wallet that comes with the key
  • each assistant's turn spends group credit on one model call

Analytics

  • conversion at every step of the journey, from the group's own analytics
  • how many people hold a key
  • meetings held, voices heard