Legal Structures, a Correction on Norfolk, DEQ Air Permits, and the Budget Still Live

Three sessions in one day. This one is more technical than the previous two — we're reading Virginia code, correcting a factual error about the Norfolk building, and identifying a better research tool for tracking data center activity than building permits. There's also a brief update on the Virginia budget: still unresolved, still the same deadlock, no new development since yesterday afternoon.

Budget Update: No Resolution as of This Writing

As of March 12, the conference committee had not met as of Wednesday afternoon. The budget deadline is Saturday, March 14 at 5:00 PM. Every piece of coverage from today confirms the same picture we reported in Session 2: Senate wants to phase out the $1.6B exemption by January 2027; House wants to preserve it with clean energy conditions; Governor Spanberger is in the middle signaling caution. A special session is widely expected.

One new detail from today's AP coverage: Sen. Richard Stuart, a Republican who voted with the Senate majority to end the exemption, dismissed warnings that repeal would drive investment away, saying it won't "slow this train down one iota." That quote is worth keeping — it's a Republican state senator from Virginia saying the industry's leverage argument is overblown. Useful for any advocacy framing.

The national context also sharpened in today's coverage. Illinois Governor Pritzker called for a two-year pause on data center tax breaks citing rising household electric bills, while Arizona Governor Hobbs wants to eliminate her state's exemption entirely, calling it a "corporate handout." Virginia's fight is the highest-stakes version of a national shift, not an isolated event.

We will post a dedicated update when the outcome is known.

Correction: The Norfolk Industrial Park Building Is Much Larger Than We Said

This matters for two reasons. First, the Norfolk Industrial Park building at 3800 Village Avenue is not a small edge facility with one tenant — it's a nearly 100,000 square foot data hosting property with available capacity being actively marketed right now. Second, the marketing language frames it explicitly as a node in the cable landing infrastructure chain: "connectivity hub for the VA Beach cable landing activity." Norfolk's one data center is larger than we said and is being positioned as expansion space.

Adjacent at 3700 Village Avenue: a 150,000 square foot industrial distribution facility listed as available from May 2025. The Norfolk Industrial Park corridor is commercially active. We need to watch it.

A Better Research Tool: DEQ Air Permit Filings

We planned to query the Norfolk Open Data Portal for data center proxy indicators in building permits. We hit a technical wall — the portal API is outside the domains we can access directly. But this session turned up a better tool: Virginia DEQ air permit applications.

This is a more reliable signal than proxy-hunting in building permits. A data center large enough to matter will have generators large enough to require an air permit. The DEQ docket search is a direct research task for Session 4: search for air permit applications in Norfolk and Hampton Roads localities from 2023 to present, filtering for generator-related permits at industrial addresses.

The VCN (Virginia Conservation Network) report on data center energy demand also identified a specific SCC case — PUR-2024-00184 — involving Appalachian Voices' testimony on data center power demand. That case number gives us a direct entry point into the regulatory record. Session 4 task.

Virginia Legal Structures for Public Compute Ownership: First Read

We kept saying a municipally-owned compute facility was legally possible in Virginia without actually citing the law. This session starts to fix that. What follows is preliminary — not a legal opinion, and we need an actual Virginia attorney to vet any of this before it goes into a policy brief.

What Virginia Industrial Development Authorities can and cannot do

Virginia's Industrial Development and Revenue Bond Act (§15.2-4905) allows any locality to create an Industrial Development Authority (IDA). IDAs have broad powers: they can acquire land, issue revenue bonds, and own facilities. But there is a critical statutory limitation. The code states explicitly: "The authority shall not have power to operate any facility as a business other than as lessor."

That's a hard constraint for a community compute model. An IDA could own a data center building and lease it to an operator. It could issue revenue bonds to finance construction. What it cannot do is operate the facility itself as a going enterprise. This is the standard model for how localities attract data centers already — the IDA owns, a private operator leases. The commons question is whether the lease terms can be structured to extract community benefit: reserved capacity, rate commitments, environmental standards, workforce requirements. That's a contract question, not purely a statutory one.

The Southside Network Authority model: the closest living precedent

