Get the Weekly Signal
Named pattern · candidate · Signal 71

The Water Gate

In a thirty-day window two corpus cities sixty miles apart welded a hard water-and-power ceiling into their land-development code against hyperscale data centers — before any data-center application exists in the corpus. Minneola Ordinance 2026-05 Draft A (the P&Z draft, June 1, 2026) caps a data center at 5 MW of provider power, 50,000 gallons per day of reclaimed water only with a 25% reuse-retention floor, a 10,000-square-foot building, and mandatory closed-loop cooling. Winter Garden Ordinance 26-16 (adopted 6-0, May 4, 2026) welds an ERU water-consumption threshold into I-1/I-2 use entitlement that triggers a mandatory Special Exception. These are the corpus's first pre-emptive exclusion code — arithmetic set below viability, set to exclude a use rather than channel it. Minneola's 50,000 gpd matches the figure Fort Meade's $2.6B / 1.2-gigawatt Polk County hyperscaler conceded, then made stricter, reclaimed-only; its 5 MW cap is roughly one two-hundred-fortieth of that 1.2 GW. The corridor codes against a wave still sixty miles south, pinned to a real neighbor's conceded number.

Exhibits
2
Direction
rising
Horizon
90-day propagation window (closes ~2026-08-30)
Confidence
high
Named
2026-06-04

The pattern

A jurisdiction welds a hard water-consumption or power ceiling into its use code before any applicant exists, against a water-and-power-intensive use class, set at arithmetic below viability — to exclude the use rather than channel it. The instrument varies. The mechanism is identical: the corridor codes against a wave it can see approaching but that has not yet arrived, and it pins the ceiling to a number a real neighbor has already conceded.

This is the corpus's first documented case of pre-emptive exclusion. The two cardinal exhibits cluster sixty miles apart along the corridor, within a thirty-day window, neither holding a local data-center application.

ExhibitDateInstrumentVote / statusCeiling
Minneola Ord 2026-05, Draft AJune 1, 2026Use-class hard cap (Special Exception in I-1, prohibited in B-1)Two-draft packet; staff recommends approval5 MW power · 50,000 gpd reclaimed-only · 25% reuse-retention · 10,000-sf / 1-acre · 2,500-ft separation · mandatory closed-loop cooling
Winter Garden Ord 26-16May 4, 2026ERU water-consumption threshold (mandatory Special Exception in I-1/I-2)Adopted 6-0ERU threshold — function-blind, catches any water-intensive industrial use

Minneola names the use; Winter Garden names the resource draw. Two surfaces, one anxiety — water-and-power load the aquifer and grid cannot absorb. The corpus documented this two-cities-two-surfaces structure once before, for recovery residences; the Water Gate generalizes it to a new use class and inverts its purpose.

How the pattern reads

