The Race — Building Democracy in the Age of AI. People race toward a shared finish line.
The Race
← October 2026 overview

OCTOBER 2026 · LANE 01

Governance and Regulation

Who writes the rules—and who can challenge decisions?

Provisional · Evidence through October 31, 8:30 a.m. MDT · Updated November 1, 2026

Direction of power
Mixed-contested
Window
Preserves; bounded openings
Confidence
Moderate
Movement since September
Public and worker remedies deepen; federal clinical-AI information duties retreat

October assessment

October makes the allocation of authority more explicit. The UK Information Commissioner’s supervision and agents consultation, the judiciary’s human-accountability requirements, Italy’s employment-decision remedies, New York’s adopted restrictions on companion features for minors, and Pflugerville’s elected technology oversight all create identifiable constraints or decision points. These mechanisms build on September’s professional-accountability laws; they do not repeat those earlier awards.

The movement is contested rather than uniformly dispersive. HHS’s final HTI-5 rule removes covered clinical-AI disclosures and predictive-tool risk-management requirements from the certification route beginning December 28. Public purchasers will have less standardized evidence through that mechanism. The separate PAIPA sanctions extend state control over AI-related intellectual-property relationships. Ordinary consultation, voluntary principles and advisory bodies remain different from operating remedies.

GSA’s September 28 purchasing clause is an important October implementation development: mandatory use in new covered purchases begins October 19. That is not a second adoption. Existing contracts and state/local transactions are not automatically rewritten. The political-influence review below finds competing networks deploying resources, with causal policy effects still unestablished.

What would change this judgment

Implemented remedies and accessible evidence; final rules after consultations; incorporation of purchasing clauses; actual operation of Pflugerville’s commission and public page; clinical-AI information available after the federal change.

Supporting scored events

Each action retains one event and score across lanes. Dates, jurisdictional limits and unresolved verification remain explicit.

October scored actionPending verification

Inquirer workers ratify contractual AI participation and layoff remedies

2026-10-02 · Dispersion +1 · Secondary lane; primary Lane 8

There is a specific unresolved contradiction: the union says the committee meets every other month, while the newspaper says monthly. The union's contract-download page still supplies a 2023 agreement, not the ratified 2026 text. Ratification is corroborated by the parties, but operative coverage and remedies require the new instrument; the newspaper is also the employer, not independent corroboration of its performance.

Contractual participation, employee consent and described grievance/severance remedies preserve organized worker leverage as AI enters production. Mark approves provisional +1 pending the final agreement; this is neither a veto over all use nor protection from all AI layoffs.

Follow-up: October 8: operative 2026 CBA, coverage, enforcement and exact meeting/remedy clauses. Reconcile union every-other-month and employer monthly descriptions.

Pending verification: Final operative documents remain missing; approval and publication do not resolve this hold.

Read the evidence and sources →

October scored actionPending verification

Michigan’s attorney general challenges the DTE–Google power agreement

2026-10-01 · Dispersion +1 · Secondary lane; primary Lane 3

On October 30, Michigan Attorney General Dana Nessel asked the Public Service Commission to reconsider its October 1 conditional approval of DTE’s twenty-year electricity contracts for Google’s Van Buren Township data center. The filed petition ↗ seeks stronger protections or rejection of the contracts. It is a challenge to an approval, not a ruling overturning it.

The central dispute is how to count costs and benefits. The commission accepted an assessment over the whole contract term; Nessel wants annual accounting and reconciliation. Her petition quotes the order’s expectation of annual net costs to other customers during 2035–2038, while disputing whether projected benefits in other years adequately protect them. She also seeks fuller transmission-cost accounting and removal of a collateral cap. These are contested prospective costs, not measured charges already imposed on households.

Read the evidence and sources →

October scored action

Amazon’s community statement also ends its use of government nondisclosure agreements

2026-10-01/02 (source-date discrepancy retained) · Dispersion +1 · Secondary lane; primary Lane 3

Amazon’s October 1 primary statement says it no longer uses nondisclosure agreements with government agencies working on its projects, will share plans early and host community discussions, and will publish annual energy and water metrics. October 3 reporting highlighted the NDA provision; it was recovered as a distinct qualification in today’s review. An NDA is a contract restricting disclosure. The company statement does not establish that all earlier agreements have been released or that residents have an enforceable remedy if disclosures are incomplete.

This is part of the same statement announcing the already-recorded Built Together community programme. Its promised spending, education and efficiency benefits are not repeated as another new event.

Read the evidence and sources →

October scored action

San Francisco adopts a data-center planning pause

2026-10-06 Board passage · Dispersion +1 · Secondary lane; primary Lane 3

San Francisco’s Board of Supervisors approved a 45-day citywide data-center moratorium on October 6. File 261021, Version 2, was passed by the Board and placed with the mayor; final mayoral completion and commencement are separate follow-up questions. The formal Board action preserves time to develop detailed data-center standards before further commitments. It is not a permanent ban.

The city’s stated planning purpose matters to the assessment. Exact exceptions and any extension depend on the adopted instrument. The award recognizes the Board’s concrete institutional action; it does not assert that every subsequent commencement step is complete.

Read the evidence and sources →

October scored action

Oakland adopts a data-center planning pause

2026-10-06 · Dispersion +1 · Secondary lane; primary Lane 3

Oakland’s City Council separately adopted an urgency data-center measure on October 6. File 27-0050 temporarily blocks new data-center land-use entitlements and related agreements while the city develops specific planning standards. The measure specifies immediate effect upon adoption. It is a temporary planning action, not a permanent ban or a finding that a particular application has been rejected.

Its purpose is to preserve a period in which local government can consider the water, electricity and land-use conditions attached to future developments. Exact project coverage, exemptions and extension provisions remain tied to the final ordinance.

Read the evidence and sources →

October scored action

Manatee County adopts a year-long pause to develop data-center rules

2026-10-08 · Dispersion +1 · Secondary lane; primary Lane 3

On October 8, Florida’s Manatee County commissioners adopted Ordinance 26-42 after its final public hearing. For up to twelve months, the county will stop accepting new data-center-related development applications in its unincorporated territory. The pause covers applications such as building permits, site plans, rezonings and development agreements. It can end earlier if the board repeals it.

The county’s existing land-development code does not specifically define data centers or large-load facilities. Staff will use the pause to recommend where these facilities belong and what rules should govern electricity and water demand, noise, setbacks, buffers and compatibility with neighboring properties. This is a planning pause, with an identified regulatory purpose, rather than a permanent prohibition. The county’s official account confirms adoption; earlier staff directions and planning-commission votes were preliminary steps. County account ↗.

