Development commission meeting April 20, 2026

Open with transcript & summary →Search this meeting's transcript →

The development commission meeting on April 20, 2026 addressed multiple active development projects and process improvements. The commission recommended rejection of Project Red and Yellow and motioned to reconsider the previously conditional approval of Comanche Circle due to numerous documented deficiencies including missing engineering documentation, incomplete topography and drainage analysis, district boundary issues, and wastewater treatment gaps; Project Panther and Lion were also rejected for inadequate submission materials. The commission also voted to reject Project Panther and Lion and discussed regulatory revisions including revised lot coverage percentages for data centers and the possibility of creating a dedicated data center district. In response to recurring submission deficiencies, the commission voted to establish an advisory council for expert input, formalized application review procedures with defined timelines and incompleteness protocols, and implemented a director email notification protocol to allow simultaneous commission review of concept plans.

• Opening invocation and pledgesThe meeting opened with an invocation and recitations of U.S. and Texas pledges.
• Public comment and minutes approvalNo public citizen comments at large were received, and prior meeting minutes were approved.
• Project Red and Yellow, Comanche Circle, Project Panther and Lion agenda overviewThe development commission discussed four major projects and flagged a process issue for later discussion.
• Project Red and Yellow: developer name deficiencySpeaker identified missing and incorrect developer identification on the concept plan.
• Project Red and Yellow: project name inconsistencyThe applicant used inconsistent project naming on official plans versus mailings to residents.
• Project Red and Yellow: district boundaries not identifiedRequired district boundary identification was missing or incomplete on submitted plans.
• Project Red and Yellow: phasing and topography deficienciesSpeaker identified missing phasing details and failure to show finished topography required for drainage analysis.
• Project Red and Yellow: grading and wastewater facilitiesSpeaker noted missing post-grading details and undisclosed wastewater infrastructure.
• FEMA flood plain verification requiredSpeaker flagged that flood plain review is a necessary component of project review.
• Road grade and topography concernsSpeaker identified steep road grades that may exceed county standards.
• Project Yellow: engineering firm notationSpeaker questioned whether engineering firm notation on Project Yellow plans constitutes proper stamping.
• Relocation of containerized Bitcoin mining unitsSpeaker documented movement of cryptocurrency mining containers between project phases.
• Recommended bases for rejection of Project Red and YellowSpeaker synthesized checklist violations into motion grounds.
• Motion and discussion: rejection recommendation for Project Red and YellowCommission discussed appropriate language for recommendation to Commissioner's Court.
• Comanche Circle: drainage plan default and water acquisition concernsSpeaker outlined multiple deficiencies in Comanche Circle submission related to water and drainage.
• Comanche Circle: detention pond elevation impossibilitySpeaker identified physically impossible detention pond design showing 100-foot elevation change.
• Comanche Circle: district boundaries and rural district purposeSpeaker documented incomplete district boundary identification and conflict with rural district conservation mandate.
• Comanche Circle: concept plan paper size violationPlans submitted on wrong paper size per regulatory requirement.
• Comanche Circle: finished topography and drainage analysisSpeaker reiterated that submitted topography is insufficient for required drainage review.
• Detention pond topographic detail examinationDetailed discussion of elevation markers and drainage features visible on plan.
• Comparison to Sports Monkey precedent and tributary water quality concernsSpeaker referenced prior regulatory action and identified tributary drainage risks.
• Recurring deficiency pattern and Commissioner Court deferenceSpeaker expressed concern that arguments have been repeatedly presented without decisive action.
• Prairie Creek and stormwater discharge concernsMultiple discharge points from data centers and power plants are discharging into Prairie Creek, creating water quality issues that are not fully visible in project documentation.
• Power generation capacity and cooling system specificationsThe projects propose 1.2 gigawatt power generation using air-cooled diesel generators and gas turbines with minimal water requirements.
• Developer credibility on water needs and facility operationsThe development company has not been transparent about true water requirements, and key operational details remain unknown including actual operators and tenant identities.
• Detention pond design and water storage inadequacyDetention ponds are designed to collect excess storm runoff but the plans do not address disposal of accumulated water or frequency of required drainage cycles.
• Missing wastewater treatment documentationWaste water treatment design is insufficient with only a single notation of a treatment plant rather than a comprehensive plan submitted to TCEQ.
• Motion to reconsider Comanche Circle conditional approvalCommission votes to ask the commissioners court to reconsider the Comanche Circle Sailfish project conditional approval for multiple deficiencies.
• Project Panther and Lion submission deficiencies and rejectionCommission votes to reject Project Panther and Project Lion due to inadequate and incomplete documentation exceeding the Comanche Circle deficiencies.
• Lot coverage percentage revisions for data center usesCommission discusses revising lot coverage regulations to 10% for data centers and proposes expanding the rule to battery storage, solar farms, and wind farms.
• Data center district creation possibilityCommission explores whether a dedicated data center district could be created to contain industrial development to specific zones rather than allowing it county-wide.
• Water quality district protections and watershed focusDiscussion focuses on whether district regulations can enforce watershed protection and whether subchapter K limits county ability to regulate land use and density.
• Advisory council formation for expert input and research supportCommission proposes creating an informal advisory council of community members with expertise to provide input on development decisions and research findings.
• Advisory council formation and membershipThe commission discussed creating an advisory council to draw on expert and citizen input for development matters, with a flexible approach to invitations and a formal motion to establish it.
• Project review process discussion and timeline proposalThe commission addressed establishing a formalized process for how projects are received, reviewed, and advanced to commissioners court, with focus on the 30-day statutory window and submission deadlines.
• Concept plan debate and preliminary design reviewCommission members debated whether to eliminate the concept plan requirement, with arguments that it provides preliminary design review but also discussion of requiring more complete applications upfront.
• Processing and incomplete application proceduresThe commission focused on establishing a receipt process with defined dates, 10-day incompleteness review, and procedures to return incomplete applications without conditional approvals.
• Development director correspondence disclaimerCommission noted a court agenda item requiring disclaimers on development department correspondence to clarify that letters are not official acceptance of applications.
• Application submission timing and commissioners court schedulingCommission debated whether to accept applications on specific dates and coordinated scheduling with commissioners court's second and fourth Tuesday meeting schedule.
• State law limitations on submission windows and conflict with chapter 245Commission acknowledged tension between state law (Texas Local Government Code chapter 245) and desire to restrict submission dates, requiring legal review of any proposed process.
• Email notification and concurrent submission to commission and directorCommission agreed that the director of development should email concept plans to commission members simultaneously upon receipt to allow parallel review.
• Motion: director email protocol and commission recommendation timingCommission voted on a motion requiring the director to immediately email concept plans to commissioners and commission members, specifying the 10th business day response deadline.
• Meeting adjournment and commission vacancy announcementThe meeting adjourned and an outstanding commission vacancy was noted regarding a prior member.
• Replacement commissioner soughtThe commission discussed identifying a candidate to replace Tyler Scott on the development commission.
• Meeting conclusion and acknowledgmentsThe meeting was adjourned with thanks to participants.