Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Project Ruby: The Explainer SeriesPart 4 of 4
Author’s note: The author submitted an alternative ordinance — The People’s Overlay — to all Columbus City Council members, the city attorney, and the mayor before the June 9, 2026 public hearing, and spoke at that hearing. 706Report.com has covered Project Ruby since its February announcement. Prior coverage is linked throughout this series.
On the morning of June 9, 2026, the Columbus City Council did two things at the same time.
While hundreds of residents stood at the microphone talking about noise and PFAS and 987 acres and what a 600-megawatt load would mean for the community around it, the council also confirmed a new city manager.
That confirmation is where Part 4 begins. Not because it overshadows the overlay debate, but because the person the council placed in that chair will be managing the most consequential phase of Project Ruby: the negotiations that turn the ordinance’s general language into specific, binding commitments. And his institutional history makes that appointment something Columbus residents need to understand clearly.
The Person in the Middle
Who is the new city manager, and why does his history matter for what comes next?
| Tyson Begly | |
|---|---|
| Education | Computer engineering, Auburn University; MBA, Duke University |
| Career | Management and technology consulting (Accenture, Diamond Management); CFO/COO of Delta Data (private equity-backed fintech); CFO of Highline (rural broadband, west Georgia) |
| Columbus civic role | Secretary and Treasurer, Development Authority of Columbus; the body that hosted Project Ruby’s February public unveiling |
| Council appointment | Appointed District 10 seat, 2023, through the political network around Mayor Henderson; stated from the start he would not run for election |
| Audit committee | Appointed chair of city audit committee because of his financial background |
| Investigation | During his tenure, Columbus retained Atlanta law firm Troutman Pepper, led by former U.S. Attorney Charlie Peeler, to investigate a massive backlog in business and alcohol license renewals in the Finance Department. The audit committee, chaired by Begly, received those findings. Those findings later contributed to the city manager’s dismissal. |
| Left council | June 18, 2024 — when Travis Chambers won the District 10 seat, Begly’s appointment naturally expired, as he had said it would |
| Hugley fired | May 27, 2025 — Isaiah Hugley was dismissed as city manager after 20 years. The Troutman Pepper findings were among the contributing factors. Mayor Henderson opposed the firing but had no vote. |
| Begly confirmed city manager | June 9, 2026 — 7-1 vote, same morning as the overlay hearing. Councilor Chambers, who replaced Begly, warned the timing risked “a mismatch from day one”, then voted yes. |
| Starts | July 2026 |
One week later, on June 16, the same day the council adopted the overlay, Isaiah Hugley won the mayoral runoff. He takes office in January 2027. His city manager will be the man who chaired the audit committee that oversaw the investigation that contributed to his firing. The council that dismissed Hugley chose his city manager for him.
That is the institutional ground on which the most consequential phase of Project Ruby will unfold.
One complicating note: Henderson vocally opposed Hugley’s firing, though he was without a vote. That makes the Henderson-Hugley relationship more complex than simply adversarial. Whether the Begly appointment represents a maneuver against the incoming mayor or a genuine institutional continuity decision is something only the next six months will clarify. What is not in dispute is the history.
What Has to Happen Before a Shovel Goes In the Ground
The overlay is a framework, not a permission slip. Everything still requires additional public processes and each one is an opportunity for scrutiny. The rezoning application for the specific Layfield Road parcel hasn’t been filed yet.
What does the path from overlay to construction actually look like?
| Step | What It Requires | Public Opportunity |
|---|---|---|
| 1. Rezoning application filed | Site plan, pre-construction acoustic study, utility availability letters, cooling fluid certification | Public record when filed — watch for it; triggers the formal timeline |
| 2. PAC public hearing | Planning Advisory Commission reviews the application | Formal comment period — a new hearing, separate from the overlay process |
| 3. Council first reading | PAC recommendation forwarded to council | Public hearing; council votes |
| 4. Council second reading | Minimum 30 days after first reading | Public hearing and final vote on applying the overlay to this specific site |
| 5. Development of Regional Impact (DRI) review — runs concurrently | Georgia DRI process administered by the Middle Georgia Regional Commission; triggered by size thresholds met by Project Ruby | Harris County and Talbot County residents have formal standing here — the only mechanism that gives neighbors across the county line a voice |
| 6. Development agreement | Must be executed before any land disturbance permit | No formal public hearings on the terms — political pressure is the leverage |
| 7. Environmental permits | Georgia Environmental Protection Division (EPD), Army Corps of Engineers for wetlands; streams on the parcel feed the Chattahoochee watershed | Independent of the overlay; runs on its own timeline |
| 8. Construction | 2027–2030 projected; 200 MW from Flint Energies beginning 2029; full 600 MW by 2034 |
The DRI step deserves special attention because it has gone almost unmentioned in Columbus’s public debate. Under rules adopted in November 2025 specifically addressing data centers, a facility of 500,000 square feet or more outside the Atlanta region triggers mandatory DRI review. Project Ruby almost certainly meets that threshold. The DRI doesn’t give neighboring counties veto power. Columbus retains final authority. It requires the developer to document water and electricity demand at full buildout, not at single-building startup, and it gives Harris and Talbot county governments a structured mechanism to place their concerns on the formal record before Columbus’s council votes on the rezoning.
Residents of those counties who had no standing in any Columbus proceeding have standing here.
The utility availability letters required at Step 1 will also force the most consequential factual question in the entire process into the public record. Flint Energies currently serves roughly 450–500 megawatts at peak across its entire service territory. Project Ruby requires 600 megawatts at full buildout which is more than the entire city of Columbus uses at peak. That gap has never been resolved in any public forum. The utility letter requires Flint Energies to confirm in writing, after a completed system impact study, that it can actually deliver this load. What that study finds is one of the most significant open questions still ahead.
Three Things the Ordinance Didn’t Fix — That the Development Agreement Still Can
The overlay debate produced real protections: the 500-foot buffer, the PFAS prohibition, the diesel generator ban, the pre-construction acoustic study. Three structural protections that residents argued for throughout the debate were not adopted. All three remain achievable in the development agreement which has to be finalized before a single permit issues.
What’s still on the table, and why does it matter?
| Protection | Why It Matters | Where It Can Be Won |
|---|---|---|
| Minimum revenue guarantee (PILOT — a legally binding annual payment floor) | The $68.7 million annual tax projection is built on AI-era chip prices. Semiconductor values are cyclical. Without a contractual floor, the city’s revenue tracks the market — not a guaranteed number. | Development agreement — negotiated term |
| Site-wide megawatt cap as deed restriction on all 987 acres | Phase 1 covers ~150 acres. The remaining 837 acres are available for future applications under the same overlay. A cap recorded on the deed — requiring a full new rezoning to increase — is the only mechanism that prevents the parcel from becoming the foundation for an expanding campus with progressively less negotiating leverage for the city. | Development agreement — must be demanded specifically as a deed restriction, not just a planning condition |
| Independent legal counsel for Columbus | The city attorney will negotiate a complex, multi-year development agreement against the outside legal specialists of one of the world’s largest technology companies. The developer’s legal budget for this transaction likely exceeds Columbus’s entire annual outside counsel expenditure. The People’s Overlay proposed that the developer fund independent counsel for Columbus as a non-negotiable condition. It didn’t make it into the ordinance. It can still be demanded. | Development agreement — or as a precondition to entering negotiations |
The development agreement must be “reasonably acceptable to the City” before any permit issues. No executed agreement means no construction. That standard what’s reasonably acceptable is the most significant leverage point Columbus has, and it will be determined by whoever is at the negotiating table when the document reaches its final form.
What Begly’s negotiations produce before January, and what posture he takes on these three protections, will determine what Hugley inherits when he walks in.
Questions That Haven’t Been Answered
Before Part 4 closes, it’s worth naming what remains publicly unresolved because these open questions will shape every proceeding that follows.
| Open Question | Status | Why It Matters |
|---|---|---|
| Who is the end user? | Still confidential — unnamed until a permit is filed | Development agreement negotiations will be conducted against a party Columbus cannot yet fully research or prepare for |
| Is the March 4 PAC session legally valid? | Georgia AG complaint filed by Columbus resident Paul Olson; no response as of June 16 | A violation finding wouldn’t necessarily void the overlay, but would place documented procedural questions in the record relevant to any future legal challenge |
| What does the project actually need for water? | Choose Columbus estimate (88K–330K gal/day) has never been officially corrected; comparable hyperscale sites report 2–4 million gal/day at full operation | The utility availability letter will produce the first binding official water demand figure — the gap between the two numbers is consequential for Columbus Water Works capacity planning |
| What happens to the remaining 837 acres? | No site-wide megawatt cap recorded as a deed restriction in the adopted ordinance | Future applications on the same parcel could arrive under the same overlay framework, with less public leverage each time — the Newton County pattern |
What Residents Can Still Do
The overlay debate demonstrated something Columbus residents didn’t necessarily believe at its start: organized, specific, technically grounded public engagement moves a legislative process. The 500-foot buffer, the PFAS prohibition, the diesel generator ban, the pre-construction acoustic study were provisions that appeared in the amended document without public explanation. The connection between what the community argued at two public hearings and what ended up in the final ordinance is not in any official record. However, the provisions are there.
The next phase of this process is longer, less visible, and more consequential than anything that happened at the June 9 and June 16 hearings. Here is where the public still has formal leverage:
| Action | When | Why It Matters |
|---|---|---|
| Monitor for the rezoning application | Now — it hasn’t been filed yet | Filing triggers the formal timeline; it’s a public record when it arrives |
| Engage Hugley’s transition before January | Now — this is the most time-sensitive item | The mayor-elect campaigned on zero environmental impact and complete community benefit; engaging his transition now — not after he takes office — is when those commitments can be shaped into concrete negotiating positions |
| Tell the mayor, city manager, and council what you expect in the development agreement | Now, repeatedly, before January | The PILOT floor, the megawatt cap deed restriction, independent counsel — all still achievable; political pressure is the only public leverage in the negotiation phase |
| Attend the PAC rezoning hearing | After application is filed | New formal comment opportunity on the specific project, not just the framework |
| Attend council rezoning readings | After PAC recommendation | The vote that actually applies the overlay to this parcel |
| Engage the DRI process | Concurrently with rezoning | Harris and Talbot county residents should contact their commissioners now |
The overlay was the starting line. Everything that matters about what actually gets built on those 987 acres on what terms, with what consequences for the people who live near it, is still ahead.
This series was reported and written by 706Report.com. The author submitted an alternative ordinance — The People’s Overlay — to the Columbus City Council in June 2026 and spoke at the June 9 public hearing. Prior Project Ruby reporting from 706Report.com is linked throughout.