Leap of Faith Labs · a protocol · v0.1

Listening Protocol

open · forkable with attribution
responses belong to the participant
← Try it
an open sequence for being understood — five steps, and the silences between them

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.

asyncasyncsyncasyncasync

Core Map

Async
Once per season · about 20 minutes

The participant draws a seasonal portrait across six sections — Roots, Now, Tending, Cycles, Alignment, Service — each closing in a single promise. A permission level is set. A witness is named, or left to the protocol to assign.

Stored as a version. v1, v2, v3 across seasons. The protocol keeps the archive; the participant owns it.

Event Preferences

Async
48 hours to 2 weeks before a gathering · about 3 minutes

Current energy only, with no overlap with 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 ask of the gathering; one offer to it.

State, not story. This step expires after the event. It is never archived against the person.

Connection Card

Sync
During the gathering · a physical card

A 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.

This is the only synchronous step. Everything before it prepares the room; everything after it digests what happened in it.

Reflection

Async
24 to 72 hours after · about 5 minutes

One shift I noticed in myself. One ask of the circle, if any. And, the only mandatory field: one promise I am making before the next gathering, with a cadence and a named witness.

Exactly one promise. No more. This feeds the Sankalp Stambh, the promise ledger. Quality over quantity is built into the form, not asked for.

Pulse

Async
Every 3 to 6 months · about 20 minutes

Re-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.

Released is a valid outcome. An unkept promise honestly named is healthier than a kept one held grudgingly. The loop closes here, and opens again.
Niyama (the rule you hold yourself to) · the rules that travel with the response

Rules of the protocol

  1. Each step is optional. Opting out is itself data, not failure.
  2. Permission levels travel with the response. Only the participant can change them.
  3. The protocol, not the convener, decides pairing. Default: match on Core Map closeness or chosen difference. The participant's call.
  4. Every Reflection contains exactly one promise. The constraint is the feature.
  5. Promises are reviewed publicly within the pair at the Pulse. Not earlier, not elsewhere.
  6. The protocol is open and forkable with attribution. Responses are not: they belong to the participant.
Bhūmika (the part you play) · who does what

Roles

Participant
The autonomous agent. The source of every promise. Nothing is imposed; everything is offered.
Convener
Kit-keeper, not interpreter. Holds the trunks, sets the date, opens the room. Does not read the responses.
Witness
One other participant, paired by the protocol. Holds the promises across the gap until the next Pulse.
Steward
Rotating. Responsible for protocol upkeep, forks and version bumps. The role guards the form, not the people.
Phala (the fruit of it) · what makes this a public good, not a workshop

Outputs

Per participantA versioned Core Map archive. Private by default; theirs to release.
Per gatheringA Reflection batch and a Pulse delta, aggregated only with explicit permission.
Per versionA public commit log: what changed, why, who proposed it, who consented.

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.

Beside this protocol

The artefacts it names

Two of the three are still in the vault. The protocol above says what each one has to do, so a group can make its own in the meantime — that is what forkable means here.

Core Map v0.1Step 1: the seasonal portrait in six movements, each closing in a promise with a cadence and a witness.in the vault · listed in the commons, not yet public
Sankalp KarandakThe synchronous container: the run-kit for the one step that happens in a room.in the vault · not yet public
The AI Usage CardsThe individual vow this protocol first named in May 2026: nine plain-language cards for saying what AI did and what stayed yours.live · open it →