Files
protocol-droid/seeds/nonviolent-communication-request.yaml
T
Protocolbot 3522c2ec5c feat: expand seed library from 6 to 100 protocols
Added 94 new protocol YAML seed files covering diverse global cultures
and practices:

Indigenous & traditional: Maori powhiri, Aboriginal yarning, Somali xeer,
Moroccan jmaa, Tswana kgotla, Zulu imbizo, Peruvian ronda campesina,
Ohlone land-back, Inuit IQ consensus, Haudenosaunee condolence,
Navajo peacemaking, Ojibwe pipe ceremony, Polynesian talanoa,
Rwandan gacaca, West African palaver tree, Mexican tequio,
Javanese musyawarah-mufakat, Tibetan story council, Korean yangban,
Filipino utari, Ainu practices

Religious communities: Quaker meeting for business, clearness committee,
Amish shunning (Meidung), Mennonite discernment, Jewish hevruta,
Rastafari nyabinghi reasoning

Facilitation: World Cafe, Open Space, Future Search, Six Thinking Hats,
Dynamic Facilitation, Socratic Seminar, Delphi method, Copenhagen
Consensus, Lean Coffee, Hackathon sprint, Agile retrospective,
Stand-up meeting, Pair programming, Roadmap planning

Governance: Sociocratic consent selection, Dynamic self-governance,
Cooperative consensus, Hackerspace consensus, Mastodon governance,
Climate assemblies (x2), Basque asamblearismo

Conflict & repair: Restorative conference, circle sentencing,
Nonviolent Communication (3 protocols), Active listening mirror,
Appreciative apology repair

Community & care: Community kitchen, Gratefulness circle, Passing circle,
Paired walking, Deep listening dyad, Mutual aid, Permaculture charrette

Education: Barefoot College night school, Socratic seminar

Everyday: Various greeting, transition, and gratitude protocols

All protocols credit original sources. Cultural context noted in
descriptions. All YAML files validated.
2026-07-07 22:12:28 -06:00

37 lines
1.6 KiB
YAML

id: nonviolent-communication-request
title: NVC Request Step
description: >-
The fourth step of Marshall Rosenberg's Nonviolent Communication — making
a clear, actionable request rather than a demand. Used after observation,
feelings, and needs have been shared.
source: Center for Nonviolent Communication
source_url: https://www.cnvc.org/
tags: [nvc, communication, request, conflict]
forked_from: null
image: null
steps:
- headline: Form a concrete request
description: >-
The speaker makes a specific, doable request: "Would you be willing
to check in with me before changing our shared deadline?" rather than
"I want you to be more considerate."
- headline: Phrase as a question
description: >-
The request is phrased as a question the other can answer with no,
without punishment. A request is not a demand.
- headline: Receive the answer
description: >-
The speaker receives the answer — yes, no, or counter — without
withdrawing empathy or imposing consequence. A "no" is information
about the other's needs, not a rejection.
- headline: Continue the dialogue
description: >-
If the answer is no, the speaker returns to the other's feelings and
needs, exploring what need the "no" is meeting.
outcome: >-
A clear request is made that the other can freely accept or refuse,
keeping the dialogue in connection rather than coercion.
practice: >-
If a "no" leads to punishment or guilt, the request was a demand. Test
yourself: would you still respect a "no"? If not, you are not yet making
a request.