Initial commit

data/components/appeal.yaml

@@ -0,0 +1,23 @@
+- id: appeal_criteria
+  title: "What are the criteria for a permissible appeal?"
+  description: "Standards for allowing an appeal of a resolution"
+  stageId: appeal
+  order: 1
+  fields:
+    - id: appealCriteriaText
+      type: text
+      label: "What are the criteria for a permissible appeal?"
+      placeholder: "Describe what circumstances justify an appeal of a resolution..."
+      required: true
+
+- id: appeal_process
+  title: "What happens when an appeal occurs?"
+  description: "Process for handling appeals"
+  stageId: appeal
+  order: 2
+  fields:
+    - id: appealProcessText
+      type: text
+      label: "What happens when an appeal occurs?"
+      placeholder: "Describe the process that follows when an appeal is initiated..."
+      required: true

data/components/assessment.yaml

@@ -0,0 +1,59 @@
+- id: dispute_assessment
+  title: "How to assess the state of the dispute?"
+  description: "Methods for evaluating the current status of a dispute"
+  stageId: assessment
+  order: 1
+  fields:
+    - id: disputeAssessmentText
+      type: text
+      label: "How is the state of the dispute assessed?"
+      placeholder: "Describe methods used to evaluate the current status of a dispute..."
+      required: true
+
+- id: values_adherence
+  title: "Are community values being followed?"
+  description: "Evaluating whether the process is aligned with community values"
+  stageId: assessment
+  order: 2
+  fields:
+    - id: valuesAdherenceText
+      type: text
+      label: "How do you ensure community values are being followed?"
+      placeholder: "Describe how you evaluate whether the process adheres to community values..."
+      required: true
+
+- id: jurisdiction
+  title: "Is the dispute within the jurisdiction of this process?"
+  description: "Determining whether this is the appropriate forum for the dispute"
+  stageId: assessment
+  order: 3
+  fields:
+    - id: jurisdictionText
+      type: text
+      label: "How do you determine if a dispute falls within this process's jurisdiction?"
+      placeholder: "Describe how you determine whether this process is appropriate for a given dispute..."
+      required: true
+
+- id: non_participation
+  title: "What happens when someone fails to participate?"
+  description: "Handling non-participation in the process"
+  stageId: assessment
+  order: 4
+  fields:
+    - id: nonParticipationText
+      type: text
+      label: "What happens when someone fails to participate?"
+      placeholder: "Describe procedures for handling situations where someone refuses to participate..."
+      required: true
+
+- id: process_change
+  title: "What if the process needs to be changed?"
+  description: "Adapting the process when necessary"
+  stageId: assessment
+  order: 5
+  fields:
+    - id: processChangeText
+      type: text
+      label: "What if the process needs to be changed?"
+      placeholder: "Describe how the process can be adapted if it's not working effectively..."
+      required: true

data/components/become_aware.yaml

@@ -0,0 +1,23 @@
+- id: reporting
+  title: "Reporting"
+  description: "Methods for reporting conflicts or disputes"
+  stageId: become_aware
+  order: 1
+  fields:
+    - id: reportingText
+      type: text
+      label: "How are conflicts or disputes reported?"
+      placeholder: "Describe the mechanisms for reporting conflicts..."
+      required: true
+
+- id: monitoring
+  title: "Monitoring"
+  description: "Proactive monitoring for potential conflicts"
+  stageId: become_aware
+  order: 2
+  fields:
+    - id: monitoringText
+      type: text
+      label: "How does your community monitor for potential conflicts?"
+      placeholder: "Describe approaches to monitoring for potential conflicts..."
+      required: true

data/components/delegation.yaml

@@ -0,0 +1,11 @@
+- id: delegation_options
+  title: "Where can the dispute be delegated if this process is inadequate?"
+  description: "Alternative processes for disputes that cannot be handled by this process"
+  stageId: delegation
+  order: 1
+  fields:
+    - id: delegationOptionsText
+      type: text
+      label: "Where can the dispute be delegated if this process is inadequate?"
+      placeholder: "Describe alternative processes for disputes that cannot be handled internally..."
+      required: true

data/components/deliberation.yaml