Read the evidence and sources →

October scored action

Raleigh pairs its data-center pause with a public rulemaking timetable

2026-10-06 · Dispersion +1 · Secondary lane; primary Lane 3

Raleigh has published the next steps: a draft for public comment on November 16, planning-commission consideration in December and January, a council public hearing scheduled for March 2, and final action targeted for April 6, 2027, when the moratorium ends. The city says state law prevents an outright ban. Its existing special-use permit process also requires approval when an applicant satisfies the applicable standards, making the standards themselves especially consequential. City FAQ and timetable ↗.

Read the evidence and sources →

October scored action

Britain’s data regulator reports changes by AI developers and opens an agents consultation

2026-10-08 · Dispersion +1 · Primary lane

On October 8, the UK Information Commissioner’s Office (ICO) reported privacy changes secured through its supervision of ten major AI developers: Amazon, Anthropic, Apple, Cohere, DeepSeek, Google, Meta, Microsoft, OpenAI and Stability AI. These are companies developing many models, not ten individual large language models. Some changes are completed; others remain commitments. The work applies existing UK data-protection duties to model training and use, including explaining whose personal data is used, identifying a lawful basis and helping people exercise access and objection rights.

For example, the supervision account documents changes to privacy notices and explanations by Apple, Cohere and OpenAI, and reviews of the justification for using personal data by other developers. On the same day, the ICO opened a public call for evidence on AI agents, which can take actions for users. It closes November 20 and asks about transparency, accountability, security and automated decisions before future guidance and a statutory code. The consultation is open now; the future code is not yet adopted. The underlying data-protection law is compulsory even where firms cooperate without a new enforcement order.

Read the evidence and sources →

October scored action

OPM opens a public, source-traceable chatbot for federal workforce data

2026-10-07 · Dispersion +1 · Secondary lane; primary Lane 6

The Office of Personnel Management launched FWD Chat in its October 7 release; reporting followed October 8. The public beta answers plain-English questions about federal civilian employment, hiring, departures and demographics using official personnel data. Its current page identifies the data as covering August 2026.

A “How was this generated?” panel shows the dataset, measure, filters and time period behind an answer. Users can examine results in the existing Table Builder. OPM warns that answers can contain errors or differ between similar questions, and advises checking important figures. Downloads and API access also exist, but their presence does not establish that new API rights were created in this release. Public service ↗; Official release history ↗.

Read the evidence and sources →

October scored action

Humboldt County adopts a 45-day data-center planning pause

2026-10-06 · Dispersion +1 · Secondary lane; primary Lane 3

Humboldt County's Board of Supervisors passed urgency Ordinance 2794 on October 6, imposing an immediate 45-day pause on covered new data-center authorizations in unincorporated areas while the county develops specific rules. The official legislative record marks the action Passed. The county is addressing energy, water, noise, air impacts and community consequences before new approvals establish development expectations.

Independent reporting from the meeting records a 4–1 vote and a carveout for facilities below 15 megawatts using 100 percent renewable electricity and closed-loop cooling without impacts on county water resources. This was included in the adopted motion, rather than merely suggested for a future ordinance. The certified ordinance attachment remains inaccessible, so its exact exemption wording is still source-qualified. Staff must publish a post-adoption summary within fifteen days; any extension requires a further decision. Official action ↗. Meeting report ↗.

Read the evidence and sources →

October scored action

Anne Arundel’s certified bill now establishes a November 26 commencement date

2026-10-05 passage; November 26 commencement · Dispersion +1 · Secondary lane; primary Lane 3

The current certified copy of Anne Arundel County’s Bill 63-26 prints November 26, 2026 as its effective date. The county’s docket retains October 5 unanimous passage. This resolves a material part of the executive/commencement follow-up; the restrictions are not already in force simply because the council voted. Certified bill, final page.

Once effective, the ordinance pauses covered new applications until January 31, 2028, or earlier comprehensive legislation. Previously filed plans, associated later applications, and future phases of existing centers on adjacent or adjoining land are excepted. A workgroup must examine resource use, siting, taxes, fees and other issues and report within ten months after commencement. Those exceptions mean this is not a universal halt on every expansion.

The existing anne-arundel-data-centers / public-finance-121008b767 case already received Dispersion +1 for council passage. Confirmed commencement information improves its lifecycle account; it does not supply another power shift.

Read the evidence and sources →

October scored action

Indiana approves Google's Monrovia power agreement, with protections and shared network costs

2026-10-07 · Dispersion +1 · Secondary lane; primary Lane 3

On October 7, Indiana utility regulators approved AES Indiana's arrangements for Google's planned 390-megawatt data-center load near Monrovia in Morgan County. October 12 reporting brings the decision into this review. The associated generation and storage project has an estimated $737.3 million cost; the load figure describes planned electricity demand, not an operating campus or the solar plant's capacity. Commission order, case 46394.

The approved structure includes minimum-demand payments, termination provisions and financial assurances. AES describes a minimum 15-year contract and an 80% minimum-demand obligation. The commission retains review of actual costs and their allocation in future rate proceedings. Nevertheless, WFYI reports testimony placing $32.3 million of direct-connection facilities on Google while $73.8 million of network upgrades enter the utility's regulated asset base for recovery through future rates. The order rejects requiring Google to pay every remaining network-asset dollar when its contract ends because those assets can continue serving others. AES's approximately $770 million customer-benefit estimate is a forecast, not realized savings. AES account.

Read the evidence and sources →

October scored action

FERC accepts a large-load registry but rejects PJM’s proposed connection bargain

2026-10-09 · Dispersion +1 · Primary lane

On October 9, the Federal Energy Regulatory Commission accepted part of PJM’s proposed tariff package: a definition of large loads and a registry describing major electricity users. It rejected the main Interim Resource Adequacy Service proposal, which would have allowed new large users to connect without matching new generating capacity if they accepted curtailment before grid emergencies. The registry provisions were accepted for October 12 effectiveness. The official docket entry ↗ identifies the partial acceptance and rejection in ER26-3515.

The proposed registry covers loads of at least 50 megawatts. Reporting describes location, demand growth schedules and capacity-supply information. FERC concluded that core service provisions intruded into state retail-rate authority and risked discrimination. This is not an order requiring data centers to bring their own generation or automatically lose power before households. A commissioner’s suggested household/hospital priority is a concurrence, not that operative rule. Final government access, confidentiality and implementation obligations still need examination in the order and accepted tariff.

