Listening Protocol
A group that wants to hear itself.
Not a set of forms. A sequence, and the silences between its steps. The protocol, not the convener, does the pairing, holds the rhythm and carries the rules. Specified plainly enough that a group can build the parts and run it without us. Fork it like an RFC.
Core Map
AsyncEach person draws a picture of themselves for this season. It has six parts: Roots, Now, Tending, Cycles, Alignment and Service. Each part ends in one promise. A permission level is set. A witness is named, or left to the protocol to assign.
Event Preferences
AsyncOnly how much energy you have now. It does not repeat the Core Map. What kind of taking part suits this season: witness, contribute, lead, rest, skip. What I am bringing into the room, and what I am leaving outside. One thing you ask of the group, and one thing you offer it.
Connection Card
SyncA paper card carrying three prompts the protocol drew from the participant's own Core Map. Handed to one paired person. Used to open a single honest conversation. The card stays with the person who received it.
Reflection
AsyncOne shift I noticed in myself. One ask of the circle, if any. And the one part you must fill in: one promise I am making before the next meeting, with how often I will keep it, and a named witness.
Pulse
AsyncRe-draw the Core Map. The protocol shows you the difference. Then review the six promises from the last Map and the Reflection promises since: kept · partial · released.
Rules of the protocol
- Each step is optional. Opting out is itself data, not failure.
- Permission levels travel with the response. Only the participant can change them.
- The protocol, not the convener, decides pairing. Default: match on Core Map closeness or chosen difference. The participant's call.
- Every Reflection contains exactly one promise. The constraint is the feature.
- Promises are reviewed publicly within the pair at the Pulse. Not earlier, not elsewhere.
- The protocol is open and forkable with attribution. Responses are not: they belong to the participant.
Roles
Outputs
A gathering that produces a committable bundle the next gathering can fork is infrastructure. One that doesn't is a show. The Pulse delta is the difference.
The artefacts it names
Two of the three are still in the vault. The steps above say what each one has to do. So a group can make its own in the meantime. That is what "forkable" means here: anyone can copy it and make their own version.