RAVEN SUBDIVISION — COMMUNITY EVIDENCE AND ENVIRONMENTAL REVIEW
October 14, 2026 • 8:08 p.m. CDT • Version 1.1 — source audit and corrections
Prepared by ChatGPT for Doug Liles.
Basis: applicant narrative, county October 7 staff report and agenda, NWFWMD permitting guidance. Preliminary documentary review; not an independently validated engineering model or a legal opinion.

ADVOCACY RECOMMENDATION — NOT AN EMPIRICAL FINDING
Request a continuance until material contradictions and environmental questions receive written, reviewable answers. If compliance cannot be demonstrated, request denial on the applicable grounds. If approval proceeds, seek enforceable, measurable safeguards. The present evidence does not establish downstream pollution, increased flooding, fraud, or a permanent closure of the entire golf course.

SCOPE AND EVIDENCE
Applicant narrative: approximately 9.6 acres at Troon Drive, currently a range, putting green, training buildings and associated facilities; 22 detached homes and road in Phase I, 24 villas contemplated in Phase II. It describes transferring development rights and converting open space. Source A below.
County agenda names ECAE as applicant and Sandestin Holdings, Sandestin Investments and Sandestin Owners Association as owners. Listing an association is not evidence of a member vote or endorsement. Source B.
The staff report recommended conditional approval but identified unresolved issues. That recommendation is not a final order. The actual vote and latest revisions remain unverified. Source C.
The 84-page consolidated packet (75,032,110 bytes) was subsequently retrieved. Selected narrative, staff, engineering and environmental pages were examined, including visual checks of the date, legal-location and plan-table observations below. The native drainage model has not been rerun; full permit history, public testimony and final approval status remain unverified.

DOCUMENT DIFFERENCES AND TECHNICAL REVIEW QUESTIONS
Source C: pp. 4–7 and review summary.
1. Density donors: Parcel 209 versus Parcels 224A/320.1.
2. Open-space loss: 6.3 versus 9.52 acres.
3. Land-use labels: Rural Residential/Rural Village versus Mixed Use/Coastal Center.
4. Site descriptions: 9.67, 9.6 and 9.52 acres.
5. Scope: conceptual Phase II versus environmental description including villas/clubhouse.
6. Proposed height, setbacks and impervious area are not consistently resolved.
7. Noncompliant review flags coexist with conditional approval recommendation.
8. Floodplain clearance coexists with unresolved stormwater review.
9. Report cites 6,194 cubic feet of floodplain fill and 138,724 cubic feet of added storage.
10. Report allows an ERP or qualifying 10-2 certification.
Items 1–6 involve document differences or incomplete data. Items 7–10 are review context or technical questions, not inherently anomalies. Conditional recommendations can legitimately coexist with outstanding conditions. None establishes misconduct or project-caused flooding or pollution.

WHY EACH ITEM MATTERS — ANALYSIS AND REQUIRED RESOLUTION
1. Density ledger: Obtain signed transfer instruments and the controlling DRI exhibit. Track donor balance, transferred units, recipient balance and prior commitments. Different donor labels may reflect revisions, but an auditor must be able to reproduce the final allocation without double counting.
2. Open space: Require a GIS exhibit and area schedule tying every figure to one plan revision. Separate gross tract area, converted area, qualifying remaining open space and resort-wide compliance. The two figures use different counting assumptions; subtracting them does not measure unpermitted development.
3. Land use: Require staff to correct the labels and cite the controlling map, development order and applicable standards. A template error is plausible. The question is whether the actual analysis used the correct rules.
4. Boundaries: Reconcile gross versus net site area, bridge/access land, phased limits and surveyed boundaries. Minor rounding alone is weak evidence. Boundary differences become material if they alter permit eligibility or compliance calculations.
5. Phase II: Require a clear statement of what approval authorizes and what remains conceptual. Obtain separate and combined buildout assumptions. Do not describe all 46 dwellings as approved.
6. Buildout assumptions: Model the maximum enforceable roof, driveway, road and other hardscape allocation. If final individual-home approvals can exceed the modeled assumptions, the hydrologic analysis may not represent buildout.
7. Review closure: Request each reviewer’s dated sign-off and response matrix, tied to the final plans. Distinguish issues cured before approval from conditions legally deferred to construction permitting.
8. Floodplain versus drainage: Passing one review does not settle the other. Ask which analyses address offsite discharge, downstream capacity and backwater.
9. Storage: Obtain stage-storage tables, surveyed elevations, normal water levels, seasonal groundwater, outlet controls and routing results. Storage volume alone cannot establish protection. Confirm that the two reported volumes describe comparable things and that existing storage is not counted twice.
10. Permit route: Obtain the permit number or actual certification and written agency confirmation of applicability. NWFWMD describes the small-project route as involving less than 10 acres total project area and less than two acres impervious surface, subject to conditions. A 9.6-acre figure alone does not establish eligibility. Ask how connected phases, road/access improvements and ultimate hardscape are counted; do not allege project segmentation without evidence. Source D.