The rejection is a completed October 9 institutional decision; no later final-rejection vote is needed. Pennsylvania PUC’s September 3 comments ↗ objected to retail compensation/jurisdiction and lack of state input. PJM disputed those objections in its September 23 answer ↗. Those submissions are party positions. Official decision metadata and independent reporting establish partial acceptance/rejection; the full operative order and accepted registry text remain inaccessible.

Read the evidence and sources →

October scored action

England and Wales’ judiciary specifies approval and human-accountability safeguards for AI

2026-10-09 · Dispersion +1 · Primary lane

The judiciary published a position statement October 9, with further specialist coverage October 12. AI may assist judicial work but cannot decide cases or replace judicial reasoning. Every output used must be reviewed, verified and approved by the responsible judicial office holder. Approved tools must provide UK data residency and enterprise protection, with web access disabled.

New use cases, products and pilots go through a central steering group chaired by the Lead AI Judge, which considers legal, ethical, operational, security and data-protection issues. The statement describes pilots in summarization, transcription, redaction and document analysis, among other uses; it does not establish a generally available automated justice service or publish evaluated performance results. The October 2025 guidance ↗ already placed responsibility on judicial office holders and warned about errors and sensitive information. The new statement adds an institutional adoption account without proving that all oversight arrangements were newly created on October 9.

The October 9 statement specifies the central steering group, chaired by the Lead AI Judge, as the sole route for developing, piloting or deploying judicial AI tools and for escalation. It sets out the current arrangement. Earlier October 31, 2025 guidance ↗ already required human checking/personal responsibility and HMCTS service-manager approval. The October statement does not establish that the group was created that day. Continuous review of the policy does not make its present approval gate merely a proposal.

Read the evidence and sources →

October scored action

Forest Grove adopts a pause that leaves already-approved projects intact

2026-10-12 · Dispersion +1 · Secondary lane; primary Lane 3

Forest Grove, Oregon, adopted a 120-day data-center moratorium on October 12, with the city publishing its account October 13. The council voted 7–0 after a public hearing. The pause stops acceptance, processing and approval of new applications for data centers as a principal land use and for expansions of at least 20%. The city's account ↗ confirms adoption and the principal-use and expansion scope.

Projects that already have land-use approval are exempt. That matters for an existing 2024 approval: the city has not cancelled all previously authorized development. The pause gives staff and residents time to examine electricity, land, housing and environmental effects and prepare code changes. It is temporary decision space, rather than a permanent ban or proof of successful cost protection.

Read the evidence and sources →

October scored action

Leon County completes its 18-month moratorium process

2026-10-13 · Dispersion +1 · Secondary lane; primary Lane 3

Leon County, Florida, unanimously adopted an 18-month pause on October 13. WCTV and the Tallahassee Democrat independently report the final vote. The measure covers large-load customer facilities, including large data centers, in the unincorporated county. It pauses acceptance, review and approval of covered development applications; it is not a permanent prohibition.

The county intends to study resource and community effects and develop comprehensive-plan and code amendments before processing future projects. The official September action record ↗ establishes that the earlier vote only advanced the ordinance to its final October hearing. Thus July's decision to prepare a pause and September's first hearing should not be mistaken for the operative adoption now reported.

Read the evidence and sources →

October scored action

Perry Village's new pause exempts the contested Champion Farm site

2026-10-08 · Dispersion +1 · Secondary lane; primary Lane 3

The ordinance expressly excludes the property known as Champion Farm. Consequently the pause does not stop the development at the heart of the village's current controversy. It changes the treatment of other covered applications while the village works on its approach. The notice establishes the exception and adopted duration; the full text is necessary before assigning an exact legal expiry or describing additional exceptions.

Read the evidence and sources →

October scored action

Anthropic clarifies who controls redactions in METR’s embedded evaluation

2026-10-15; October 16 redaction clarification · Dispersion +1 · Secondary lane; primary Lane 2

Anthropic announced on October 15 that six METR evaluators received company hardware, office space and internal-system access broadly comparable to its own risk-assessment teams, subject to specified exclusions.

Anthropic added an October 16 clarification to its October 15 announcement about six METR employees working inside the company. It now explicitly says Anthropic ultimately decides whether information falls within categories it can require METR to redact. METR retains specified rights to describe the access and information it received. The arrangement still permits publication without Anthropic’s general approval; it does not give METR final authority over confidentiality classifications. Current primary account.

Read the evidence and sources →

October scored action

Millington’s six-month pause is adopted, including off-grid computing proposals

2026-10-12 · Dispersion +1 · Secondary lane; primary Lane 3

Millington, Tennessee, adopted Resolution 44-2026 on October 12. Local reporting published October 14 confirms an immediate six-month pause through April 12, 2027, unless extended. The resolution stops acceptance of new applications for the defined computing/power facilities, including facilities in mixed-use developments. It gives the city time to study service, infrastructure, safety and neighborhood effects and write zoning rules.

Projects approved at any stage, and applications already officially submitted and awaiting a hearing, are exempt. This does not reopen all existing approvals or stop every construction project. The city’s two-page resolution establishes the mechanism; reporting corroborates adoption. Memphis and Shelby County proposals remain separate decisions.

Read the evidence and sources →

October scored action

Ohio's Supreme Court preserves Lordstown's ability to pause a data-center proposal

2026-10-20 · Dispersion +1 · Secondary lane; primary Lane 3

On October 20, Ohio's Supreme Court unanimously rejected a developer's attempt to force Lordstown to continue reviewing its proposed data-center complex under the rules that existed before the village's moratorium. Bristolville 25 Developer had started a preliminary site-plan process in October 2025, before the village imposed a ban and subsequently replaced it with a temporary pause.

The distinction matters: Bristolville had not completed the required preliminary stages or reached a qualifying zoning-permit application. The court therefore found no clear legal duty to continue its review under the earlier rules. This is a ruling about this project's procedural position, not a blanket finding that every application can be stopped retroactively. The actual opinion confirms the holding.

For The Race, the decision protects a municipality's remaining room to govern before a developer secures rights to proceed. It does not establish public ownership or a more competitive compute market.

Read the evidence and sources →

October scored action

A federal judge protects the NAACP's ability to pursue its xAI pollution case

2026-10-19 · Dispersion +1 · Primary lane