@@ -0,0 +1,35 @@
+- id: deliberation_process
+  title: "How do participants deliberate about the dispute?"
+  description: "Methods for deliberation during the dispute process"
+  stageId: deliberation
+  order: 1
+  fields:
+    - id: deliberationProcessText
+      type: text
+      label: "How do participants deliberate about the dispute?"
+      placeholder: "Describe the format and structure of deliberations..."
+      required: true
+
+- id: additional_voices
+  title: "Who, beyond the main participants, can be heard?"
+  description: "Including additional perspectives in the deliberation"
+  stageId: deliberation
+  order: 2
+  fields:
+    - id: additionalVoicesText
+      type: text
+      label: "Who, beyond the main participants, can be heard?"
+      placeholder: "Describe whose voices are included in deliberations beyond the main parties..."
+      required: true
+
+- id: deliberation_conclusion
+  title: "When is the deliberation over?"
+  description: "Criteria for concluding the deliberation phase"
+  stageId: deliberation
+  order: 3
+  fields:
+    - id: deliberationConclusionText
+      type: text
+      label: "When is the deliberation over?"
+      placeholder: "Describe how you determine when deliberation is complete..."
+      required: true

data/components/initiation.yaml

@@ -0,0 +1,23 @@
+- id: filing
+  title: Filing a Complaint
+  description: Process for submitting a dispute
+  stageId: initiation
+  order: 1
+  fields:
+    - id: filingProcess
+      type: text
+      label: Filing Process
+      placeholder: Describe how disputes are submitted...
+      required: true
+
+- id: notification
+  title: Notification Process
+  description: How parties are informed of the dispute
+  stageId: initiation
+  order: 2
+  fields:
+    - id: notificationMethod
+      type: text
+      label: Notification Method
+      placeholder: Describe how involved parties are notified...
+      required: true

data/components/intake.yaml

@@ -0,0 +1,71 @@
+- id: process_start
+  title: "How does the process begin?"
+  description: "The mechanism for initiating the dispute process"
+  stageId: intake
+  order: 1
+  fields:
+    - id: processStartText
+      type: text
+      label: "How does the process begin?"
+      placeholder: "Describe how disputes are initiated in your community..."
+      required: true
+
+- id: rules_access
+  title: "Where does the community keep its rules?"
+  description: "Location and accessibility of community rules and guidelines"
+  stageId: intake
+  order: 2
+  fields:
+    - id: rulesAccessText
+      type: text
+      label: "Where does the community keep its rules?"
+      placeholder: "Describe where community rules are documented and how they can be accessed..."
+      required: true
+
+- id: information_access
+  title: "Who has access to information about the process?"
+  description: "Transparency and confidentiality policies"
+  stageId: intake
+  order: 3
+  fields:
+    - id: informationAccessText
+      type: text
+      label: "Who has access to information about the process?"
+      placeholder: "Describe who can access information about ongoing dispute processes..."
+      required: true
+
+- id: participant_inclusion
+  title: "How are other participants brought into the process?"
+  description: "Methods for notifying and including relevant parties"
+  stageId: intake
+  order: 4
+  fields:
+    - id: participantInclusionText
+      type: text
+      label: "How are other participants brought into the process?"
+      placeholder: "Describe how relevant parties are notified and included in the process..."
+      required: true
+
+- id: participation_requirement
+  title: "Is participation in the process required or voluntary for involved parties?"
+  description: "Expectations regarding participation"
+  stageId: intake
+  order: 5
+  fields:
+    - id: participationRequirementText
+      type: text
+      label: "Is participation required or voluntary?"
+      placeholder: "Describe whether participation is mandatory or optional for involved parties..."
+      required: true
+
+- id: participation_commitments
+  title: "What commitments does participation involve?"
+  description: "Expectations of participants in the process"
+  stageId: intake
+  order: 6
+  fields:
+    - id: participationCommitmentsText
+      type: text
+      label: "What commitments does participation involve?"
+      placeholder: "Describe what participants are committing to when they engage in the process..."
+      required: true

data/components/preparation.yaml

