# MiroFish Simulation: Heritage/Homestead Timeline and Blockers Date: 2026-06-09 Tool run: - MiroFish project: `proj_129c4e6afa38` - Graph: `mirofish_7ff72ab926ff418e` - Simulation: `sim_39f634c5d344` - Report: `report_86dbbe0c34e1` - Model path: DeepSeek via the MiroFish local wrapper - Raw local report: `tools/mirofish/upstream/backend/uploads/reports/report_86dbbe0c34e1/full_report.md` ## Simulation Question Simulate stakeholder reactions to Heritage/Homestead pushing through a legally durable, financeable water-authority path for phase-one subdivision. Estimate realistic timeline ranges and likely blockers using the latest seed facts. Rank blockers by probability/severity and identify first-30-day proof items that keep the plan in a 10-12 month lane versus sliding to 18-24+ months. ## Bottom Line The simulation says the 10-12 month lane is possible only if the first 30-60 days convert the water path from a concept into written, bankable authority proof. The critical issue is not whether a physical connection could be built. The critical issue is whether Waco, Chalk Bluff, Ross, McLennan County, title, lender, and counsel can all see the same written authority chain. The most realistic planning range from the simulation is: - Fast lane: 10-12 months, but only if Waco's posture is reduced quickly to signed service, consent/no-protest, release, refusal/non-service, or service-area-agreement language, and the title/lender proof package is acceptable. - Good-normal lane: 12-18 months if Waco does not formally fight but takes time, if Chalk Bluff remains a fallback/comparator, and if county/title/lender proof has to be revised. - Bad lane: 18-24+ months if Waco silently delays, protests, or forces the path into a contested CCN/service-area process; or if Chalk Bluff's `Facilities +200 Feet` status cannot support bankable service proof. The main MiroFish finding: legal certainty comes before engineering feasibility. Cost estimates and construction calendars do not lock the subdivision timeline unless the service authority is written in a form that county, title, lender, counsel, and the relevant utility parties will accept. ## Verified Seed Facts Used - Waco is the mapped water/sewer CCN holder for the relevant area in the current working facts. - Chalk Bluff's water CCN appears as `Facilities +200 Feet`, not a broad bounded service area. - No issued Heritage/Homestead/Halbert water CCN has been identified in the current TXSP/PUC working checks. - 2026-06-10 update: a Water Engineers proposed Homestead Heritage water CCN map exhibit has been recovered. It is prior-work-product evidence, not issued-CCN proof. The signed Waco agreement reportedly held by Bro. Dadi Lev-Cochav is now the next proof item. - Heritage has active PWS material around `TX1550143`, but a PWS record does not by itself solve subdivision/title/lender service-authority proof. - Existing strategy is Heritage-controlled WSC or similar local-control path, with Chalk Bluff as a serious fallback/provider comparator rather than a blind permanent sale. - The June 7 timeline reality check frames 10-12 months as a narrow clean lane; 12-18 months as a good-normal range; and 18-24+ months as likely if the path becomes broad, deficient, or contested. ## Ranked Blockers 1. Waco silent delay - Simulated probability/severity: highest. - Delay effect: 4-6 months by itself; more if it causes second-order disputes. - Why it matters: Waco can avoid giving a clean yes/no while repeatedly requesting more information. That drains the first 30-60 day window without producing the written proof needed by county/title/lender. 2. Waco or another party formally challenges the path - Simulated probability/severity: very high. - Delay effect: 6-12 months, with a realistic path to 18-24+ months if it becomes a contested CCN/service-area fight. - Why it matters: a formal protest or challenge can turn a practical service solution into an administrative/legal proceeding. 3. Bankable written service-authority proof fails - Simulated probability/severity: medium-high. - Delay effect: 2-3 months for revision, but can reset the path if the defect is substantive. - Why it matters: county approval, title acceptance, lender comfort, and lot conveyance all need written proof that is more durable than a quote, oral statement, meeting note, or informal intent letter. 4. Chalk Bluff boundary/authority proof is insufficient - Simulated probability/severity: medium-high. - Delay effect: about 3-6 months if it requires clarification or fallback redesign. - Why it matters: the 6-9 month Chalk Bluff physical path does not equal a 6-9 month legal/financeable subdivision path. `Facilities +200 Feet` has to be tested against the exact lots and the exact proof format. 5. Ross or adjacent service-area edge questions surface late - Simulated probability/severity: medium. - Delay effect: roughly 4+ months if it becomes a formal boundary or notice/protest issue. - Why it matters: edge questions are dangerous when they show up after money has already been spent on a preferred path. 6. Heritage internal alignment/cost allocation dispute - Simulated probability/severity: medium. - Delay effect: 2-4 months. - Why it matters: uncertainty creates internal pressure. If stakeholders split between own-system, Waco, and Chalk Bluff paths, the external clock keeps running while the internal decision stalls. 7. Engineering, construction, supply, and field conditions - Simulated probability/severity: lower as primary blockers. - Delay effect: 1-3 months unless combined with one of the legal/proof blockers above. - Why it matters: these matter, but the simulation did not treat them as the controlling risk. The controlling risk is authority proof. ## First 30-Day Proof Package To keep the 10-12 month lane alive, the simulation says the first 30 days should produce or tee up these items: 1. Service-area authority map packet - Current Waco water/sewer CCN map evidence. - Chalk Bluff `Facilities +200 Feet` evidence. - Ross/adjoining service-area edge check. - Heritage/Homestead/Halbert no-issued-CCN check. - A plain-English boundary memo separating verified map facts from legal inference. 2. Waco response-trigger package - A formal written request that gives Waco structured response options: serve, consent/no-protest, release, refuse/non-serve, or negotiate a service-area agreement. - Meeting request and technical exhibit packet. - Counsel-reviewed wording so Heritage does not overpromise or accidentally concede control. 3. Chalk Bluff fallback proof package - Binding-enough service intent or term sheet, not just an informal quote. - Exact service area/lot coverage explanation. - Rate, connection-fee, maintenance, capacity, and timing terms. - Clear statement of what is still subject to TCEQ/PUC/county/title/lender acceptance. 4. County/title/lender acceptance template - Draft proof language that asks title and lender stakeholders what they need before the final path is chosen. - McLennan County-facing service proof checklist. - Separate fields for provider, authority source, maintenance responsibility, life-of-project obligation, and revocation/termination risk. 5. Counsel/engineer/operator alignment memo - Legal authority path. - Engineering feasibility path. - Operator/compliance path. - Cost allocation and asset-transfer assumptions. - Open questions that must be answered before external filings or binding commitments. ## Timeline Gates Day 0-30: - Build the proof packet. - Trigger Waco's written posture. - Validate Chalk Bluff as fallback/comparator. - Get title/lender/county proof-format expectations before locking language. Day 30-60: - If Waco gives a usable written path, move to service-area agreement / no-protest / release / service terms. - If Waco refuses or imposes unacceptable terms, shift to the Chalk Bluff or Heritage-controlled alternative with the written reason preserved. - If Waco is silent, treat that as an active blocker, not neutral waiting. Day 60-120: - Convert the chosen path into counsel-reviewed documents, engineering support, operator/FMT proof, county-facing proof, and financeable closing evidence. - Avoid spending heavily on construction design until the authority chain is clear enough to survive county/title/lender review. After Day 120: - The path should be in execution mode only if authority proof is in writing. - If authority proof is still unsettled, the project is likely in the 12-18 or 18-24+ month lane, even if the engineering scope looks simple. ## MiroFish Run Limitation The raw MiroFish social-action stream was shallow: it produced only a small number of initial synthetic posts and had agent-assignment warnings. The stronger output came from the MiroFish report agent, which used the generated graph, stakeholder profiles, graph searches, and simulated interviews to produce the timeline/blocker report. Treat the percentages as simulation estimates, not verified public-record probabilities. The strategic pattern is still useful: first-tier blockers are Waco posture and bankable written authority proof; engineering/construction is secondary until those are solved. ## Actionable Takeaway The next operating move is not "pick Waco or Chalk Bluff" in the abstract. The next move is to force the proof question into writing: - What exact document will Waco sign or refuse to sign? - What exact document can Chalk Bluff sign, and does it cover the lots? - What exact language will McLennan County, title, lender, counsel, and the engineer accept? If those answers are gathered in the first 30-60 days, the 10-12 month lane remains alive. If they remain oral, ambiguous, or conditional after day 60, the practical timeline should be managed as 12-18 months, with 18-24+ months as the risk case.