An October 19 federal order, reported October 20, allows the Environmental Protection Agency to join the NAACP's Clean Air Act case over xAI's gas-fired power plant in Southaven, Mississippi, while rejecting the federal government's claimed power to join and unilaterally dismiss it.

The NAACP and its Mississippi conference sued in April over alleged operation without required permits. Judge Debra Brown held that the statute permits EPA intervention but does not grant the dismissal power the administration asserted. The 22-page order establishes an actual ruling. It neither decides the pollution allegations nor orders the plant closed.

This preserves an independent enforcement route for affected communities when the executive branch prefers that their case end. That is a concrete countervailing-power mechanism, even though the underlying environmental outcome remains unresolved.

Read the evidence and sources →

October scored action

Volusia County adopts a prohibition on large data centers in its unincorporated areas

2026-10-20 · Dispersion +1 · Secondary lane; primary Lane 3

Volusia County, Florida, says its council adopted the final ordinance on October 20. It prohibits large-scale data centers in unincorporated county territory and stops associated applications and approvals, including expansions or intensified operations. It does not govern municipalities inside the county.

The county identifies the statutory threshold as a single location with an anticipated monthly peak electrical load of 50 megawatts or more. The action follows an earlier first hearing; that hearing was not the final adoption. The county's October 21 account establishes passage and the main coverage, while the executed ordinance's detailed transition provisions still warrant inspection.

The power mechanism is a local public institution deciding whether this class of resource-intensive development may proceed. The prohibition does not itself disperse ownership of AI infrastructure.

Read the evidence and sources →

October scored action

Brighton completes its one-year data-center moratorium process

2026-10-20 final action; October 21 announcement · Dispersion +1 · Secondary lane; primary Lane 3

Brighton's October 21 official announcement confirms approval of a one-year moratorium. The earlier October 6 vote was a first reading; contemporary accounts that called it a completed ban omitted that remaining step. October 21 reporting corroborates the final October 20 action.

The city's stated purpose is to pause data-center requests while staff develop code, policy and procedural changes. The earlier official description covers acceptance, processing and approval of relevant permit, license, zoning and land-use applications. The year runs from the ordinance's effective date; that date and final exceptions should come from the executed text rather than being guessed.

This is a real governing interval before further development permissions, with its ultimate value depending on the rules and public process produced during it.

Read the evidence and sources →

October scored action

Amazon agrees to abandon the proposed data-center use of its former GW campus

2026-10-20 · Dispersion +1 · Secondary lane; primary Lane 3

On October 20, Loudoun County chair Phyllis Randall announced that Amazon had accepted a negotiated alternative to its proposed data-center redevelopment of the former George Washington University campus in Ashburn. Amazon publicly acknowledged the agreement, saying that it disagreed with the county about development rights but preferred a shared plan to costly litigation. The announced concession includes withdrawal of the proposed application and foregoing litigation to realize data-center development on this site.

The dispute followed community opposition and the county’s position that data centers were not permitted as the principal use under the older zoning regime. The arrangement, called Project Potomac Promise, includes roughly 25 acres for county facilities, valued at about $65 million, a reported $5 million housing-fund contribution, and mixed-use development with residential uses on the remainder. These are announced terms; a completed deed, inspected payment receipt, final rezoning and the instrument binding future owners have not been verified.

The modest power shift is the successful exercise of community and county bargaining leverage to secure abandonment of the proposed data-center use. Amazon’s public acceptance and the county’s announcement provide sufficient evidence for this limited assessment. Permanent exclusion of data centers and delivery of public benefits remain implementation questions. A rezoning condition or properly drafted recorded covenant could make the restriction enforceable; which instrument is actually used remains unverified.

Read the evidence and sources →

October scored action

The United States extends an AI trade-secrets case to companies and their financiers

2026-10-19 · Concentration +1 · Secondary lane; primary Lane 2

On October 19, the U.S. State Department designated five China-based entities under the Protecting American Intellectual Property Act in connection with theft of Google AI-related trade secrets. The targets include Shanghai Zhisuan Technology, MiraclePlus and three associated investment or management entities. The department’s statement and fact sheet, reproduced by Forth, establish actual designations rather than a proposal.

The fact sheet specifies sanctions under Section 2(b)(1)(A), (D), (H), (I) and (J). These concern property within U.S. jurisdiction or U.S. persons’ control, loans or credits from U.S. financial institutions totaling more than $10 million in a twelve-month period, with the statute’s humanitarian-relief qualification, foreign-exchange and banking transactions subject to U.S. jurisdiction, and U.S. investment in the entities’ equity or debt, subject to statutory scope and exceptions. This reaches organizations and financing relationships beyond the prosecution of one engineer; it is not a general ban on Chinese AI.

The power shift is the federal government’s concrete exercise of national-security authority to narrow the targeted AI-related network’s access to assets and finance within U.S. reach. That supports a modest concentration assessment even if the security rationale is defensible. It does not establish increased Google market share or a measured decline in Chinese AI capability.

Read the evidence and sources →

October scored action

Project Tango receives administrative approval for a larger data-center footprint in Palm Beach County

2026-10-07 · Concentration +1 · Secondary lane; primary Lane 3

Palm Beach County’s zoning director approved a revised Central Park Commerce plan on October 7, an action reported by WLRN on October 21. The site is in unincorporated western Palm Beach County near Twenty Mile Bend. The administrative approval adds about 64.46 acres to the development, bringing it to about 202.67 acres, and permits approximately 698,000 square feet of data-center use plus 54,000 square feet of accessory office space. The earlier plan allowed about 200,000 square feet of data-center use and 6,000 square feet of office space. The overall development retains its approximately 2.02-million-square-foot ceiling, including substantial warehouse space. The signed approval and development orders establish an entitlement, not an operating facility; other permits and existing development conditions still apply.

County commissioners rejected a separate, much larger expansion in July. The applicant nevertheless had an administrative route under its earlier approved plan. The county’s subsequent processing pause did not stop this pending application. That distinction matters: the October action does not establish that staff unlawfully reversed the commission, but it does establish a substantial expansion of private development rights without another commission vote on this application. The available approval does not establish operating IT capacity, final power architecture or water consumption.

Administrative approval expands a private data-center entitlement through an existing-plan route after a larger proposal was rejected. Other permissions remain necessary.

Read the evidence and sources →

October scored actionPending verification

Clackamas County adopts a pause on new and expanded data centers

2026-10-22 · Dispersion +1 · Secondary lane; primary Lane 3