@@ -0,0 +1,23 @@
+- id: principles
+  title: Guiding Principles
+  description: Core values that guide the dispute resolution process
+  stageId: preparation
+  order: 1
+  fields:
+    - id: principlesText
+      type: text
+      label: Principles
+      placeholder: List the guiding principles for your dispute resolution process...
+      required: true
+
+- id: participants
+  title: Participants
+  description: Roles and responsibilities in the dispute resolution process
+  stageId: preparation
+  order: 2
+  fields:
+    - id: participantsRoles
+      type: text
+      label: Roles and Responsibilities
+      placeholder: Define the roles involved in your dispute resolution process...
+      required: true

data/components/prepare.yaml

@@ -0,0 +1,35 @@
+- id: values
+  title: "Values"
+  description: "Core values that guide the dispute resolution process"
+  stageId: prepare
+  order: 1
+  fields:
+    - id: valuesText
+      type: text
+      label: "What values guide your dispute resolution process?"
+      placeholder: "List the values that inform your approach to conflict..."
+      required: true
+
+- id: agreements
+  title: "Agreements"
+  description: "Agreements about how conflicts will be handled"
+  stageId: prepare
+  order: 2
+  fields:
+    - id: agreementsText
+      type: text
+      label: "What agreements do community members make about handling conflicts?"
+      placeholder: "Describe the agreements community members make about how conflicts will be handled..."
+      required: true
+
+- id: skills
+  title: "Skills"
+  description: "Skills needed for handling disputes effectively"
+  stageId: prepare
+  order: 3
+  fields:
+    - id: skillsText
+      type: text
+      label: "What skills do community members need for handling disputes?"
+      placeholder: "Describe the skills that community members should develop..."
+      required: true

data/components/process.yaml

@@ -0,0 +1,35 @@
+- id: community_values
+  title: "What values does the community hold in disputes?"
+  description: "Core values that guide the dispute resolution process"
+  stageId: process
+  order: 1
+  fields:
+    - id: communityValuesText
+      type: text
+      label: "What values does the community hold in disputes?"
+      placeholder: "Describe the core values that guide your community's approach to conflicts..."
+      required: true
+
+- id: facilitation
+  title: "How is the process facilitated?"
+  description: "Methods of facilitation during the dispute process"
+  stageId: process
+  order: 2
+  fields:
+    - id: facilitationText
+      type: text
+      label: "How is the process facilitated?"
+      placeholder: "Describe who facilitates the process and how they are selected/trained..."
+      required: true
+
+- id: ground_rules
+  title: "What are the ground-rules of the process?"
+  description: "Basic rules of conduct during the dispute process"
+  stageId: process
+  order: 3
+  fields:
+    - id: groundRulesText
+      type: text
+      label: "What are the ground-rules of the process?"
+      placeholder: "Describe the rules of engagement that all participants must follow..."
+      required: true

data/components/resolution.yaml

@@ -0,0 +1,23 @@
+- id: resolution_process
+  title: "How does resolution of the dispute occur?"
+  description: "Methods for reaching a resolution"
+  stageId: resolution
+  order: 1
+  fields:
+    - id: resolutionProcessText
+      type: text
+      label: "How does resolution of the dispute occur?"
+      placeholder: "Describe the process by which disputes are resolved..."
+      required: true
+
+- id: resolution_failure
+  title: "What if a resolution cannot be reached?"
+  description: "Handling situations where resolution is not achieved"
+  stageId: resolution
+  order: 2
+  fields:
+    - id: resolutionFailureText
+      type: text
+      label: "What if a resolution cannot be reached?"
+      placeholder: "Describe what happens when parties cannot come to a resolution..."
+      required: true

data/modules/assessment.yaml

