# Fence Line Negotiator: Shared Boundary Cost Splitter ## The Problem Fence disputes are one of the most common sources of neighbor conflict in American cities, often escalating from a simple repair need into years of tension or even litigation. When a shared boundary fence fails, homeowners face an awkward dance: Who asks first? Who pays what? What does the city even require? This tool transforms that dreaded conversation into a collaborative, transparent process by providing real contractor data, clear municipal code summaries, and a fair splitting framework that both neighbors can review independently before talking. ## Who Uses It **Primary: The Initiating Homeowner** Sarah notices the fence between her yard and her neighbor's is leaning badly. She's lived next to the Johnsons for three years but they've never discussed property lines. She wants to approach them fairly but doesn't know local fence codes or what contractors charge. She needs ammunition for a *friendly* conversation, not a confrontation. **Secondary: The Responding Neighbor** Marcus gets a text from Sarah with a link: "Hey, I put together some info about our fence situation — take a look when you have a chance?" He clicks through, sees transparent cost breakdowns, learns that city code actually says they split it 50/50 for boundary fences, and feels relieved rather than ambushed. **Tertiary: Renters Caught in the Middle** Jamie rents a house and the backyard fence is falling apart. They need to communicate between their landlord and the neighbor's landlord, so having a neutral document to forward both directions helps everyone. ## Core Features 1. **Address-Based Fence Assessment Intake** User enters their address and their neighbor's address (or selects "I don't know their exact address" and points to the shared boundary on a simple map). They specify fence length in feet, current condition (leaning, rotted posts, missing boards, total replacement needed), and fence type (wood privacy, chain link, vinyl, wrought iron). 2. **Local Contractor Discovery with Real Pricing Context** The tool queries WellSpr.ing for local fencing contractors, displays their contact info and reach numbers, and prompts the user to request quotes. Provides average cost ranges for the region (sourced from public construction data or user-submitted actuals) so both neighbors understand ballpark figures before quotes arrive. 3. **Municipal Code Summarizer via Ody** Using the address's jurisdiction, the tool asks Ody to explain local fence regulations: height limits, setback requirements, permit needs, and — critically — boundary fence cost-sharing laws. Many cities (especially in California) have "good neighbor fence" laws requiring 50/50 splits. Ody surfaces this in plain language with source citations. 4. **Fair Split Calculator with Adjustable Factors** Default split is 50/50, but the tool allows adjustments both neighbors can see: "My side faces the finished side" (+10% to that neighbor), "Fence primarily contains my dog" (+15%), "Previous fence was installed entirely by other party" (-20%). Each adjustment is visible and negotiable before finalizing. 5. **Shareable Proposal Document Generator** Creates a clean, printable/PDF-able summary: fence details, contractor options, municipal code excerpts, proposed cost split with reasoning, and space for both parties to initial. Includes a QR code linking back to the live proposal so the neighbor can review digitally. 6. **Neighbor Communication Bridge** Generates suggested language for the initial outreach: a text/email template that's warm, non-accusatory, and frames this as "I did some research to make this easier for both of us" rather than "You owe me money." 7. **Quote Collection Tracker** Both neighbors can log quotes they receive from contractors. The tool averages them and updates the split calculation in real time, so there's no "my guy said $2,000" vs "my guy said $4,000" standoff — all data lives in one transparent place. ## WellSpr.ing Integration Points ### MCP Tools (via POST https://wellspr.ing/mcp, JSON-RPC 2.0) | Tool | Purpose in Fence Line Negotiator | |------|----------------------------------| | `get_businesses` | Query for fencing contractors, handymen, and lumber yards in the user's area. Filter by category keywords like "fence," "fencing contractor," "fence repair." | | `get_business_detail` | Retrieve full details for selected contractors: address, hours, services, reviews if available. | | `reach_number` | Get or generate reach numbers for contractors so users can contact them without exposing personal phone numbers during the quote-gathering phase. | | `ask_ody` | The critical integration. Ask Ody questions like: "What are the fence regulations for [city/county]?" "Does [jurisdiction] have a good neighbor fence law?" "What permits are required for fence replacement at [address]?" "What is the maximum fence height allowed in residential zones in [city]?" | | `get_city_services` | Surface relevant city services: permit office contact info, code enforcement for abandoned properties with derelict fences, mediation services for neighbor disputes. | | `search_civic_services` | Find community mediation programs, legal aid for property disputes, or homeowner assistance programs that might help with fence costs for low-income residents. | | `get_civic_ideas` | Check if others in the community have proposed fence-related civic improvements (shared tool libraries for fence repair, bulk contractor negotiations, etc.). | ### REST Endpoints | Endpoint | Purpose | |----------|---------| | `GET /api/geo/portals?area_code=NNN` | Determine the user's civic portal based on their location, which helps contextualize Ody's responses and ensure contractor results are locally relevant. | | `GET /api/officials` | Surface contact info for city council members or code enforcement supervisors if the user needs to escalate a dispute or clarify an ambiguous regulation. | ### Future Capabilities (Not Yet Live) - **Roadmap: Covenant Commerce payment rails** — Would enable neighbors to split payments directly through the platform, with funds held in escrow until work completion. Currently, the tool provides Venmo/Zelle split instructions as a workaround. - **Roadmap: Contractor ratings/reviews** — Would allow users to submit feedback on contractors after work completion. Currently, display what's available in `get_business_detail` but don't promise a ratings system. - **Roadmap: Permit application integration** — Direct submission to city permit systems. Currently, surface permit requirements and office contacts only. ## Data Model ### `fence_projects` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | initiator_address | string | Address of the person starting the project | | neighbor_address | string | Shared boundary neighbor's address | | fence_length_ft | integer | Estimated or measured length | | fence_type | enum | wood_privacy, chain_link, vinyl, wrought_iron, other | | condition | enum | minor_repair, moderate_repair, full_replacement | | share_token | string | Public URL slug for neighbor to view/edit | | created_at | timestamp | | ### `split_factors` | Field | Type | Notes | |-------|------|-------| | id | uuid | Primary key | | project_id | uuid | FK to fence_projects | | factor_type | string | e.g., "finished_side_faces," "pet_containment," "prior_installation" | | applied_to | enum | initiator, neighbor | | percentage_adjustment | integer | Positive or negative | | agreed_by_both | boolean | Both parties confirmed | ### `contractor_quotes` | Field | Type | Notes | |-------|---