The Water Gate is not a tuning detail in an industrial use table. It is a deliberate constraint regime installed ahead of demand, and it follows a precise logic that competent observers can read.

  1. The ceiling is set below the floor of viability. A hyperscale data center's minimum viable scale is 50-100+ MW (the largest run past 650 MW). Minneola Draft A caps provider power at 5 MW — roughly one two-hundred-fortieth of Fort Meade's 1.2 GW, and twentyfold below SB 484's own 100-MW "large-scale" line. Draft A does not regulate hyperscale; it zones it out. Draft B (performance-based, with utility-impact analysis and a development-agreement path) is "here, on our terms." The two-draft packet is a genuine in-or-out fork.

  2. The number is borrowed from a real, conceded figure. Fort Meade's developer cut projected water from 150,000 to 50,000 gpd after committing to closed-loop cooling. Minneola Draft A caps water at exactly 50,000 gpd — reclaimed-only, with a 25% reuse-retention floor and mandatory closed-loop cooling. The corridor watched its neighbor, took the figure the hyperscaler had already agreed to, and made it the ceiling. The number arrives pre-negotiated; a developer arguing it is infeasible argues against a number one of its own already accepted sixty miles south.

  3. The code runs ahead of the statute, not behind it. Florida SB 484 (Chapter 2026-65) was signed May 7, 2026 and takes effect July 1, 2026. It prohibits consumptive water-use permits to large-scale data centers, mandates reclaimed water, bars utilities from passing data-center costs to residential ratepayers, and explicitly preserves local authority to reject data centers. Minneola translated a 25-day-old statute into draft code text. Winter Garden moved three days before the bill was signed. The precoding clock runs on legislation, not applications.

  4. The state hands the authority back — selectively. SB 484 is the inverse of SB 180. Where SB 180 strips local authority over general development and freezes more-restrictive code to June 30, 2028, SB 484 hands local authority back on the single use class the state shares the cities' fear of — Florida Commerce Secretary J. Alex Kelly called Fort Meade "fundamentally flawed." The state's posture is use-class-specific, not monolithic. Water-and-grid draw is where Tallahassee and the corridor align even as they clash everywhere else. The cities are exercising the grant immediately, before the first applicant.

  5. The wave is visible but not local. No data-center application exists anywhere in the corpus. The proximate threat is Fort Meade in Polk — a corpus-adjacent county feeding the Davenport and Haines City service area — approved April 15, 2026 with 40 of 41 public commenters opposed and the commission voting unanimously to approve. The cautionary tale runs further: DeSoto County's 1,300-acre complex drew enough backlash that Erin Brockovich set up a statewide AI-data-center tracking map. The corridor is building the wall while the water is still abstract.

Precode-to-exclude versus precode-to-channel

The Water Gate is the same family as recovery-residences-regulatory-precoding — both write the rulebook for a use class before any applicant arrives — and its opposite in purpose.

Precode-to-channelPrecode-to-exclude
PatternRecovery Residences Regulatory Pre-codingThe Water Gate
Use classFederally protected (Fair Housing Act / SB 954)Market-driven, high-draw (hyperscale data centers)
PurposeRoute a protected use through orderly local procedureSet arithmetic below viability so the use does not file
SurfaceLowest-visibility administrative review (Director decides)Hard caps and separation in the use table itself
Statutory postureComply on the protected dimension; reserve life-safety enforcementExercise the rejection authority a statute just confirmed
OutcomeThe use arrives, channeledThe best outcome is the application that never files

The recovery-residence precoding channels a use the city cannot lawfully refuse. The Water Gate excludes one it can — by building a ceiling no viable applicant can clear. Withdrawn and canceled projects elsewhere (St. Lucie's Sentinel Grove, February 2026; Okeechobee's Okee-One, April 2026) suggest the exclusion may work by deterrence: the wall is most effective when no one tests it.

What's next for this pattern

The pattern is at candidate stage — two exhibits, one cycle. The Pattern Atlas will track whether it consolidates:

  • Which Minneola draft the board recommends and Council adopts. Draft A (exclusion) versus Draft B (performance-admission) is the leading indicator for whether the corridor participates in the Florida data-center wave at all. Tracked in watch minneola-data-center-draft-choice.
  • Whether a third corpus city files a parallel water-or-power gate inside the 90-day window (closes ~2026-08-30). Two cities is a cluster; three resolves data-center-cross-corpus-propagation toward confirmed.
  • Whether the instrument generalizes past data centers. Winter Garden's ERU threshold is already function-blind — it catches cold storage, beverage processing, any water-intensive industrial form. The use-named version (Minneola) and the draw-named version (Winter Garden) may converge on the draw-named instrument as the more durable one.
  • Whether the SB 180 exposure draws a challenge. The exclusion gate is a land-development regulation adopted into the active freeze that runs to June 30, 2028. SB 484 confirms the data-center authority; it does not insulate the ordinance from SB 180's more-restrictive standard. Two SB 180 suits are pending statewide with no injunction.