@@ -0,0 +1,27 @@
+- id: participant-goal-assessment
+  title: "Participant Goal Assessment"
+  componentId: dispute_assessment
+  fieldId: disputeAssessmentText
+  content: |
+    The dispute is assessed by focusing on the goals of all participants:
+    
+    1. Each participant articulates what they hope to achieve through the process
+    2. Participants identify areas of common ground and shared interests
+    3. The facilitator helps frame the dispute in terms of compatible and competing goals
+    4. Participants rate the importance of different goals to help prioritize
+    5. Assessment continues throughout the process as goals may evolve
+    6. Resolution options are evaluated against the stated goals of participants
+
+- id: fact-assessment
+  title: "Fact Assessment"
+  componentId: dispute_assessment
+  fieldId: disputeAssessmentText
+  content: |
+    The dispute is assessed through a structured fact-finding process:
+    
+    1. Facilitators interview all parties separately to gather initial accounts
+    2. Documentary evidence and other materials are collected and cataloged
+    3. Areas of factual agreement and disagreement are identified
+    4. Where possible, neutral verification of disputed facts is sought
+    5. A written summary of established facts is created and shared with participants
+    6. The dispute assessment is updated as new information becomes available

data/modules/delegation.yaml

@@ -0,0 +1,41 @@
+- id: police-report
+  title: "Refer to Police Report"
+  componentId: delegation_options
+  fieldId: delegationOptionsText
+  content: |
+    In cases where this process is inadequate, disputes may be referred to law enforcement:
+    
+    1. Situations involving immediate danger or criminal behavior are referred to police
+    2. The community does not attempt to handle issues of criminal law internally
+    3. Support is offered to community members who need to file police reports
+    4. Community members may request an advocate to accompany them
+    5. The community maintains relationships with local law enforcement liaisons
+    6. Community process may resume after legal proceedings if appropriate
+
+- id: internal-process
+  title: "Refer to Another Internal Process"
+  componentId: delegation_options
+  fieldId: delegationOptionsText
+  content: |
+    In cases where this process is inadequate, disputes may be referred to other internal processes:
+    
+    1. The community maintains several conflict resolution pathways for different situations
+    2. Disputes involving multiple community groups are referred to the inter-group resolution committee
+    3. Disputes requiring specialized knowledge may be referred to relevant working groups
+    4. Cases requiring more structured intervention may be referred to the elder council
+    5. Mediation services are available as an alternative to the standard process
+    6. The community maintains clear guidelines for which process is appropriate for different situations
+
+- id: external-process
+  title: "Refer to External Process"
+  componentId: delegation_options
+  fieldId: delegationOptionsText
+  content: |
+    In cases where this process is inadequate, disputes may be referred to external resolution services:
+    
+    1. The community maintains partnerships with professional mediation services
+    2. Complex cases may be referred to specialized conflict resolution organizations
+    3. Cases involving legal questions may be referred to legal aid services
+    4. The community maintains a fund to help members access external services when needed
+    5. A list of recommended external resources is maintained and regularly updated
+    6. The community liaison helps ensure smooth handoff to external processes

data/modules/filing.yaml

@@ -0,0 +1,21 @@
+- id: written-filing
+  title: Written Filing Process
+  componentId: filing
+  fieldId: filingProcess
+  content: |
+    1. Complainant fills out a standard form describing the dispute
+    2. Form includes sections for: parties involved, description of the issue, desired outcome
+    3. Submission can be made via email, website, or physical drop-off
+    4. Complainant receives confirmation of receipt
+    5. Submission is reviewed for completeness within 48 hours
+
+- id: verbal-filing
+  title: Verbal Filing Process
+  componentId: filing
+  fieldId: filingProcess
+  content: |
+    1. Complainant schedules a meeting with a designated intake person
+    2. During the meeting, the intake person documents the dispute details
+    3. The intake person reviews the documented information with the complainant
+    4. Once approved, the complaint is officially filed
+    5. Complainant receives a copy of the documented complaint

data/modules/intake.yaml

@@ -0,0 +1,104 @@
+- 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

data/modules/notification.yaml

@@ -0,0 +1,21 @@
+- id: direct-notification
+  title: Direct Notification Process
+  componentId: notification
+  fieldId: notificationMethod
+  content: |
+    1. All parties are notified in writing within 72 hours of a filed complaint
+    2. Notification includes a copy of the complaint and next steps
+    3. Parties confirm receipt of notification
+    4. If no confirmation is received within 48 hours, a secondary contact method is used
+    5. All notifications maintain privacy and confidentiality standards
+
+- id: facilitated-notification
+  title: Facilitated Notification Process
+  componentId: notification
+  fieldId: notificationMethod
+  content: |
+    1. A neutral facilitator contacts all parties individually
+    2. The facilitator explains the process and shares the complaint details
+    3. Parties have an opportunity to ask questions about the process
+    4. The facilitator documents that notification has occurred
+    5. Follow-up written summary is provided to all parties