On October 22, Clackamas County’s commissioners voted 5–0 to adopt a data-center moratorium. The county’s official draft minutes record the passed motion. The arrangement presented to commissioners suspends county approval of land-use and building permits for new or expanded primary-use data centers in unincorporated territory, while staff develops permanent rules. It does not govern incorporated cities merely because they are inside the county.

The staff-described initial pause lasts up to 120 days. A possible six-month extension requires another public hearing and findings about the continuing need and progress toward a solution. The signed resolution remains outstanding, so any final exceptions must stay qualified. The verified vote establishes adoption; the hearing calendar alone would not.

Read the evidence and sources →

October scored actionPending verification

Grant County, New Mexico, approves a one-year data-center moratorium

2026-10-22 · Dispersion +1 · Secondary lane; primary Lane 3

Grant County commissioners voted 4–1 on October 22 to adopt a one-year pause on data centers and their directly supporting infrastructure. The Albuquerque Journal’s meeting report establishes the vote and quotes the restriction on establishing, constructing, developing, expanding or commencing covered facilities. The county’s official meeting notice ↗ identifies Ordinance O-26-03 and its application to unincorporated county territory.

The dispute includes the proposed Site Layer 1 project near Hachita. Commissioners want time to consider rules and resource effects. The developer and a landowner opposed the pause; one concern was whether its broad language could also obstruct environmental studies. The final ordinance is still needed to settle exceptions, commencement and that boundary. Neither the vote nor the project announcement establishes an operating campus or verified water demand.

Read the evidence and sources →

October scored actionPending verification

Hayward adopts an initial 45-day pause, rather than a two-year ban

2026-10-20 · Dispersion +1 · Secondary lane; primary Lane 3

Hayward’s City Council unanimously adopted an immediate data-center moratorium on October 20. The city published its account October 21, and the Hayward Herald reported the meeting October 22. The official legislative history ↗ records passage, including a modification.

The initial period is 45 days. California law allows later extensions totaling up to two years; those extensions have not all been adopted. During the pause, the city can study cumulative resource demands, emergency-response needs and land-use consequences before approving new facilities. The existing Stack project under construction is not described as cancelled. The final modified ordinance is still needed for a complete account of exceptions and application handling.

Read the evidence and sources →

October scored actionPending verification

Coweta County returns Project Peach’s site to rural-conservation zoning

2026-10-20 · Dispersion +2 · Secondary lane; primary Lane 3

On October 20, 2026, Coweta County, Georgia, approved returning approximately 323.9 acres for Project Peach from Light Industrial to Rural Conservation. The county’s official recap confirms the reversal. On April 15, 2025, commissioners had granted North Coweta Investors LLC industrial zoning for a data-center operation, subject to 25 conditions. Condition 21 required a land-disturbance permit by October 16, 2026. Condition 23 required a will-serve letter and power purchase agreement; CyrusOne obtained a twelve-month extension of the original October 2025 power-agreement deadline.

The county’s September 28 staff memo said the required permanent power agreement and permit were still missing. Reporting on the October 20 meeting says temporary construction power had been arranged and site plans had entered initial review, but the required permit and permanent supply agreement remained outstanding. Commissioners voted 3–2 to return the land to Rural Conservation. Some preparatory work occurred; the failure concerns the required final conditions. The action removes the project’s industrial zoning entitlement, not an operating data center. The final instrument and any subsequent challenge remain follow-up evidence.

Read the evidence and sources →

October scored action

Italy puts a human decision-maker—and a legal remedy—between workplace AI and covered final decisions

2026-10-07 decree; October 8 publication; October 23 effect · Dispersion +1 · Primary lane

Italy’s Legislative Decree 179, issued October 7 and published October 8, took effect October 23. Article 41 requires employers using AI in covered final employment decisions to leave the decision to a person with effective, autonomous authority. The rule covers establishing, changing or ending employment, including discipline and performance evaluation. Workers cannot waive it by consenting. Candidate searching and screening, including exclusion from later recruitment stages, are expressly outside this particular definition; other applicable protections remain. Official Article 41 ↗.

An affected worker can request an intelligible explanation from a person, including AI’s influence and the principal factors considered. Dismissals and other employer decisions that violate the human-decision requirement are void. This gives the requirement a concrete legal consequence.

Read the evidence and sources →

October scored actionPending verification

Current Affairs puts restrictions on AI-generated writing and art into its union agreement

2026-10-02 signed/ratified agreement announcement · Dispersion +1 · Secondary lane; primary Lane 8

On October 2, the Current Affairs Guild announced that staff had ratified and signed a two-year contract after bargaining concluded in September. Its published account identifies a prohibition on generative AI writing articles or creating magazine art, retained worker copyright and a worker representative on the board. Editor Nathan J. Robinson confirms the agreement and says it still allows helpful uses of technology. The announcement therefore does not establish a ban on every workplace AI use. Jointly presented union and employer account ↗.

Read the evidence and sources →

October scored actionPending verification

Martin County adopts a one-year pause—but an existing application can proceed

2026-10-27 · Dispersion +1 · Secondary lane; primary Lane 3

Martin County, Florida, commissioners voted 4–0 on October 27 to pause new large-scale data-center applications for one year. The pause concerns unincorporated county land, where the county controls planning. Staff will use the interval to examine resource demands and possible comprehensive-plan and land-development-code changes. It does not govern the separate municipality of Indiantown.

The exception matters: a hyperscale proposal already filed near Kanner Highway west of Interstate 95 is unaffected. This is a pause on new applications, not a decision rejecting that individual project. Commissioners adopted the pause on second reading. The final ordinance's complete exceptions and commencement remain to be checked; reporting establishes adoption.

Read the evidence and sources →

October scored actionPending verification

Madison County removes data centers from an enterprise-zone property-tax benefit

2026-10-21 · Dispersion +1 · Secondary lane; primary Lane 9

On October 21, Madison County, Illinois, approved enterprise-zone changes excluding data centers from a property-tax incentive. The Southwestern Madison County zone covers Granite City, Madison and Venice. Its eligible improvements can otherwise receive a ten-year abatement, with fuller relief initially and a later phase-out; land remains taxable. Exclusion means a qualifying data-center improvement would no longer receive this particular relief.

This is not a countywide construction ban or removal of every incentive. Discovery-zone benefits depend on individual taxing districts, and municipalities may consider separate arrangements. Reporting identifies the adopted county action; the complete amendment and any state approval or commencement requirements remain unverified. The separate 21–3 vote reported in the same coverage concerned solar incentives, not this data-center decision.

Read the evidence and sources →

October scored action