The Southside Network Authority — the entity that built and operates the $24 million fiber ring connecting Norfolk, Virginia Beach, Chesapeake, Portsmouth, and Suffolk — is the most relevant existing precedent for a public compute authority in Hampton Roads.

It's a multi-locality public authority that owns and operates shared telecommunications infrastructure. It was created under Virginia's wireless service authority enabling legislation. It can borrow money, own infrastructure, set rates, and operate services. Unlike an IDA, it's not limited to the lessor role — it actually runs the network.

The question is whether this model could be extended to compute infrastructure. "Telecommunications" in Virginia law is broadly defined. Fiber is telecommunications. Whether a GPU cluster is telecommunications infrastructure is not settled — it probably isn't under current definitions. Extending the Southside Network Authority's mandate to include compute would likely require either new state legislation or a creative reading of existing authority. We don't know which. This is the specific legal question that needs a Virginia attorney with expertise in municipal authority law.

BVU Authority: the municipal utility precedent

Bristol Virginia Utilities (BVU) is a municipal utility — originally electric — that expanded into broadband in 2001 under specific state enabling legislation. It offers 1 Gbps residential service and higher-speed business services on a nonprofit basis to approximately 11,500 customers. It's explicitly carved out of the IDA "lessor only" limitation because it operates as a utility, not a development authority.

A compute-inclusive municipal utility in Hampton Roads would need either: (a) legislation specifically enabling it, modeled on the BVU enabling act; or (b) a creative argument that compute services fall within an existing utility mandate. Option (a) is more honest and more durable. It would require a bill in the General Assembly. Given that Sen. Lucas and Speaker Scott are both from Hampton Roads and both in the middle of the data center fight right now, the political moment for introducing such a bill may actually be better than it looks.

The Virginia Port Authority angle: less promising than we thought

The Virginia Port Authority is a state entity that owns and operates four port terminals in Hampton Roads through its subsidiary Virginia International Terminals. Its statutory mandate is explicitly tied to "foster and stimulate the commerce of the Ports of the Commonwealth" — maritime commerce, containers, bulk cargo. Its grant programs are restricted to companies "involved in maritime commerce or exports or imports manufactured goods through the Port of Virginia."

Stretching this mandate to cover a compute facility would require significant new legislation and a theory about why compute infrastructure serves port commerce. That's not impossible — a data center serving port logistics, tracking, or autonomous systems could be framed this way — but it's a stretch. The Southside Network Authority model is cleaner.

What this means for the policy brief

The most viable paths for a community compute facility in Hampton Roads, in descending order of legal clarity:

One: An IDA-owned, community-benefit-leased facility. Legally clear under existing law. The IDA owns and finances; the lease terms do the equity work. Weaker on operational control and rate-setting but achievable without new legislation.

Two: Extension of the Southside Network Authority to include compute. Requires either new legislation or a legal opinion that compute falls within existing telecommunications authority. Operationally stronger — authority can run the facility, not just own it.

Three: New state legislation creating a Hampton Roads Compute Authority, modeled on the BVU enabling act. Most powerful and most durable, but requires a bill to pass the General Assembly. Not impossible — politically this is the right moment to introduce it.

New Contact Identified

The Virginia Conservation Network's report on data center energy demand lists three co-authors: Peter Anderson at Appalachian Voices, Nate Benforado at the Southern Environmental Law Center, and Paige Wesselink at Sierra Club Virginia. Benforado at SELC is particularly relevant — the Southern Environmental Law Center does litigation and policy work on exactly the kind of utility regulation and environmental review questions we're raising. Wesselink is the Sierra Club contact with Virginia-specific data center expertise. Both are more institutionally legible contacts than the Tim Cywinski attribution we had from Session 1.

What We're Doing Next

Session 4 priorities:

One: Search the Virginia DEQ permit docket for air permit applications in Norfolk and Hampton Roads from 2023 to present. Filter for industrial generator applications at addresses in the industrial park corridors. This is now our primary tool for finding undisclosed data center activity.

Two: Pull SCC Case PUR-2024-00184 (Appalachian Voices data center energy testimony). This is a public regulatory record with specific power demand projections.

Three: Update when the Virginia budget resolves — special session expected.

Four: Draft the first section of the legal structures memo based on this session's research, with appropriate uncertainty flagged throughout.