FLOODING — TECHNICAL QUESTIONS FOR AN INDEPENDENT ENGINEER
The following are proposed review tasks, not findings that the design fails.
• Trace the actual drainage network from each project outfall through ponds, pipes, bridges, culverts and receiving waters. Name the final receiving water only after verifying the connection.
• Obtain editable model inputs and outputs, software/version, survey datum, drainage boundaries, soils, infiltration testing, seasonal-high-groundwater data, rainfall inputs and downstream boundary conditions.
• Compare existing and proposed peak flow, runoff volume, maximum water level and inundation duration at every discharge and vulnerable neighboring location. A lower peak can coexist with more volume or longer flooding.
• Check whether a “new” pond occupies existing flood storage and whether groundwater leaves the claimed storage available when needed.
• Include offsite contributing drainage, shared-system capacity and recorded rights to use it. A pipe being present does not prove capacity or authorization.
• Test the applicable regulatory events. Also request transparent resilience sensitivity runs for larger storms, wet antecedent conditions, consecutive storms, high receiving-water levels, restricted outlets, construction-phase runoff and credible equipment failures. Identify which runs are mandatory versus additional requested protection.
• Require an emergency overflow map showing flow paths, low points, neighboring finished floors, road access and safe discharge.
• Compare model behavior with dated resident photos, high-water marks, rainfall records and historical maintenance/complaint records. Record uncertainty and do not treat every historical flood as caused by this proposal.

ESTUARY AND WATER QUALITY — REVIEW AND DESIGN REQUESTS
No verified outfall-to-estuary route or project-specific pollutant export calculation was obtained. Obtain those before making pollution claims.
• Map receiving waters and verify their classifications, impairment listings and applicable basin requirements.
• Require predevelopment and postdevelopment annual nitrogen, phosphorus and suspended-solids estimates using a consistent drainage area, defensible land-use assumptions and documented treatment performance.
• The existing golf practice use may already contribute nutrients. Compare measured or justified existing loads against realistic residential loads; do not assume either land use is cleaner.
• Show treatment during routine storms and the paths taken by overflow or bypass. Show where construction dewatering will discharge and how sediment will be controlled.
• Have the permitting agency identify the applicable stormwater rule edition, any transition/grandfathering basis and project-specific water-quality requirements in writing. Do not assume the DRI’s age determines the applicable standards.
• Consider a treatment train appropriate to site conditions, native buffers, fertilizer limits, irrigation controls and low-impact designs. High groundwater can limit infiltration; require site-specific justification.
• Collect a scientifically designed baseline upstream and downstream of outfalls before disturbance, with rainfall and flow context. Continue paired storm-event monitoring during construction and after occupancy. Parameters, methods, frequency and thresholds should be set by qualified professionals.
• Include quality assurance, laboratory methods and sampling locations. A single turbid sample is not reliable proof of project-caused estuary damage.

PROPOSED CONDITIONS IF THE PROJECT MOVES FORWARD
These are negotiating objectives subject to engineering and legal review, not claims about requirements already imposed.
1. One controlling plan set, density ledger, open-space exhibit and reviewer closure matrix identified in the approval.
2. Independent drainage peer review with written responses to all material comments; a transparent funding arrangement that preserves reviewer independence.
3. Demonstrated compliance with offsite-impact criteria plus any specifically adopted resilience conditions. Define locations, events and numerical tolerances.
4. Enforceable hardscape limits matching the accepted model. Require review before later additions exceed them.
5. A receiving-water protection plan with treatment performance, erosion/dewatering controls, monitoring points and corrective-action procedures.
6. Construction controls in place and inspected before disturbance; staged clearing, stabilization deadlines and documented response to discharge problems.
7. Surveyed as-builts, field verification and engineer certification before the relevant completion/occupancy milestone.
8. A named stormwater operator, inspection schedule, maintenance access, adequate reserve funding and enforceable repair duties.
9. Defined reporting, exceedance response and enforcement procedures within the county/agency’s authority; specify who may suspend work and under what conditions.
10. Future phases or material design changes require the applicable further review and updated cumulative drainage analysis.