HHS removes mandatory information and risk-management requirements for clinical AI

2026-10-28 final rule; December 28 effect · Concentration +1 · Primary lane

HHS published its final HTI-5 rule on October 28, following its October 26 announcement. From December 28, developers of covered certified health-record software will no longer have to support the specified disclosures about decision-support tools or undertake the certification rule's predictive-tool risk-management practices. These disclosures explain matters such as training, intended uses, limitations and performance across patient groups. A hospital choosing a predictive tool consequently loses a standardized certification requirement on which to base its questions. This is an adopted future change, not a removal already in force. Operative rule ↗.

The change concerns this certification route, not every AI system or every legal protection. HHS points to continuing anti-discrimination obligations and encourages buyers to request information. It says it found no evidence that the disclosure requirements improved care; commenters disputed the wisdom of removing them before fuller evaluation. The broader package removes 14 certification criteria and revises seven, rather than the 34 removals originally proposed.

Read the evidence and sources →

October scored actionPending verification

Van Buren adopts siting, setback and noise rules before a project arrives

2026-10-26 · Dispersion +1 · Secondary lane; primary Lane 3

Van Buren, Arkansas, council members voted 6–0 on October 26 to adopt data-center regulations. The city confines facilities to Industrial-2 districts, requires 1,000 feet of separation from districts allowing residential development, and sets daytime/overnight noise limits of 65/55 decibels. Applicants must undergo development-plan review and supply utility-capacity information. These are restrictions on a permitted development route, not a citywide ban.

Mayor Joe Hurst says companies have made preliminary inquiries but submitted no formal project. Planning Director Wally Bailey drew on other Arkansas cities' ordinances. The available explanatory report establishes adoption and core requirements; the signed ordinance, measurement method, exceptions and commencement remain uninspected. The separate $45 million bond discussion in the headline is not established AI financing.

Read the evidence and sources →

October scored actionPending verification

DeSoto blocks two expansion rezonings for the same proposed campus

2026-10-27 and October 28; one campus judgment · Dispersion +1 · Secondary lane; primary Lane 3

DeSoto County, Florida, commissioners failed to approve DCIP-related rezoning applications on October 27 and 28: both motions tied 2–2. The first concerned 3-F Ranch; the second concerned the approximately 554-acre Swisher property. These were separate decisions within the developer's proposed campus near Arcadia. They leave the applications without the requested zoning. They do not reverse the separate March approval of the original 34.22-acre site. County application register ↗; official two-day hearing schedule ↗.

The county register identifies the original application acreage for 3-F Ranch differently from the roughly 238 acres reported at the hearing; the final tract scope needs the decision record. Reporting describes a gas-powered campus proposal and unresolved noise, water and wastewater details. Neither the power capacity nor an operating cooling design was established. The developer's broader ambition is not operating capacity, and the failed votes do not establish permanent abandonment.

The county exercised existing land-use authority to withhold expansion permissions. For The Race, that is a concrete public decision rather than a protest count. The two applications should remain distinguishable without treating one proposed campus as two independent trend cases.

Read the evidence and sources →

October scored actionVerified

Washington County restricts county property, access rights and data-center secrecy

2026-10-27 · Dispersion +1 · Secondary lane; primary Lane 3

Washington County, Oregon, adopted signed Resolution and Order 26-103 on October 27 by a 3–1 vote, including three operative amendments. County departments cannot voluntarily grant easements or rights-of-way to facilitate a known large standalone data center, except where required by law or supporting a road improvement consistent with the approved Transportation System Plan. County-owned property cannot be sold, conveyed or leased to facilitate such construction. The county also cannot enter related nondisclosure agreements unless legally required.

Those directions govern county resources and conduct. They are more consequential than the order’s statements opposing large standalone data centers and related financial incentives. The order also directs limited scoping of possible future planning work; it does not establish a general zoning ban, a countywide application moratorium or repeal of every incentive.

The county’s land-use jurisdiction concerns unincorporated areas; incorporated cities retain their own land-use authority. The restrictions include the legal and road-plan exceptions described above.

Read the evidence and sources →

October scored actionPending verification

San Antonio requires council approval for future data centers

2026-10-29 · Dispersion +1 · Secondary lane; primary Lane 3

San Antonio’s council voted 9–2 on October 29 to require case-by-case specific-use authorization for future data centers. A developer must bring its proposal to elected representatives, giving residents a public decision point before construction. Council can consider project-specific conditions. The adopted approach confines the use to eligible commercial/industrial zones and excludes the Edwards Aquifer Recharge Zone.

The council rejected both a by-right alternative for certain industrial sites and the mayor’s more prescriptive package. Do not describe the rejected 1,000-foot setback or 45-day notice as adopted requirements. The indexed official meeting transcript identifies Option Two as the final motion, with definition and World Heritage amendments; independent local reporting confirms the completed vote. Final signed text, existing-project treatment and commencement remain documentary checks. Official transcript ↗; independent corroboration ↗.

Read the evidence and sources →

October scored actionVerified

New York adopts enforceable limits on chatbot features offered to minors

2026-10-28 signature; January 1, 2027 effect · Dispersion +1 · Primary lane

Governor Kathy Hochul signed S9051B/A10379C on October 28; the restrictions take effect January 1, 2027. Covered operators may supply the listed features to New York users only after determining that they are adults. The list includes pretending to be human, cultivating personal relationships, encouraging secrecy or self-harm, sexual content and specified uses of remembered personal information.

The law exempts systems limited to specified customer-service or research/technical functions and business systems used internally or for employee productivity. Interim age checks must offer multiple methods, including one preserving anonymity or avoiding government identification; an adult’s self-declaration alone is insufficient. The attorney general can seek injunctions, restitution, damages and penalties up to $25,000 per violation and must provide a public complaints route. Signed status and active bill text ↗.

Read the evidence and sources →

October scored actionVerified

Animation performers ratify contracts with concrete AI protections

2026-10-29 ratification · Dispersion +1 · Secondary lane; primary Lane 8

SAG-AFTRA members ratified four-year television and basic-cable animation agreements on October 29. They cover relevant television and new-media animation, not theatrical animated films. The term ends June 30, 2030. The union’s FAQ says most terms start the Sunday after the producers’ association receives ratification notice; specified provisions have other dates.

