104 lines
5.0 KiB
YAML
104 lines
5.0 KiB
YAML
- id: incident-report-form
|
|
title: "Incident Report Form"
|
|
componentId: process_start
|
|
fieldId: processStartText
|
|
content: |
|
|
The dispute process begins when a community member fills out an incident report form. This form includes:
|
|
|
|
1. Details about the parties involved in the dispute
|
|
2. A description of what happened, including dates and times
|
|
3. Any relevant evidence or documentation
|
|
4. A description of the outcome the person is seeking
|
|
|
|
The form can be submitted electronically through our community portal or as a paper form to the designated community coordinator.
|
|
|
|
- id: strong-confidentiality
|
|
title: "Strong Confidentiality"
|
|
componentId: information_access
|
|
fieldId: informationAccessText
|
|
content: |
|
|
Our community practices strong confidentiality in dispute processes:
|
|
|
|
1. Only the designated facilitator(s) and directly involved parties have access to full information
|
|
2. All participants must sign confidentiality agreements
|
|
3. Records are kept secure and are accessible only to the dispute resolution committee
|
|
4. Only general statistics and anonymized outcomes may be shared with the broader community
|
|
5. Breaches of confidentiality may result in removal from the process
|
|
|
|
- id: strong-transparency
|
|
title: "Strong Transparency"
|
|
componentId: information_access
|
|
fieldId: informationAccessText
|
|
content: |
|
|
Our community practices strong transparency in dispute processes:
|
|
|
|
1. Basic information about active disputes is available to all community members
|
|
2. Proceedings are documented and records are available for community review
|
|
3. Regular updates on the status of disputes are shared at community meetings
|
|
4. Only personal identifying information and sensitive details are redacted
|
|
5. All decisions and their rationales are published internally
|
|
|
|
- id: notification-message
|
|
title: "Notification Message"
|
|
componentId: participant_inclusion
|
|
fieldId: participantInclusionText
|
|
content: |
|
|
Additional participants are brought into the process through a formal notification message:
|
|
|
|
1. The facilitator sends a written notification to all identified relevant parties
|
|
2. The notification includes the nature of the dispute, the process that will be followed, and their role
|
|
3. Recipients are given information about how to respond and participate
|
|
4. The notification includes resources to help participants understand the process
|
|
5. Participants have 7 days to acknowledge receipt and confirm their participation
|
|
|
|
- id: summons
|
|
title: "Summons"
|
|
componentId: participant_inclusion
|
|
fieldId: participantInclusionText
|
|
content: |
|
|
Additional participants are brought into the process through a formal summons:
|
|
|
|
1. The dispute committee issues an official summons to all identified relevant parties
|
|
2. The summons clearly states that participation is required according to community agreements
|
|
3. It specifies the date, time, and method of required appearance
|
|
4. The summons outlines potential consequences of non-participation
|
|
5. Delivery of the summons is documented to ensure proper notification
|
|
|
|
- id: voluntary-participation
|
|
title: "Voluntary Participation"
|
|
componentId: participation_requirement
|
|
fieldId: participationRequirementText
|
|
content: |
|
|
Participation in our dispute resolution process is entirely voluntary:
|
|
|
|
1. All parties must consent to participate in the process
|
|
2. Any party may withdraw from the process at any time
|
|
3. No negative consequences result from declining to participate
|
|
4. Alternative means of resolution are suggested for those who decline
|
|
5. The community respects individuals' autonomy in choosing whether to engage
|
|
|
|
- id: required-participation
|
|
title: "Required Participation"
|
|
componentId: participation_requirement
|
|
fieldId: participationRequirementText
|
|
content: |
|
|
Participation in our dispute resolution process is required for all community members:
|
|
|
|
1. By joining our community, members agree to participate in the dispute process when necessary
|
|
2. Participation is mandatory for all named parties in a dispute
|
|
3. Failure to participate may result in consequences as outlined in our community agreement
|
|
4. Only in exceptional circumstances may exemptions be granted
|
|
5. Repeated refusal to participate may result in review of community membership
|
|
|
|
- id: stake-based-participation
|
|
title: "Stake-based Participation"
|
|
componentId: participation_commitments
|
|
fieldId: participationCommitmentsText
|
|
content: |
|
|
Participants in the dispute process must place a meaningful stake into the process:
|
|
|
|
1. Each participant contributes a small financial deposit (adjusted based on ability to pay)
|
|
2. Deposits are returned when parties fulfill all process commitments
|
|
3. Participants commit a specified amount of time to the process
|
|
4. Participants agree to adhere to all ground rules and procedural guidelines
|
|
5. All parties agree to implement the resolution in good faith |