COMMUNITY TALKING POINTS
• “Please identify the controlling donor parcels and provide the dated pre- and post-transfer ledger so the public can reproduce the allocation.”
• “Which open-space reduction is correct, and can the public reproduce the resort-wide calculation from the final exhibit?”
• “Please correct the conflicting land-use labels before relying on the staff analysis.”
• “What exactly would this order approve today, and what remains conceptual?”
• “Show the route from the outfalls to the receiving waters and demonstrate that neighboring properties are protected.”
• “Please show peak flow, total volume, maximum water level and flood duration. More storage on paper does not answer all four.”
• “What pollutant-load analysis establishes protection of the actual receiving water?”
• “If approval is recommended, place measurable safeguards and maintenance duties in enforceable conditions.”
• “We request time to review a complete corrected record. If compliance cannot be demonstrated, we ask for denial on the applicable standards.”

RECORDS REQUEST SCOPE
Request the complete MAJ26-000007 file, all versions and revision dates; application and ownership/agent authorizations; controlling DRI orders, amendments and Exhibit E; density transfer instruments and ledger; GIS/open-space calculations; survey and civil plans; drainage reports and native models; soils and groundwater testing; outfall and shared-system easements; environmental assessments; agency applications, certifications and permits; reviewer comments, applicant responses and sign-offs; notice affidavits and supporting materials; public submissions; meeting recordings/minutes; final orders; later revisions.
Request electronic files in the form maintained, with a fee estimate before chargeable work. County and NWFWMD records requests have been sent. Replies have not been verified in this review. The February 11 pre-application file and complete 2024 Biennial Report remain targeted follow-ups; no new request was sent during this accuracy audit.

STATUS AND NEXT DECISIONS
The continuation to October 21 is reported by a secondary summary whose displayed date is inconsistent; verify directly with county planning. Do not confuse an agenda request for approval with an actual approval.
No procedural appeal deadline or standing determination has been verified. Obtain the actual order and ask appropriate counsel to identify the decision-maker, participation requirements, review route and deadlines. Do not assume an ordinary email preserves legal rights.
For Doug’s district role: the staff report records “No comments” from mosquito control dated August 11. That is not evidence of a comprehensive district endorsement of stormwater or water-quality engineering. Source C. Any new district statement should follow the district’s actual authority and process.
Priority: obtain the final current file and independent civil/water-quality review. The defensible immediate position is to withhold approval until the material record is reconciled, then evaluate denial grounds or protective conditions against the governing standards.

SOURCES AND PROVENANCE
A. ECAE applicant narrative, March 20, 2026, 2 pages:
https://walton.civicweb.net/document/540073/
B. Walton County TRC October 7 agenda, item 4:
https://walton.civicweb.net/document/540121/
C. County staff report, October 7, 2026, 13 pages:
https://walton.civicweb.net/document/540072/
D. Northwest Florida Water Management District, Environmental Resource Permits:
https://nwfwater.com/permits/environmental-resource-permits/
E. NWFWMD current rules/reference portal:
https://nwfwater.com/permits/rules-and-references/
F. Secondary meeting-status report, date inconsistency noted:
https://citizenportal.ai/articles/10576286/trc-delays-raven-subdivision-review-after-residents-raise-stormwater-and-notice-concerns
Source A–C materials were cross-checked against the retrieved complete county packet: https://walton.civicweb.net/document/540083/ . No later revision or final approval has been verified. Technical review questions, proposed conditions and talking points are AI-generated analysis. No Daily News article was obtained.
PFAS ADDENDUM — October 14, 2026, 7:27 p.m. CDT
A relevant local source was located: SaveOurBay.net describes Good Samaritan Institute testing of a composite of livers from 13 catfish collected April 16, 2024 at Ditch #10, 240 Osprey Lane. It reports PFOS 66.1 µg/kg and total detected PFAS 96.7 µg/kg. These are liver concentrations, not fillet or water concentrations. The collection location has not been linked hydrologically to Raven. Source: https://saveourbay.net/
The underlying Pace report, Lot ZD17009, completed May 21, 2024, addressed to Doug Liles, was retrieved: https://saveourbay.net/PFAS-Catfish-Report-ZD17009.pdf
Additional audit flags: the receiving-lab summary calls the matrix “Aqueous,” while the subcontractor summary identifies “Tissue.” The laboratory lists 55 entries under EPA 1633 DRAFT; analyte totals can count isomers and other entries differently. The current project website has not been fully audited here. Request written clarification of matrix coding, the analyte list and matrix-specific accreditation. These differences are not evidence that the results are invalid.
A pooled sample is one analytical composite, not 13 independent measurements. It cannot establish prevalence, variability, bay-wide conditions, or exclude an individual fish dominating the result. Do not infer population representativeness without additional sampling support.
Recommended PFAS work: obtain original collection records and chain of custody; verify coordinates and tissue handling; obtain full analytical and QC tables and laboratory interpretation of qualifiers. Trace Raven’s outfalls independently. If the site or its receiving pathway warrants investigation, request baseline water, sediment and groundwater testing and a qualified assessment of whether excavation, dewatering or changed drainage could mobilize contamination. This is a hypothesis to test, not an established impact.
Use tissue-appropriate benchmarks and consistent wet/dry-weight units. Never compare µg/kg liver directly with drinking-water ng/L limits or fillet advisories. No source attribution to Raven or official fish-consumption advisory is established here.
Community wording: “Local fish-tissue testing warrants a careful look at existing contamination. Before disturbance, identify the project’s discharge pathway and determine whether construction or altered drainage could mobilize pollutants. Require appropriate baseline testing and an enforceable response plan where the evidence supports it.”