The union’s agreement summary ↗ closes a loophole involving replicas made from existing recordings and prevents later, unprovided scripts from expanding alterations allowed without further consent. It establishes minimum compensation and residuals for specified independently created replicas. Consent for replica-based foreign-language dubbing applies to productions starting July 1, 2027. Transfer provisions preserve contractual responsibility or require an approved transferee’s written commitment, including arbitration rights. Synthetic performers remain possible under qualified notice, bargaining and additional-value provisions; this is not a blanket AI prohibition. Independent ratification report ↗.

Member ratification completes the collective decision. The general contract runs from July 1, 2026 through June 30, 2030, while individual new protections have their own commencement rules. Further notice and final-document checks do not postpone recognition of the ratified agreement.

Read the evidence and sources →

October scored actionPending verification

Silver City’s council adopts its data-center permit pause

2026-10-27 · Dispersion +1 · Secondary lane; primary Lane 3

Silver City’s council unanimously approved a resolution on October 27 temporarily suspending permits for data-center facilities within the town, according to Juno Ogle’s October 29 meeting report. The published council notice ↗ identifies Resolution 2026-29. Officials chose a resolution on advice from the town attorney and administration, with an ordinance possible later.

Read the evidence and sources →

October scored actionPending verification

Pflugerville puts high-risk city technology under elected oversight

2026-10-27 · Dispersion +1 · Primary lane

Pflugerville’s council unanimously adopted its SAFE technology policy on October 27. Local reporting distinguishes routine administrative tools, which remain under the city manager, from high-risk systems—including surveillance and biometric identification—that require council review. The official legislative record ↗ identifies RES-1443 as a resolution.

The reported policy preserves human judgment in significant city decisions and generally prevents vendors from selling city data or using it to train general-purpose AI without council approval and legal authorization. A resident commission, public information page and review procedures are to be established within ninety days; they are implementation duties, not demonstrated operating institutions. Specified council authorizations and emergency exceptions matter. The separate November 3 charter proposal should not be confused with this adopted policy.

Read the evidence and sources →

October scored actionPending verification

A newsroom contract protects workers’ professional judgment over AI

2026-10-08 ratification; October 21/29 union publications · Dispersion +1 · Secondary lane; primary Lane 8

Embarcadero Community News Guild members ratified their first three-year contract on October 8. the NewsGuild published details October 21, followed by CWA’s October 29 account. The union represents twenty reporters, editors, designers and photo staff at the California nonprofit newsroom.

The union reports that members participate in setting AI policy and cannot be required to use AI in ways conflicting with professional ethics, legal standards, journalistic goals or AI policies. That is narrower than a ban on AI or a worker veto over every deployment. The accounts come from the union family; the complete agreement and clause-specific remedies remain uninspected.

Read the evidence and sources →

Earlier actions and October implementation

These support the cumulative assessment. They are not new October adoptions and receive no repeat award.

Earlier action / October lifecycle

BetaNYC shows how civic groups can combine public-record access with citizen AI literacy

May 2026 release; October 5 testimony / October 6 recognition · Dispersion +1 · Secondary lane; primary Lane 6

Alongside its October 5 Council testimony, BetaNYC documented existing civic AI resources. Its public tools page ↗ describes connectors for Council legislation, procurement notices, public spending, laws, service information and other public records. A connector uses the Model Context Protocol, a standard interface through which an assistant can request information from a specified source. Some connectors require free agency API keys; others do not. Availability is not an accuracy audit.

Its AI 101 materials ↗ serve New Yorkers attending introductory classes, including recordings and settings guidance for common assistants. The testimony ↗ separately schedules an October 8 train-the-trainer session for staff of community partner organizations in the Council’s AI Community Engagement initiative. That audience is not all city employees. Future lessons and the paused fellowship are not delivered programmes; the specific funding and curriculum independence of this session were not established.

Availability, license and chronology resolved. BetaNYC’s public toolkit describes seven free civic-data connectors compatible with multiple assistant clients. The inspected Council connector’s README, MIT license and changelog confirm installation and copy/modify/distribute rights. Its initial release was May 19, 2026, MIT licensing May 22, and hybrid operation May 26; October 5 testimony/publicity is not a new launch. Current code includes unreleased 2.6.0 functions, which are not represented as packaged capability. The underlying government APIs already existed. Free keys, local indexing, storage, freshness, assistant-provider and output-accuracy dependencies remain. Other connectors’ exact first-release dates are not established here.

Primary artifacts: https://github.com/BetaNYC/nyc-council-mcp ↗ ; https://github.com/BetaNYC/nyc-council-mcp/blob/main/CHANGELOG.md ↗ ; https://github.com/BetaNYC/nyc-council-mcp/blob/main/LICENSE ↗ .

Read the evidence and sources →

Earlier action / October lifecycle

GSA adopts substantive protections for government purchases of language models

2026-09-28 adoption; 2026-10-19 mandatory use in new covered purchases · Dispersion +1 · Primary lane

GSA adopted a standard contract clause on September 28 for government purchases in which a large language model is a material feature and directly receives or produces government data. Mandatory use in new covered purchases starts October 19; contracting officers may use it earlier. Incorporating it into an existing contract is a separate contracting decision. This is an adopted purchasing rule, not a single new supplier contract that every government can immediately order from.

The clause protects covered government inputs, outputs and custom developments; limits their reuse for training, sale and marketing; requires portable data and documented interfaces; and protects migration from obstructive charges. It includes reasonable human intervention and action traces, incident reporting within 72 hours, ordinarily 30 days' notice of material changes, and suspension and noncompliance remedies. Supplier ownership of pre-existing models and technology remains. Decommissioning liability after qualifying termination is capped at 25% of the affected order; replacement-system and reprocurement costs are excluded.

Eligible state, local and tribal governments and public educational institutions can use relevant GSA purchasing programmes within their statutory scope. If the underlying eligible contract contains this clause and the supplier accepts the non-federal order, its applicable terms carry into that separate purchase. Suppliers may reject those orders; eligibility, product category and incorporation must be checked for the particular purchase. The protection is therefore potentially reusable well beyond federal agencies, without assuming universal coverage or automatic amendment of all existing contracts.

Read the evidence and sources →

Earlier action / October lifecycle

DoNotPay's final order provides a concrete example of AI consumer protection

January 2025 final order; January 14/16/17 document/vote/index dates · Dispersion +1 · Primary lane

The FTC's January 2025 DoNotPay order prohibits unsupported claims that covered services perform like a human professional. It also prohibits specified misrepresentations about legal analysis, fee savings and subscription features. The order requires $193,000 in monetary relief and notices to eligible customers who subscribed during 2021–23.