data/modules/participants.yaml

@@ -0,0 +1,33 @@
+- id: community-circle
+  title: Community Circle Model
+  componentId: participants
+  fieldId: participantsRoles
+  content: |
+    1. Facilitator: Guides the process, ensures fairness, and helps maintain focus
+    2. Affected Parties: Those directly impacted by the dispute
+    3. Support Persons: Friends, family, or advocates who support affected parties
+    4. Community Members: Representatives who bring wider perspective
+    5. Resource People: Those with relevant expertise to inform the process
+
+- id: mediation-model
+  title: Mediation Model
+  componentId: participants
+  fieldId: participantsRoles
+  content: |
+    1. Mediator: Neutral third party who facilitates the process
+    2. Disputants: Primary parties involved in the conflict
+    3. Advocates: Optional support persons who may speak on behalf of disputants
+    4. Witnesses: Those who provide information relevant to the dispute
+    5. Implementers: Those responsible for helping carry out any agreements
+
+- id: council-model
+  title: Council Model
+  componentId: participants
+  fieldId: participantsRoles
+  content: |
+    1. Council Members: A designated group responsible for hearing disputes
+    2. Complainant: Person bringing the dispute
+    3. Respondent: Person responding to the complaint
+    4. Witnesses: Those providing testimony or evidence
+    5. Advisors: Those who support the council with expertise
+    6. Community Observers: Those who may witness proceedings for transparency

data/modules/principles.yaml

@@ -0,0 +1,32 @@
+- id: restorative
+  title: Restorative Justice Principles
+  componentId: principles
+  fieldId: principlesText
+  content: |
+    1. Focus on harm and needs of those affected
+    2. Address obligations resulting from harm
+    3. Use inclusive, collaborative processes
+    4. Involve all stakeholders (victims, offenders, community)
+    5. Work toward repairing harm and healing relationships
+
+- id: transformative
+  title: Transformative Justice Principles
+  componentId: principles
+  fieldId: principlesText
+  content: |
+    1. Seek to address immediate safety, healing, and agency
+    2. Work to transform the conditions that allowed violence to occur
+    3. Build community accountability systems
+    4. Focus on community-based responses without relying on punitive systems
+    5. Acknowledge interconnection of all forms of violence
+
+- id: consensus
+  title: Consensus-Based Principles
+  componentId: principles
+  fieldId: principlesText
+  content: |
+    1. All members have equal input in decision-making
+    2. Seek solutions that address everyone's fundamental concerns
+    3. Prioritize listening and understanding diverse perspectives
+    4. Work toward outcomes that all parties can accept
+    5. Focus on collaborative problem-solving over adversarial positions

data/modules/process.yaml