DOCUMENT TRAIL ADDENDUM — October 14, 2026, 7:59 p.m. CDT
Prepared by ChatGPT for Doug Liles from the county-published 84-page Raven packet.
The staff report records a February 11, 2026 pre-application meeting (packet page 5). The underlying request, tracking number, notes, concept plans and follow-up correspondence have not yet been recovered in this review.
The April 21 allocation letter (packet pages 77–78) proposes 16 units from Parcel 224A and 6 from Parcel 320.1; it cites Exhibit E of the 2024 Sandestin Biennial Report. Obtain the complete controlling report, approval and amendments and reconcile the Parcel 209 reference flagged by county staff. Residential entitlements and wetland mitigation credits are separate accounting systems.
County and district records requests have been sent; responses have not been verified in this review. No state permit boundary or mitigation-credit transaction has been verified as covering the Raven construction footprint.
Future records correspondence: digitalcommons@icloud.com.
The main Raven page now provides the document index, direct source links, parcel identifiers, agency search paths, and found/requested/not-yet-obtained status.
Complete packet: https://walton.civicweb.net/document/540083/

ACCURACY AUDIT — October 14, 2026, 8:08 p.m. CDT
Three additional source differences were visually verified in the complete packet:
• Page 26 master-plan table: 44 total units, including 22 Phase II multifamily units; page 15 narrative: 22 homes plus 24 future villas. Later-phase count and scope remain unresolved.
• Page 53 environmental assessment: survey date December 15, 2026, after the October packet. Staff page 6 refers to an assessment dated January 19, 2026. Seek corrected dates and original field records, not an inference that no survey occurred.
• Page 24 engineering cover: Section 23; pages 15 and 26: Section 26. Confirm legal description and any cover correction.
Permit route: page 26 lists 11.09 acres for the master plan and 6.11 Phase I impervious acres. Staff's alternative 10-2 route (page 4) has stated thresholds below 10 total acres and below 2 impervious acres. Request agency determination; no eligibility or violation is established here.
Favorable evidence: staff recommends conditional approval, reports no outstanding floodplain issues, summarizes no jurisdictional wetlands and no observed contamination, and describes compensatory storage. Those findings must accompany the unresolved engineering questions. Observation is not chemical testing; no model was rerun here.
Sampling provenance: the laboratory report supports sample results; pooling, fish count and collection location are attributed to the Good Samaritan Institute's project account and have not been independently reconstructed here. This is one analytical composite, not 13 independent measurements. No bay-wide prevalence, fish-consumption conclusion or Raven source attribution follows.
Method and limits: preliminary selected-document comparison, AI-assisted; not peer reviewed, a complete permit/title search, engineering certification or a field study. Newly reported visual differences may be clerical or revision-related. Seek agency/applicant responses and retain corrected versions.
Source register: https://protect30a.org/raven/source-register.json