These are enforceable duties against a named provider under existing consumer-protection authority. The order requires evidence supporting professional-equivalence claims; it does not impose a general AI-model audit or universal data-minimization regime. Recovery of the actual order today establishes its clauses, but not proof that every payment and notice requirement was completed.

Read the evidence and sources →

Earlier action / October lifecycle

Brazil’s enacted data-center tax regime trades tax relief for domestic services, research and resource conditions

2026-09-15 enactment · Mixed 0 · Secondary lane; primary Lane 9

Brazil enacted Redata in Law 15.504, dated September 15. The law establishes tax relief for qualifying data-center equipment, covering ordinary cloud services as well as AI. Companies must obtain federal qualification; an operating intake and implementing rules were not verified. Finance Ministry account.

The ordinary commitments include domestic services amounting to 10% of data-center service revenue and research investment equal to 2% of benefited equipment purchases. Domestic services can be sold: this is not 10% free public computing. An additional research contribution of 10% of benefited equipment purchases can replace the domestic-service commitment. The ordinary domestic-service and research commitments fall by 20% in the North, Northeast and Centre-West regions. Beneficiaries also face low-emission or renewable-power, water-efficiency and reporting conditions. The law provides tax recovery or suspension/cancellation for specified failures. Its five-year headline duration has an exception: specified federal tax benefits end on December 31, 2026 under the tax transition. Operative law, especially articles 11-B–11-J.

For The Race, this is a concrete statutory bargain over public revenue and private infrastructure. It supports privately owned scale while attaching domestic capability and accountability conditions. Geography and research spending do not establish public ownership, affordable access or a net public return; the alternative to domestic provision also weakens a simple access interpretation.

Brazil’s conditions fit an established national industrial-policy practice of exchanging fiscal benefits for domestic capability. The Informatics Law, originating in 1991, links incentives to domestic research and development and provides for suspension/recovery when conditions are not met. PADIS, established in 2007, likewise links semiconductor incentives to domestic research; current legislation requires at least 5% of qualifying revenue in research, development and innovation, including a specified institutional-partnership share. MOVER, established in 2024, exchanges credits for research and technological investment; a related auto-parts import arrangement requires a contribution equal to 2% of customs value to a national development fund. These are precedents in strategic industries, not proof that every Brazilian tax concession has such conditions. Informatics Law; PADIS legislation; MOVER official explanation.

Redata extends this familiar conditional-incentive approach to computing infrastructure. Its distinctive combination concerns domestic services, research partnerships, energy/water conditions and public reporting. Free services to research institutions or government can count toward the domestic-service commitment with a regulatory multiplier, but commercial domestic sales can also satisfy it, and additional research investment can replace it. It therefore creates no guaranteed free public-compute entitlement. The reusable instrument is tax relief conditional on specified, verifiable public benefits; delivered benefits, net fiscal value and democratic dispersion remain to be assessed.

Read the evidence and sources →

Earlier action / October lifecycle

Richmond’s existing data-center moratorium creates a public rulemaking interval; an extension needs final-text confirmation

2026-09-15 adoption; October extension remains qualified · Dispersion +1 · Secondary lane; primary Lane 3

Richmond, California, adopted Urgency Ordinance 13-26 N.S. on September 15. The city’s official account establishes an immediate 45-day pause on issuing or approving permits and land-use entitlements for new data centers while it studies land use and develops rules. The initial period expires October 30. Its October 20 hearing notice proposed extending the pause by 22 months and 15 days. The notice covers facilities serving AI, high-performance computing, cloud services and cryptocurrency, while excluding subordinate server rooms serving another primary use.

An independent civic review of the October 20 meeting reports a unanimous extension through September 15, 2028. The final extension instrument has not been verified. The reported extension should therefore be distinguished from the original moratorium, which the city itself confirms was adopted. The original pause was enacted September 15.

The adopted pause stops covered new permissions while the city develops its rules. Its temporary scope limits the change.

Read the evidence and sources →

Earlier action / October lifecycle

Gilroy’s moratorium stops future applications while leaving the approved Amazon project in place

2026-09-14 adoption · Dispersion +1 · Secondary lane; primary Lane 3

Gilroy, California, unanimously adopted an immediate 45-day moratorium on September 14. According to the city’s detailed explanation, it pauses future data-center applications while the city develops rules for siting and operation. It does not stop the previously approved Amazon Web Services facility already under construction. A second Amazon location had only reached preliminary discussions; a future formal application would be subject to the pause.

The city’s October 15 notice scheduled an October 19 decision on extending the moratorium by 10 months and 15 days, through September 3, 2027. October 21 reporting says the extension passed, but the final instrument has not been verified. The original September adoption is confirmed by the city and contemporaneous local reporting. An existing project’s exemption is a material boundary on the power effect, not evidence that the entire pause is ineffective.

The adopted moratorium creates time to govern future applications. The approved AWS facility remains outside the pause.

Read the evidence and sources →

Earlier action / October lifecyclePending verification

Texas moves permit screening out of an automatic filing process

2026-08-03 and September 21 existing lifecycle; October 21 screening response · Dispersion +1 retained; no new award · Secondary lane; primary Lane 3

On October 21, the Texas Commission on Environmental Quality temporarily disabled the electronic filing route used for automatic authorizations after watchdogs identified data-center construction permits issued during the governor’s permitting pause. The agency told the Texas Tribune that applications had to be physically submitted so staff could check whether they concerned data centers. It also said identified permits had been suspended.

TCEQ’s construction-stormwater notice confirms that the pause includes applications for construction projects associated with data centers. This is an implementation change in screening, not a newly enacted statewide data-center law. The original October 19 response letter, individual suspension records and the filing system’s subsequent status remain separate checks.

Read the evidence and sources →

Earlier action / October lifecycle

Saginaw requires data-center impact review and continuing reports

2026-09-28 adoption; October 9 commencement · Dispersion +1 retained; no second award · Secondary lane; primary Lane 3

The City of Saginaw’s certified Ordinance O-281 records an 8–0 vote September 28 and an October 9 effective date. Principal-use data centers require special-land-use review. A limited accessory-use exemption applies where computing serves the on-site enterprise, supplies no third parties, occupies at most 10% of the building footprint and is not in a separate building.

Covered developers must provide resource and operating information, hold neighborhood meetings and finance necessary public water/wastewater capacity increases. Continuing reports and noise studies are tied to business licensing; required reports must be submitted before renewal. The text also requires provision for decommissioning security. Certified ordinance ↗.

Read the evidence and sources →

← All nine lanes