Related patterns and entities

The Water Gate composes with the corpus's broader reading of the corridor's constraint regime change:

  • The Quiet Revolution on Highway 27 — South Lake's municipal regulatory rebuild. The Water Gate is the rebuild reaching a new use class: the corridor that spent a decade pricing entitlements against the road is now pricing them against the water, and writing the water ceiling into permanent land-use architecture.
  • Recovery Residences Regulatory Pre-coding — the precode-to-channel sibling. Both write code ahead of the applicant; the Water Gate inverts the purpose from accommodation to exclusion.
  • The Grandfather Window — codes adopted before the SB 180 retroactive line carry protection that later codes lack. The Water Gate adopts into the freeze, accepting challengeability through mid-2028; its durability is a live question, not a settled one.
  • Minneola and Winter Garden place dossiers — the two cardinal jurisdictions; Minneola on the US-27 South Lake axis, Winter Garden on the SR-429 Western Beltway, the gate appearing on both corridors in the same window.

For developers and their counsel structuring high-draw industrial entitlements along the corridor: read the ceiling before the use table. A 5 MW cap against a 50-100+ MW use is exclusion codified, and SB 484 confirms the local authority behind it. The performance-based draft (Minneola Draft B) is the negotiable path; the hard-cap draft is the closed door.

For city counsel weighing a parallel gate: the exclusion arrives pre-litigated when it is pinned to a neighbor's conceded figure, but it adopts into an active SB 180 freeze. The data-center authority SB 484 grants does not cure the more-restrictive exposure on the rest of the code. The function-blind draw threshold (Winter Garden) captures use classes the table cannot yet name; the use-named cap (Minneola) is sharper against the one threat in view.

Exhibits inventory

2 detected instances

Defensive responses