@@ -0,0 +1,65 @@
+- id: participant-facilitation
+  title: "Participant Facilitation"
+  componentId: facilitation
+  fieldId: facilitationText
+  content: |
+    The dispute process is facilitated by the participants themselves:
+    
+    1. Participants take turns leading different parts of the conversation
+    2. A written guide provides structure to ensure all voices are heard
+    3. All participants receive basic training in productive dialogue techniques
+    4. Time limits and speaking guidelines ensure fair participation
+    5. Any participant can call for a break or reset if the process becomes unproductive
+
+- id: peer-facilitation
+  title: "Peer Facilitation"
+  componentId: facilitation
+  fieldId: facilitationText
+  content: |
+    The dispute process is facilitated by peers from within the community:
+    
+    1. A pool of trained peer facilitators is maintained within the community
+    2. Facilitators are selected who have no direct involvement in the dispute
+    3. Peer facilitators receive regular training in conflict resolution techniques
+    4. Typically, two peer facilitators work together on each case
+    5. Peer facilitators help maintain structure but do not make decisions
+
+- id: trained-facilitation
+  title: "Trained Facilitation (e.g. mediator)"
+  componentId: facilitation
+  fieldId: facilitationText
+  content: |
+    The dispute process is facilitated by professionally trained mediators:
+    
+    1. Professional mediators with formal certification lead the process
+    2. Mediators are selected from outside the community to ensure neutrality
+    3. Mediators have specific training in the type of conflict being addressed
+    4. The community maintains a roster of approved mediators
+    5. Mediators are paid for their services according to a pre-established rate
+
+- id: facilitation-committee
+  title: "Facilitation Committee"
+  componentId: facilitation
+  fieldId: facilitationText
+  content: |
+    The dispute process is facilitated by a standing committee:
+    
+    1. A dedicated committee of 5-7 members oversees all dispute processes
+    2. Committee members serve rotating terms and receive ongoing training
+    3. For each dispute, a subgroup of 2-3 committee members is assigned
+    4. Committee members with conflicts of interest must recuse themselves
+    5. The committee follows established procedures and maintains records of all cases
+
+- id: nonviolent-communication
+  title: "Nonviolent Communication"
+  componentId: ground_rules
+  fieldId: groundRulesText
+  content: |
+    Our dispute process follows the principles of Nonviolent Communication (NVC):
+    
+    1. Participants focus on observations rather than evaluations or judgments
+    2. Participants express feelings using "I" statements rather than blaming others
+    3. Participants identify needs that are or are not being met by the situation
+    4. Participants make clear, actionable requests rather than demands
+    5. Facilitators help participants translate judgmental language into NVC format
+    6. Active listening is practiced, with participants reflecting back what they've heard

data/modules/resolution.yaml

@@ -0,0 +1,41 @@
+- id: participant-consensus
+  title: "Participant Consensus"
+  componentId: resolution_process
+  fieldId: resolutionProcessText
+  content: |
+    Resolution occurs through consensus of all involved participants:
+    
+    1. Participants collaboratively develop possible solutions
+    2. All parties must agree to the final resolution
+    3. Consensus does not mean everyone's first choice, but a solution everyone can accept
+    4. Multiple rounds of proposal and revision may be necessary
+    5. Facilitators help test solutions against participants' stated needs
+    6. Once consensus is reached, the agreement is documented in writing
+
+- id: facilitator-adjudication
+  title: "Facilitator Adjudication"
+  componentId: resolution_process
+  fieldId: resolutionProcessText
+  content: |
+    Resolution occurs through a decision made by the facilitator(s):
+    
+    1. After full deliberation, the facilitator(s) makes a binding decision
+    2. The decision is based on community guidelines and the specifics of the case
+    3. Facilitators provide a written explanation of their decision and reasoning
+    4. All parties agree in advance to abide by the facilitator's decision
+    5. Decisions establish precedent for future similar cases
+    6. Decisions may be appealed only on specific grounds
+
+- id: jury-adjudication
+  title: "Jury Adjudication"
+  componentId: resolution_process
+  fieldId: resolutionProcessText
+  content: |
+    Resolution occurs through a decision made by a jury of community peers:
+    
+    1. A jury of 5-7 community members is randomly selected
+    2. Jury members receive an orientation to their role and responsibilities
+    3. After hearing all perspectives, the jury deliberates privately
+    4. The jury reaches a decision by two-thirds majority
+    5. The jury provides a written explanation of their decision
+    6. All community members agree in advance to respect jury decisions

data/stages/stages.yaml

@@ -0,0 +1,34 @@
+- id: intake
+  title: "Intake"
+  description: "How disputes enter the process"
+  order: 1
+
+- id: process
+  title: "Process"
+  description: "How the dispute resolution operates"
+  order: 2
+
+- id: assessment
+  title: "Assessment"
+  description: "Evaluating the state of the dispute"
+  order: 3
+
+- id: deliberation
+  title: "Deliberation"
+  description: "Discussing the dispute"
+  order: 4
+
+- id: resolution
+  title: "Resolution"
+  description: "Determining outcomes for the dispute"
+  order: 5
+
+- id: appeal
+  title: "Appeal"
+  description: "Process for reconsidering dispute decisions"
+  order: 6
+
+- id: delegation
+  title: "Delegation"
+  description: "Alternative processes when this one is inadequate"
+  order: 7