# Fence Mending Circle: Dispute Resolution Starter Kit ## The Problem Property line disputes over fences, overhanging trees, and boundary encroachments are among the most common—and emotionally charged—conflicts between neighbors. What starts as a trimmed branch or a fence post placed six inches over can escalate into years of hostility, thousands in legal fees, and permanent community fractures. Most neighbors don't want lawyers; they want their neighbor to just *understand* and work something out—but they don't know how to start that conversation without making things worse. ## Who Uses It **The Concerned Homeowner (Primary):** Sarah moved in two years ago. Her neighbor just installed a fence that she's pretty sure crosses onto her property by a foot. She doesn't want to sue anyone, but she also doesn't want to lose part of her yard. She needs to know: Is this actually a problem? What do I even say? **The Accidental Encroacher:** Mike built a fence last summer using what he thought was the property line. His neighbor just sent him an angry text with a survey attached. He's mortified but also defensive. He needs help crafting a response that doesn't admit liability but opens dialogue. **The Long-Suffering Neighbor:** Teresa has dealt with her neighbor's oak tree dropping leaves in her gutters for a decade. She's never said anything, but she's reached her limit. She needs guidance on whether this is even a legitimate complaint and how to raise it without seeming petty. **Community Mediators:** Local peacemakers who want to be listed as resources and receive referrals for disputes they can help resolve informally. ## Core Features 1. **Situation Assessment Wizard:** User answers 5-7 plain-language questions about their dispute (fence/tree/boundary, who did what, how long ago, current relationship temperature). The system categorizes the issue and surfaces relevant guidance and template letters. 2. **Plain-Language Fence Law Library:** Curated explanations of common property rules—fence responsibility, tree overhang rights, adverse possession basics, survey requirements—written for regular people, not lawyers. Each explainer ends with "This is general info, not legal advice." 3. **De-escalation Letter Generator:** Customizable templates for opening dialogue: "First Contact" letters, "Response to Complaint" letters, "Let's Get a Survey Together" proposals, and "Informal Resolution Agreement" drafts. Users fill in specifics; the system generates warm but clear language. 4. **Local Mediator Directory:** Searchable list of community mediation services, retired attorneys offering pro bono guidance, and neighborhood association contacts who've handled similar disputes. Users can filter by language, availability, and dispute type. 5. **Civic Services Connector:** Based on the dispute type, the tool surfaces relevant city services—code enforcement contacts, permit offices for fence construction, surveyor recommendations, and local court small claims info if amicable resolution fails. 6. **Resolution Agreement Builder:** When neighbors reach a handshake deal, this feature helps them document it: who agrees to what, by when, what happens if someone doesn't follow through. Generates a PDF both parties can sign. 7. **Anonymous "Am I Being Reasonable?" Check:** Users can submit their situation anonymously and get AI-powered feedback on whether their position is typical, aggressive, or potentially problematic—helping them calibrate before engaging their neighbor. ## WellSpr.ing Integration Points ### MCP Tools (via POST to `https://wellspr.ing/mcp` using JSON-RPC 2.0) | Tool | Use Case | |------|----------| | `search_civic_services` | Find local mediation services, dispute resolution programs, and legal aid organizations based on user location and dispute type | | `get_city_services` | Surface relevant municipal resources: code enforcement, permit offices, property records departments, small claims court info | | `get_businesses` | Locate local surveyors, fence contractors (for remediation), and attorneys specializing in property law | | `get_business_detail` | Pull contact info and details for specific mediators or service providers when user selects one | | `ask_ody` | Power the "Am I Being Reasonable?" feature and provide contextual guidance based on user's situation description | | `get_civic_ideas` | Show existing community proposals related to neighbor relations, boundary disputes, or mediation programs—user might find allies | | `reach_number` | Display engagement metrics showing how many neighbors this tool has helped find resolution (builds trust) | ### REST Endpoints | Endpoint | Use Case | |----------|----------| | `GET /api/officials` | Display relevant local officials (city council, neighborhood liaisons) who handle constituent complaints about code enforcement or property issues | | `GET /api/geo/portals?area_code=NNN` | Identify neighboring civic data portals; useful when a dispute crosses municipal boundaries | ### WCIB Endpoints | Endpoint | Use Case | |----------|----------| | `POST /api/wcib/ody-ask` | Submit user's situation narrative for AI-powered assessment and template customization | | `GET /api/wcib/ideas` | Display related civic tech ideas; user might want to build on or contribute to neighboring projects | ### Future Capabilities (Not Yet Live) - **Roadmap: Covenant Commerce** — Once payment rails exist, mediators could offer paid consultations directly through the platform - **Roadmap: Verified Mediator Registration** — Submit and verify community mediators via a structured onboarding flow - **Roadmap: Resolution Tracking** — Log anonymized resolution outcomes to help future users understand what works ## Data Model ### `disputes` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | user_id | uuid | Anonymous or authenticated | | dispute_type | enum | fence, tree, boundary, drainage, other | | situation_summary | text | User's description | | temperature | enum | cold, warm, heated, legal | | created_at | timestamp | | ### `templates_used` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | dispute_id | uuid | FK to disputes | | template_type | enum | first_contact, response, survey_proposal, resolution | | generated_text | text | The customized letter | | downloaded_at | timestamp | | ### `mediators` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | name | string | | | organization | string | Nullable | | languages | array | | | dispute_specialties | array | | | contact_method | string | email, phone, or both | | wellspring_business_id | uuid | Links to get_business_detail for full info | ### `resolutions` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | dispute_id | uuid | FK to disputes | | agreement_summary | text | What was agreed | | pdf_url | string | Stored agreement document | | signed_at | timestamp | | ### `law_explainers` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | topic | string | e.g., "Tree Overhang Rights" | | jurisdiction | string | State or locality | | content_md | text | Markdown explainer | | last_reviewed | date | When a legal volunteer confirmed accuracy | ## Vibe Coding Prompt to Get Started ``` Build a web app called "Fence Mending Circle" — a civic tech tool helping neighbors resolve property disputes before they escalate to lawyers. TECH STACK: - React frontend with Tailwind CSS for styling - Express.js backend -