How the field responds when this pattern is detected

  • Cities translating a fresh enabling statute into use-code text within weeks — Minneola codified a 25-day-old SB 484; Winter Garden moved three days before the bill was signed. The precoding clock now runs on statutes, not applicants.
  • Pinning the local ceiling to a verified neighboring concession — Minneola's 50,000 gpd reclaimed-only is Fort Meade's own conceded figure, made stricter. The number arrives pre-litigated because a real hyperscaler already agreed to it.
  • Issuing the in-or-out fork as competing drafts (Minneola Draft A exclusion vs. Draft B performance-admission) so the board adjudicates posture once, not applicant-by-applicant.
  • Naming the resource draw rather than the use (Winter Garden's ERU threshold) to capture future water-intensive classes the use table cannot yet name — cold storage, beverage processing, the next high-draw industrial form.
  • For developer counsel: a 5 MW cap against a use class whose minimum viable scale is 50-100+ MW is exclusion dressed as standards. SB 484 confirms the local authority to reject outright; the draft is the rejection, codified.
  • For city counsel: the exclusion gate adopts INTO an active, fully-enforceable SB 180 freeze that runs to June 30, 2028 — every post-August-2024 land-development regulation is challengeable as more-restrictive. The SB 484 grant of data-center authority does not cure SB 180 exposure on the rest of the code.
Briefs analyzing this pattern
Detected in
Provenance trail
Citation anchors — 9 stable references on this page

Each claim below is a citation-stable reference. Pin to the slug for stability across rewordings. Available as HTML data-claim-id attributes, JSON-LD Claim nodes, and the claims[] array in every describe_* MCP response.

  • the-water-gate.voxel_lead.thirty-day-window-two · voxel_lead

    In a thirty-day window two corpus cities sixty miles apart welded a hard water-and-power ceiling into their land-development code against hyperscale data centers — before any data-center application exists in the corpus. Minneola Ordinance 2026-05 Draft A (the P&Z draft, June 1, 2026) caps a data center at 5 MW of provider power, 50,000 gallons per day of reclaimed water only with a 25% reuse-retention floor, a 10,000-square-foot building, and mandatory closed-loop cooling. Winter Garden Ordinance 26-16 (adopted 6-0, May 4, 2026) welds an ERU water-consumption threshold into I-1/I-2 use entitlement that triggers a mandatory Special Exception. These are the corpus's first pre-emptive exclusion code — arithmetic set below viability, set to exclude a use rather than channel it. Minneola's 50,000 gpd matches the figure Fort Meade's $2.6B / 1.2-gigawatt Polk County hyperscaler conceded, then made stricter, reclaimed-only; its 5 MW cap is roughly one two-hundred-fortieth of that 1.2 GW. The corridor codes against a wave still sixty miles south, pinned to a real neighbor's conceded number.

  • the-water-gate.exhibit.minneola-ord-2026-05 · exhibit

    Minneola Ord 2026-05 — corpus's first explicit data-center text amendment. Adds Data Centers as a Special Exception in I-1, prohibits them in B-1, carries two competing drafts. Draft A (P&Z, exclusion-by-arithmetic): 5 MW provider-power cap, 50,000 gpd reclaimed-water-only with 25% reuse-retention floor, 10,000-sf / 35-ft / 1-acre maximum, 2,500-ft separation, mandatory direct-to-chip or immersion cooling, EMF shielding. Draft B (performance-based admission): 500-ft setbacks, utility-impact analysis with denial authority, Ch 163 development-agreement option. The two-draft packet is a genuine in-or-out policy fork. Draft A's 50,000 gpd matches the figure Fort Meade's hyperscaler conceded; the 5 MW cap is ~1/240th of Fort Meade's 1.2 GW.

  • the-water-gate.exhibit.winter-garden-ord-26 · exhibit

    Winter Garden Ord 26-16 — welds an ERU water-consumption threshold into I-1/I-2 use entitlement; any use exceeding the threshold triggers a mandatory Special Exception Permit. Function-blind: catches data centers, cold storage, beverage processing, any water-intensive industrial. Adopted 6-0, three days before SB 484 was signed. Names the resource draw rather than the use — a different instrument reaching the same anxiety.

  • the-water-gate.defensive_response.cities-translating-fresh-enabling · defensive_response

    Cities translating a fresh enabling statute into use-code text within weeks — Minneola codified a 25-day-old SB 484; Winter Garden moved three days before the bill was signed. The precoding clock now runs on statutes, not applicants.

  • the-water-gate.defensive_response.pinning-local-ceiling-verified · defensive_response

    Pinning the local ceiling to a verified neighboring concession — Minneola's 50,000 gpd reclaimed-only is Fort Meade's own conceded figure, made stricter. The number arrives pre-litigated because a real hyperscaler already agreed to it.

  • the-water-gate.defensive_response.issuing-out-fork-competing · defensive_response

    Issuing the in-or-out fork as competing drafts (Minneola Draft A exclusion vs. Draft B performance-admission) so the board adjudicates posture once, not applicant-by-applicant.

  • the-water-gate.defensive_response.naming-resource-draw-rather · defensive_response

    Naming the resource draw rather than the use (Winter Garden's ERU threshold) to capture future water-intensive classes the use table cannot yet name — cold storage, beverage processing, the next high-draw industrial form.

  • the-water-gate.defensive_response.developer-counsel-5-mw · defensive_response

    For developer counsel: a 5 MW cap against a use class whose minimum viable scale is 50-100+ MW is exclusion dressed as standards. SB 484 confirms the local authority to reject outright; the draft is the rejection, codified.

  • the-water-gate.defensive_response.city-counsel-exclusion-gate · defensive_response

    For city counsel: the exclusion gate adopts INTO an active, fully-enforceable SB 180 freeze that runs to June 30, 2028 — every post-August-2024 land-development regulation is challengeable as more-restrictive. The SB 484 grant of data-center authority does not cure SB 180 exposure on the rest of the code.