Tag: Government Accountability

  • A Technology Leader’s First Year: A Guide for Counties and Cities

    By the Founders, Department of Technology | San Diego, California | November 13, 2026

    Most county boards and city councils are being asked to approve the largest infrastructure projects in their history with a planning staff built for strip malls. This is a practical first-year guide for the person whose job it should be to fix that.

    Our proposal calls for elected technology leaders at the local and county level. What would one actually do? Everything below has been tried somewhere, in communities of different sizes and politics. We cite examples as examples, not endorsements, and we flag where the evidence is thin. Local law varies, so check with your county attorney before adopting anything binding.

    Months 1 to 3: Find out what is coming, and stop the clock

    Inventory the pipeline. Ask your utility how many large-load connection requests are sitting in your territory, how many megawatts they represent, and how many are speculative or duplicated. This matters. AEP Ohio was facing 30 gigawatts of potential new load before it adopted a data center tariff, and one analysis found its pipeline fell from roughly 30 GW to 13 GW after the tariff took effect, suggesting much of the reported demand was speculative or duplicated across utilities. A local government that cannot tell the real projects from the placeholders cannot plan.

    End by-right approval. In March, the Loudoun County Board of Supervisors eliminated by-right zoning for data centers. Harrisonburg, Virginia, moved data centers to special-use permits, which routes proposals through public hearings and discretionary review. A Brookings researcher has recommended never allowing by-right data center development. Where a pause is needed, treat it as a tool with a work plan and an end date. A Federation of American Scientists review found that local moratoria share the same stated rationale: the zoning code does not yet define data centers, so the jurisdiction needs time to study impacts and draft rules.

    Ask the standard questions. Cuyahoga County’s playbook urges communities to ask about power demand, water use, grid upgrades, backup generators, jobs, infrastructure costs and decommissioning plans. Put those questions in writing and make every applicant answer them in public.

    Months 4 to 6: Write the rules

    Linn County, Iowa, adopted one of the most detailed local frameworks so far. Its ordinance requires a water study as part of the zoning application and a water-use agreement with the county before construction, and it also covers noise, light, road use and decommissioning bonds. The board finalized it unanimously after three readings and multiple public hearings. In Scott County, Kentucky, a draft ordinance would bar data centers from prime farmland and wetlands, require developers to pay for water system upgrades, and require a cleanup bond.

    One caution. Jefferson County’s committee worked to keep its draft legally defensible under recent Supreme Court rulings on land-use exactions. In general, what you demand has to relate to the project’s actual impacts. Have counsel review the ordinance before you adopt it.

    Months 6 to 9: Get a seat in the rate case

    Your county does not set electricity rates, but it lives with them. The state utility commission does the setting, and many have recently created separate rules for the largest customers. According to the Edison Electric Institute, 23 states had approved at least one large-load tariff as of May 2026, with seven more pending. Ohio’s AEP tariff applies to data centers above 25 megawatts, requires them to pay at least 85 percent of contracted capacity and commits them to initial contracts of at least twelve years. Dominion’s Virginia tariff sets 14-year minimum contracts and $1.5 million per megawatt of collateral. A Lawrence Berkeley National Laboratory brief lists minimum billing demand, exit fees and collateral as common building blocks.

    Find out whether your utility has such a tariff and, if not, whether a proceeding is pending. In many states, local governments can file comments or intervene, so ask your counsel. A county technology leader’s job is to make sure the people who live there are represented where the cost allocation is decided.

    Months 7 to 9: Negotiate in public

    Use community benefit agreements, carefully. The Federation of American Scientists found only eight data center community benefit agreements when it looked. Lancaster’s covers transparency, water, energy, noise, public works and decommissioning, but the reviewers noted it leaves much of the substance to be decided later, and that tax breaks can outweigh any financial benefit a community receives. The lesson is to write numbers and enforcement into the agreement now.

    Do not sign NDAs. Bloomberg Law reports that Microsoft is working to end any active NDAs governments have signed. Proposed Minnesota legislation would require at least two public hearings and disclosure of key details, including the company behind a project. You do not need to wait for a state law. A local government can adopt a policy that it will not sign NDAs on development matters and will post proposals, incentive terms and cost-benefit analyses on its website.

    Months 10 to 12: Budget for the upside and the downside

    Data center revenue can be a windfall, and it can be a trap. We cover the budgeting in a companion piece, “What Every County Treasurer Should Model Before AI Layoffs.” For your first-year report, the minimum is this: publish how much of your general fund depends on data centers, what happens to that revenue if equipment values fall, and what reserve you are holding against it.

    Then publish the whole first year in plain language: projects reviewed, conditions imposed, public hearings held and agreements signed.

    Your first week

    1. Ask the utility for the pipeline numbers. Megawatts, projects and status.
    2. Check your zoning. Is a data center allowed by right anywhere in your jurisdiction?
    3. Find out what has been signed. Any NDAs, development agreements or incentive deals.

    The case against our case

    • Data centers pay more than they cost. Speakers at a National Taxpayers Union discussion said Loudoun County receives about $26 in tax revenue for every $1 spent on services for data centers. Industry advocates argue that heavy requirements and delays can send projects, and that revenue, elsewhere. Loudoun itself credits favorable zoning and fast approvals for accelerating its growth, even though it later ended by-right approval. A good technology leader should make the process predictable and fast for projects that meet the standards, not just slower.
    • Small counties lack the expertise. A rural county may not be able to staff a water study or a rate-case intervention. That argues for shared staff across counties, or for state technical help, and we would support both.
    • Legal limits are real. Exaction rules constrain what localities can demand, and, as the FAS review shows, many agreements stay vague. This is a reason to involve counsel early, not to skip the work.
    • It might not need to be an elected office. A county could assign this to a staff director. Our view is that elected officials are accountable to voters for the tradeoffs, but a staff role is a sensible first step.

    Start with one question

    If your community is being asked to approve a data center this year, ask the person proposing it a single question: who in our government is responsible for the whole picture of power, water, land, taxes and jobs? If the answer is nobody, that is the position to fill. Find our proposal at department.technology/.

  • The First 100 Days: A Technology Agenda for the Next Congress

    By the Founders, Department of Technology | San Diego, California | November 13, 2026

    A new Congress has 100 days to show it can govern the technology buildout instead of reacting to it. Here is a practical agenda that members of either party can sign onto.

    In our last piece, we described five mistakes the previous Congress made on data centers and AI. This one is the to-do list. We built it from items that already have bipartisan footprints, because the fastest agenda is one that members have already voted for, sponsored or said they support. One timing note: bills that do not become law expire when a Congress ends, so even measures that passed one chamber, like the Ratepayer Protection Act, have to be introduced again.

    1. Days 1 to 30: Hold one set of hearings on the whole picture

    Today the pieces of this problem sit in different committees. Energy committees see the grid. Commerce committees see competitiveness. Finance and tax committees see revenue. Each hears from its own witnesses, and nobody hears the tradeoffs.

    Hold a joint hearing series with the same witnesses in the same room: grid operators, state utility regulators, economists, county officials and workers. The evidence on each risk is already strong enough to start. In the largest U.S. grid market, wholesale power prices rose almost 76 percent in a year and the market monitor called the effects irreversible. At the same time, BloombergNEF expects China to add more than six times as much generating capacity as the United States over five years. Members should hear both facts at once.

    2. Days 1 to 45: Reintroduce ratepayer protection and settle the real disagreement

    The Ratepayer Protection Act cleared the House Energy and Commerce Committee 52 to 0, passed the House 417 to 3, and then failed a Senate procedural vote 57 to 43 that needed 60. The two sides disagreed about one question: whether states should merely be required to consider making large data centers pay for the grid upgrades built to serve them, or whether the cost allocation should be mandatory, as in the Democratic GRID Savings Act.

    Both positions have a principled basis. Utility regulation has long been a state responsibility, and voluntary pledges have a mixed record. We suggest negotiators look for a middle design: a mandatory core for the very largest new loads, with states keeping flexibility over how to implement it. That is our suggestion, not a settled answer, and the details matter. The point is to have the argument in February rather than the weeks before an election.

    3. Days 30 to 60: Open the deals

    Secret agreements are the issue where public frustration is highest and the policy fix is simplest. Bloomberg Law found that 25 of 31 proposed data center projects in Virginia involved nondisclosure agreements, and that Microsoft says it is working to end any active NDAs governments have signed. Lawmakers in more than a dozen states have introduced bills to ban such agreements, but only Delaware has passed a transparency measure through its legislature, according to MLex. A bipartisan group in Congress has now introduced a federal bill to ban NDAs that keep officials from discussing proposed data center projects, while protecting trade secrets.

    Move that bill. And because Congress’s reach is strongest where federal assets are involved, require public disclosure of any data center deal that touches federal land, federal funds or federal permits.

    4. Days 60 to 90: Ask the revenue question before the layoffs

    We do not know how much AI will displace work, and forecasts vary widely. We do know how exposed the tax base is if it does. A RAND analysis found that 84 percent of federal revenue in 2024 came from individual and payroll taxes, and that losing high-paid white-collar jobs would hurt revenue disproportionately. New York City’s Comptroller has already modeled five AI scenarios for the city’s finances.

    Ask the Congressional Budget Office and the Government Accountability Office to publish scenario analyses of federal revenue under different displacement paths, and encourage states and counties to do the same. Planning for a range of outcomes is not predicting the worst one.

    5. Days 90 to 100: Name an owner

    Every item above would be easier to carry out, and harder to forget, if someone were accountable for them together. Begin by creating a standing joint committee with jurisdiction over the whole technology buildout. Then open the larger debate about a Department of Technology and elected technology leaders at the local, county, state and federal levels, including a Secretary of Technology.

    Two rules for all 100 days

    • No riders. Questions as large as federal preemption of state AI laws should not be decided inside a defense or budget bill. They need their own hearings and their own text.
    • Settle the hard disagreements early. The last Congress’s one bipartisan success stalled because the central dispute surfaced a few weeks before Election Day.

    The case against our case

    A fair agenda includes the strongest objections.

    • It is too much, too fast. Skeptics will say five items in 100 days is unrealistic, especially in a Senate that needs 60 votes for most bills. We would rather offer a full list and let members pick; the first two items are the most achievable.
    • Congress has limited reach over local contracts. A federal NDA ban cannot easily dictate how a city signs agreements except through federal funding, permits or land. Developers also argue that confidentiality protects competitive information, and Microsoft has said the agreements were meant to protect sensitive information. The bill’s trade-secret carve-out is where this fight will be decided.
    • Mandatory cost allocation could raise costs or slow building. Supporters of the optional approach worry that rigid federal standards could discourage investment at a moment when the country needs more capacity.
    • Revenue scenarios are speculative. The same New York report acknowledges it is hard to connect today’s hiring trends to AI with certainty. We agree, which is why we ask for a range of scenarios and not a single forecast.

    Start now

    None of this requires a party to give up its principles. It requires members to decide that the question of who is accountable for the technology buildout is theirs to answer. We will keep publishing the evidence and we will tell you plainly when we think a proposal falls short. Our proposal is at department.technology/.

  • Preemption Without an Owner: Why the Federal-State AI Fight Needs Someone Accountable

    By the Founders, Department of Technology | San Diego, California | November 13, 2026

    Washington is arguing over whether federal law should override state AI rules. Both sides have real arguments. But whoever wins, someone has to enforce the result and answer to voters for it, and right now no one does.

    Few questions in technology policy have produced more heat than federal preemption: whether Congress should replace the growing body of state AI laws with a single national standard. This piece does not argue that preemption is right or wrong. We lay out the strongest case on each side, review what the record shows, and make one claim that holds under either outcome: a national standard, or a patchwork, without a named, accountable owner is not a policy. It is a vacuum.

    The case for a national standard

    Supporters of preemption make an argument that deserves a fair hearing. AI development does not stop at state borders, they say, and companies facing dozens of different rules face rising compliance costs that favor the largest firms. In December 2025, a presidential executive order called for a uniform national framework, directed the Justice Department to challenge state laws it deemed onerous, and tied some federal broadband funding to state policy. Industry groups and senators including Ted Cruz have argued for explicit federal preemption of conflicting state laws, and some supporters now say the longer Congress waits, the harder preemption becomes as more state laws pile up.

    In March 2026, the White House sent Congress a national framework that called for preempting burdensome state AI laws, with exceptions for child safety, general consumer-protection and fraud laws, state procurement and state zoning for AI infrastructure.

    The case against

    Opponents make an equally serious argument. States, they say, are closer to the people affected and can respond faster than Congress, and preemption without enforceable federal protections would leave residents with fewer remedies than they have today. The opposition has been broad. In July 2025, the Senate voted 99 to 1 against a proposed state AI moratorium. When it returned in the defense bill, more than 300 state lawmakers from across the political spectrum urged Congress to reject it, and prominent Republicans including Senator Josh Hawley, Representative Marjorie Taylor Greene and Arkansas Governor Sarah Huckabee Sanders spoke against it. The defense bill text did not include the moratorium, and House Republican leaders were left searching for another vehicle.

    What the record shows

    Whatever one thinks of preemption, the practical result so far is a stalemate. Two attempts to attach it to must-pass bills failed. The White House framework has not become law. By one account, Congress left for its August recess without moving a federal AI framework out of committee. Meanwhile, 29 states enacted AI legislation in 2026, and for the first time both Republican- and Democratic-led states passed laws adding requirements or oversight for data centers.

    The states did not wait for permission, and no one in Washington was positioned to tell them to stop or to give them something better to follow.

    The part both sides already agree on

    Here is the detail that gets lost in the argument. Even the strongest preemption proposals carve out data center infrastructure. The December executive order said legislation should not preempt state laws on data center infrastructure, and the March framework would leave state zoning for AI infrastructure in place. In other words, the people who favor the broadest national standard agree that decisions about where data centers go, how they are powered and who pays remain local and state decisions.

    That has a consequence. Whatever Congress decides about model rules, child safety or algorithmic discrimination, the data center decisions that voters care about most, and that voted on November 3, will be made by city councils, county boards, state utility commissions and legislatures. Those officials are making multibillion-dollar decisions with no technology counterpart whose job it is to see the whole picture.

    Where the owner is missing under each outcome

    • If broad preemption passes, a federal standard replaces state rules. Who enforces it, who updates it as the technology changes, and who do residents call when it fails? Without an accountable federal office, critics of preemption are right that residents lose remedies.
    • If preemption fails, the patchwork grows. Companies face rules that differ by state, and states and counties negotiate against the same few buyers with little shared information. Without a coordinating office, supporters of a national standard are right that the burden falls hardest on smaller firms and communities.
    • If a narrow hybrid passes, federal and state authority meet at a boundary that will be contested. Someone has to be accountable for where that boundary sits and for what falls through it.

    In every case, the missing piece is the same: an office that answers to voters for how the system works as a whole.

    Three tests for any national AI standard

    We take no position on how broad preemption should be. We do suggest three tests for any proposal, from any party:

    1. Is the federal protection enforceable? If a national standard replaces state rules, it should carry real enforcement and clear remedies, not just guidance.
    2. Is there a named, accountable official? Someone should be answerable to voters, and to Congress, for how the standard is administered and updated.
    3. Does it keep data center decisions local and public? Siting, rates and disclosure of public deals should stay with local and state governments, with transparency rules attached.

    And a procedural test: was it debated on its own, with hearings and a public text, instead of inside a must-pass bill?

    The case against our case

    • Accountability can be built into existing agencies. Some will say a regulator or a White House coordinator could play this role without a new elected office. That is a reasonable design, though we think voters should be able to hold someone to account directly.
    • Local decisions are the problem. Some supporters of preemption believe local control over data centers is what slows the buildout, and would prefer more federal permitting authority. The administration has proposed streamlining federal permitting for AI data centers, and reasonable people can weigh that against local consent.
    • It adds a layer. Another layer of officials could slow decisions. We would answer that the status quo already has many layers and no owner, but we welcome the debate.

    The question underneath

    The preemption fight will continue, and we hope it is resolved by open debate and not by rider. But the question underneath it will not go away: when the technology goes wrong, or when it goes right and the gains are not shared, who is responsible? We think the answer should be someone voters can elect, at every level of government. Find our proposal at department.technology/.

  • A Briefing for the New Congress: What the Last Two Years Got Wrong, and What to Do Differently

    By the Founders, Department of Technology | San Diego, California | November 13, 2026

    To the newly elected: you are about to inherit the most consequential technology decisions in a generation, and the last Congress left you a map of what not to do.

    This is not a partisan scorecard. The record we describe below includes members of both parties acting in good faith and members of both parties falling short. Newly elected members of Congress are sworn in this January, and we think you are better served by an honest account of what happened than by a flattering one. We start with what worked.

    What the last Congress got right

    It is easy to say Congress did nothing on data centers. That is not quite true. In July, the House Energy and Commerce Committee passed the Ratepayer Protection Act 52 to 0, a bill from Republican Gabe Evans and Democrat Kathy Castor. In September, the full House passed it 417 to 3 under a procedure that required a two-thirds majority. The bill would require state utility regulators to consider standards that make large data center customers pay the full cost of the grid upgrades built to serve them. In a polarized era, that is a real accomplishment, and it shows what is possible when members start from a problem their constituents can feel: the electric bill.

    Then came the mistakes.

    Mistake 1: Trying to pass the big thing through the back door

    For two years, advocates of a national AI framework tried to move federal preemption of state AI laws by attaching it to must-pass bills. Those efforts, including the defense authorization bill and the 2025 budget reconciliation law, were unsuccessful. Senators rejected a broad preemption proposal 99 to 1. In March 2026, the White House sent Congress a national policy framework that again called for preempting burdensome state laws while carving out areas such as child safety and state zoning for AI infrastructure. By one account, Congress left for its August recess without moving a federal AI framework out of committee.

    The lesson is not that preemption is right or wrong. Reasonable people disagree, and we lay out both sides below. The lesson is that a question this large cannot be settled by rider. It needs its own hearings, its own text and its own public debate.

    Mistake 2: Letting the one agreement become a campaign prop

    The Ratepayer Protection Act did not stall because no one wanted it. It stalled because of how it arrived. On September 30, five weeks before Election Day, the Senate voted 57 to 43 on a procedural motion that needed 60 votes. Only four Democrats voted yes.

    The two sides told different stories, and each has a serious argument:

    • Republican supporters said the bill had passed the House almost unanimously, with Democratic votes and Democratic cosponsors, and accused Senate Democrats of refusing to take yes for an answer for political reasons.
    • Senate Democrats said the bill’s core protection is optional, since states need only consider standards, and offered their own GRID Savings Act to make large customers actually pay for grid upgrades. Senator Schumer called the Republican bill “optional” and toothless.

    We take no side on optional versus mandatory. We do note that Reuters reported Senate Republicans aimed to improve their midterm prospects with the vote, and that the bill arrived at the end of the session, after the Senate had not moved on data centers for months. A measure introduced in July and brought to a test vote in the last weeks before an election will be judged as a campaign move whatever its merits. The practical lesson for new members: if you want a data center bill to become law, negotiate the mandatory-versus-optional question in the spring, not the fall.

    Mistake 3: Solving one slice of a three-part problem

    Even if the Ratepayer Protection Act had passed, it would have addressed one of three risks we described in our earlier piece, “The Data Center Casino.” It deals with who pays for grid upgrades. It does not address how fast we can build power to compete with China, the financial exposure if the AI investment boom turns, or what happens to federal and state revenue if AI displaces high-paid white-collar work. Congress legislated the slice that polls well. No committee is responsible for the whole.

    Mistake 4: Leaving a vacuum for states and for secret local deals

    When Congress does not act, others do. In 2026, 29 states enacted AI legislation, and for the first time both Republican- and Democratic-led states passed laws adding requirements or oversight for data centers. That is encouraging, and it is also a patchwork. Meanwhile, at the local level, many deals are still negotiated under non-disclosure agreements. As we noted in our open letter, 25 of 31 Virginia local governments involved in data center development had signed NDAs. Residents learn about the largest infrastructure project in their county after the decision is made.

    Mistake 5: Nobody owns it

    This is the mistake underneath the others. AI, data centers, the power grid, student data, surveillance and the workforce are governed by a patchwork of committees and agencies. Each handles a slice, and no one is accountable to voters for how the slices fit together. We raised this directly. In February 2025 we submitted a proposal to the White House Office of Science and Technology Policy for a national AI action plan, and in July 2025 we published a response to the plan that followed. We have not had a substantive engagement with either. We mention it not as a complaint, since a good idea should not depend on one administration, but because it illustrates the structural problem: there was no office whose job it was to say yes or no.

    What new members can do in the first 100 days

    1. Hold hearings on the whole picture. Grid capacity, public cost, competitiveness and fiscal impact together, with the same witnesses in the same room.
    2. Settle optional versus mandatory early. Bring Republicans and Democrats who both voted for ratepayer protection into one room and write the version that can reach 60 votes.
    3. Keep big structural questions out of must-pass bills. Preemption, if it happens, should be debated on its own.
    4. Open the deals. Require public disclosure of data center agreements that involve public land, public utilities or public incentives.
    5. Create a single point of accountability. At minimum, a standing joint committee with jurisdiction over the whole question. Ideally, an elected technology leader at every level of government, including a Secretary of Technology at the federal level, whose job is to answer to voters for the combination.

    The case against our case

    A fair briefing includes the strongest objections.

    • Preemption advocates argue a patchwork of state laws slows innovation and that national competitiveness requires one national standard, and they note that the longer Congress waits, the harder preemption becomes as states pass more laws (Broadband Breakfast). Opponents respond that preemption without enforceable federal protections would leave residents with fewer remedies.
    • Optional standards may be the right design. Supporters of the Ratepayer Protection Act argue that utility regulation has long been a state responsibility and that a federal mandate would overreach. Critics respond that voluntary pledges have not been enough.
    • Congress already has committees for this. Some will say the problem is political will, not structure, and that a new office adds a layer. Our view is that structure shapes will: when every committee owns a slice, no one is blamed for the whole. But we welcome the argument.

    The first step

    The new Congress does not need to solve everything in January. It needs to stop treating the central question, who is accountable for the technology buildout, as someone else’s job. Start the conversation about a Department of Technology and elected technology leaders at every level. We will help, and we will be honest with you when we think you are wrong. Find our proposal at department.technology/.

  • Voters Didn’t Reject AI. They Rejected Building It Backward


    By the Founders, Department of Technology | San Diego, California | November 9, 2026


    Voters Didn’t Reject AI in 2026. The ever-increasing number of paid memberships for OpenAI, Anthropic (Claude AI), Google Gemini, and others has proved this to be the case.

    They Rejected Building It Backward.

    On November 3rd, voters across ten states said no to data centers almost every time they were asked. The reason is not that they oppose AI. It is that they have watched the buildout run ahead of the power grid, and they suspect the people steering it are not putting the public first.

    In Ashville, Ohio, the village council had already approved an agreement with a data center developer. Residents petitioned to put it on the ballot anyway. On Election Day, 82% of voters rejected the deal, according to Northeast Ohio reporting by Fox 8.
    Ashville was not an outlier. Ballotpedia counted 41 local data center measures on the November 3rd ballot across 10 states, with Ohio accounting for 21. Voters favored limiting data center development in 40 of the 41. The one exception was Harwood, North Dakota, where voters defeated a proposed review requirement. Voters in Granville, Ohio, approved a ban by 84%. In Urbana, 77% backed one.

    This was not a one-day mood. A Heatmap poll reported by Forbes found more than 70% of Americans would oppose a data center planned for their area, with rising electricity prices the top reason.
    Many voters may not weigh how much national AI leadership depends on new computing capacity. That is a fair criticism, and we take it seriously below. But the voters who showed up made a different judgment, and it deserves a hearing: they believe this buildout is being driven first by profit, with national strategy a distant second, and that their concerns about power bills and the environment were treated as obstacles rather than inputs.
    The comparison with China shows why that suspicion is not irrational.

    What China Did First
    China and the United States are in a race for AI leadership, but they are not running it from the same starting line.
    According to Inside Climate News, China added an estimated 540 gigawatts of generating capacity in 2025, more than 80% of it renewable. The United States added about 54 gigawatts, roughly 60% renewable. Al Jazeera reports that China already generates more than twice as much electricity as the US, and that BloombergNEF expects China to add more than six times as much generating capacity over the next five years.

    Transmission, the high-voltage lines that carry power from where it is made to where it is used, tells the same story. Grid Strategies estimates the US needs roughly 5,000 new miles of high-capacity transmission per year but has averaged only about 600 since 2017, according to Yale Climate Connections. China, by the same report, has been building over 1,000 miles of ultra-high-voltage lines per year. In January, China’s State Grid announced a CNY 4 trillion (about $580 billion) investment plan for 2026 to 2030, up 40% from the prior plan, including 15 new ultra-high-voltage lines, according to Enerdata.

    Getting connected is the other bottleneck. A ChinaTalk analysis finds that the time for a US generation project to connect has grown from under two years in the early 2000s to over four years for projects built from 2018 to 2024. Because China plans generation, transmission, and demand together under state direction, the American concept of a years-long interconnection queue for large loads barely exists there.

    The US leads on the other side of the equation. Stanford’s AI Index counts an estimated 5,427 US data centers in 2025 versus 449 in China. As one analyst quoted by Al Jazeera framed it, the US has the chips and is short on power, while China has the power and is short on chips.

    Cost is where the picture gets less lopsided. Reporting from bne IntelliNews puts Chinese industrial electricity rates roughly in line with the US, at about $0.08 to $0.11 per kilowatt-hour, while Chinese households pay about $0.08 versus $0.15 to $0.17 for American households. The Financial Times reported that Beijing is subsidizing power for data centers using domestic chips down to about 5.6 cents per kilowatt-hour, against a US industrial average of 9.1 cents.

    The Warnings Were Public
    Here is the part voters understand best. The power shortfall was not a secret.

    In its Long-Term Reliability Assessment, the North American Electric Reliability Corporation (NERC) raised its ten-year summer peak demand forecast sharply and said new data centers account for most of the projected growth, with several regions at high risk of supply shortfalls by the end of the decade. This spring, NERC issued a Level 3 alert, its highest tier, over large computational loads like data centers, and found that grid operators cannot reliably model how 77% of operating data center load behaves during grid disturbances, according to reporting by SAN and Utility Dive.

    Grid operators are also being overwhelmed at the front door. Texas’s ERCOT built its process for a large-load queue of 40 to 50 projects, then received 225 new interconnection requests in 2025 alone, about 70% of them data centers, according to the Texas Tribune. ERCOT itself cautions that many requests are speculative and its demand forecast is probably inflated. That caution cuts both ways: it means some projects may never be built, and it also means officials are approving and planning against numbers nobody can fully trust.
    We want to be precise. We are not claiming that officials privately concealed a known shortfall. What the public record shows is that independent grid reliability authorities published escalating warnings, and in many places projects advanced anyway, sometimes under nondisclosure agreements and sometimes over local objections. When voters see that sequence, and then see their bills, they draw a conclusion.

    Why the Bill Concern Is Real, and Why It Is Contested
    The electricity price argument is the most contested part of this debate, so it deserves care.

    In PJM, the grid operator serving 13 states and Washington, DC, capacity auction prices rose from $28.92 per megawatt-day for 2024/25 to $329.17 for 2026/27, roughly tenfold. PJM’s independent market monitor attributed 63% of the increase in the 2025/26 auction to data center demand, about $9.3 billion in added costs recovered from ratepayers, according to analysis by the Institute for Energy Economics and Financial Analysis.
    But capacity charges are only about 10% to 20% of a typical bill, as FactCheck.org notes, and several studies find no clear nationwide link between data centers and household rate increases. A Rutgers policy lab analysis found no statistically significant local bill effect yet, while warning that “not yet” is not the same as “nothing to worry about.” FactCheck.org also cites an estimate that capacity increases added about $18 per month to the average home bill in western Maryland and $16 in Ohio between mid-2025 and mid-2026, with 63% of that tied to data centers.

    The honest summary: the bill effect is real and documented in some regions, overstated in others, and likely to grow if the cost-allocation rules do not change. Voters are reacting to the direction of travel, and the direction is up.

    “Doesn’t Slowing Down Hand China the Win?”
    This is the strongest objection, and it is not frivolous. If China is building power at this scale and pricing it for AI, then any delay in the US could cost real strategic ground.

    But the China comparison cuts against the current approach, not for it. The binding constraint on American AI is no longer chips alone. It is power, transmission, and public consent, and the backlash of November 3rd shows what happens when a project skips the last of those. Projects imposed on unwilling towns get voted down, and every vote down is a delay no strategist planned for.

    We also want to avoid the lazy conclusion that the US should copy Beijing. China’s model rests on centralized, state-directed planning that the US system, with its many jurisdictions and its commitment to local consent, cannot and should not replicate. China’s buildout has its own costs: Oxford Institute for Energy Studies notes it added as much as 80 gigawatts of new coal-fired power in 2025, and Al Jazeera reports a gap between China’s data center capacity and how much of it is actually used. The lesson is narrower and more useful: China treats the grid as infrastructure to be built before the load arrives. We have been building the load and hoping the grid catches up.

    The Fix: Grid First, Public Accountability Always
    The way out is not a moratorium on AI infrastructure and not a free pass for developers. It is a different order of operations. The framework at Department of Technology proposes layered accountability: a confirmed federal Secretary of Technology, and elected technology leaders at the state, county, and local level who answer to the voters whose bills and water supply are on the line. Concretely:
    Grid first. No major data center approval without a utility- or grid-operator-certified plan covering power supply, transmission, and interconnection timing.

    Make the large loads pay. Require large-load tariffs so the full cost of new generation and grid upgrades lands on the facilities that cause it, not on residential ratepayers. Pennsylvania’s governor has moved this direction with an executive order requiring developers to build, bring, or buy their own capacity, and a Republican challenger has pressed for a ratepayer-protection moratorium. This is not a one-party issue.

    Publish the grid impact. Before any rezoning or tax abatement, publish projected power demand, water use, and cost allocation in plain language, and limit NDAs on projects that use public land, money, or incentives.

    Fund the wires. Treat transmission and interconnection reform as national AI infrastructure, because it is. If the United States wants to out-build China on compute, it has to stop being out-built on the grid.

    What Each of Us Can Do
    Congress: Prioritize transmission permitting and interconnection reform, and pass transparency rules for large-load projects.
    Statehouses and utility commissions: Adopt large-load tariffs and grid-readiness tests before approvals, and require public notice before rezoning or tax breaks.
    Candidates and local officials: Answer two questions in public. Who pays for the power this project needs? Where is the grid study that says it can be delivered?

    Voters: Ask every candidate those same two questions, at every level, before the next ballot.

    The Choice
    The United States can win the AI race, but not by asking communities to host the buildout on faith. China’s advantage is not that it has better engineers. It is that it built the power first. If we want national AI leadership, we have to earn it the way voters just demanded: build the grid, make the costs transparent, and put people accountable to the public in charge of the decisions.

    Summary
    Voters in 40 of 41 local data center ballot measures on November 3rd chose limits, and polls show most Americans oppose a data center near them. The backlash is not a rejection of AI. It reflects a buildout that outran the grid, a shortfall that grid reliability authorities publicly warned about, and a bill impact that is real in some regions and contested in others. China built power and transmission first, at a scale and speed the US has not matched, though its model is not one we should copy. The answer is to put the grid first, make the large loads pay, and make the decisions accountable to the people who live with them.
    Sources

  • America Won’t Lose the AI Race to China’s Chips. It Will Lose It to Distrust.

    Voters have already rejected data centers at the ballot box in 2026. The officials building this infrastructure are still hiding deals and holding stakes in the companies they oversee.

    Last week, on November 3rd, 2026, voters delivered a verdict on the AI buildout. They weighed nearly 40 data center-related ballot measures across 10 states, and in Edgewater, Florida, over three-quarters of voters approved a ban on new data centers. This week, ProPublica reported that our United States Secretary of the Interior, Doug Burgum is leading the push to put data centers on public lands while holding between $18.1 million and $64.4 million in AI-company investments, according to an analysis by the advocacy group Save Our Parks.

    Our United States Secretary of the Interior, Doug Burgum says any suggestion that his decisions are driven by personal investments is false. But lawyers told ProPublica his holdings appear to be acceptable under current law. That is the real scandal. If an official can steer national AI policy while holding a stake in the industry he is steering, the problem is the law, not just the official.

    The argument of this piece is simple: America will not lose the AI race to foreign chips. America will lose it to its own distrust, unless the people building our AI infrastructure are accountable to the people who live next to it.

    A Lead That Depends on Power and Public Trust

    The United States still dominates the hardware and capital side of AI. Global data center capacity is projected to grow by 97 GW between 2026 and 2030, effectively doubling, and that buildout could require $3 trillion in investment. China, meanwhile, is closing the capabilities gap and training a large share of the world’s AI researchers.

    Chips are no longer the binding constraint. Energy and public consent are. BloombergNEF estimates a 63 GW gap between what AI chip shipments imply the U.S. should build by 2033 and what energy constraints will allow. A country that cannot power its data centers, or persuade its citizens to host them, will not win this race.

    Washington DC Has Not Built the Grid

    AI is, at bottom, a question of electricity. A serious national defense strategy would fast-track nuclear baseload, advanced renewables, and modernized transmission lines. Instead, Congress has taken only minimal steps to regulate these facilities, and the cost is landing on aging local utility systems and the people who pay for them.

    The Backlash Is Rational

    Gallup found that 71% of Americans oppose an AI data center in their local area, including 48% who are strongly opposed. A later Heatmap Pro poll put strong support at just 4%, down from 13% a year earlier. This is not simple NIMBYism. A majority of Americans, 59%, expect their electricity bills to rise if a data center opens nearby, and these facilities also draw heavily on local water and grid capacity.

    When officials answer this with dismissal, they deepen the problem. Burgum has blamed the mass rejection of data centers on a foreign psyop. Calling public worry about bills and water a foreign plot cannot win the cooperation of the communities that must host the infrastructure of national power.

    Secrecy and Self-Dealing

    Consider Tucson, a drought-stricken city. Amazon Web Services and a developer spent nearly two years negotiating a $3.6 billion, 290-acre data center campus behind NDAs, keeping the public in the dark about projected water usage. Residents learned the details only after the deal was largely set.

    Tucson is not unusual. In Virginia, 25 of 31 local governments involved in data center development had signed NDAs. In Louisiana, records requests found at least 54 NDAs signed by elected officials. This is the pattern we warned about in our analysis of America’s AI Action Plan: data centers sited without local democratic input.

    The conflicts reach the top, too. ProPublica’s database shows more than 320 members of our Trump administration have ties to Alphabet, with large numbers also tied to Nvidia and Meta. Our Secretary of the Interior, Doug Burgum pledged to divest many of his AI investments, but not his stake in Titan Development, a real estate firm that has handled land acquisitions for data centers in the Southwest. And the administration has not completed any environmental reviews for data centers on public lands.

    This is not a one-party problem, and the rules must not be one-party rules. The standards proposed here should apply to every official in every administration, including all members of Congress, the White House and others.

    Reform is starting. Lawmakers in at least ten states have introduced bills to restrict or ban these NDAs, Pennsylvania’s governor has barred them for agencies under his control, and a bipartisan federal bill, the No Secrets for Data Centers Act, would void NDAs signed by officials acting in their official capacity. Industry has a defense: one developer says NDAs protect officials from insider-trading exposure, since a planned campus can count as material non-public information. That argues for narrow disclosure rules and a limited carve-out for genuine trade secrets. It does not justify blanket secrecy over water, power, and tax breaks.

    “Won’t Rules Slow Us Down?”

    The strongest objection is that accountability will slow the buildout and hand China an advantage. The opposite is closer to the truth. Projects imposed on unwilling communities are the ones being voted down, and secrecy is what turns a zoning question into a ballot-box revolt. Transparency is how projects survive.

    The Fix: Accountability at Every Level

    Our AI strategy is currently shaped by appointed officials, zoning boards, and “AI czars” who answer to executives rather than voters. The framework at Department of Technology proposes a permanent Department of Technology with layered accountability:

    • Federal: a cabinet-level Secretary of Technology, nominated by the President and confirmed by the Senate. That gives one accountable official real authority over national AI policy, cybersecurity, and digital infrastructure, with a public confirmation process where conflicts must be disclosed and divestment pledges can be tested.
    • State, county, and local: elected technology leaders. They face voters, and they would decide questions like whether a data center goes up beside a reservoir.

    An elected state secretary of technology or county technology commissioner cannot easily hide behind a corporate NDA when residents are looking at their utility bills and voting on the next term. A federal Secretary who is vetted, confirmed, and held to strict divestment rules would have far less room to wave away grid concerns.

    As we argued in Stop the Litigation Loop, a national AI strategy works best when elected state and local partners help carry it out. Elected officials can be conflicted too, so the office needs disclosure and divestment rules from day one.

    Four Legal Changes, Now

    1. Treat AI infrastructure as defense infrastructure. Foundational models, sovereign compute clusters, and their dedicated power supply should be formally classified as critical to national defense.
    2. Create an AI conflict-of-interest offense, modeled on war profiteering law. Criminalize officials trading stock, holding options, or receiving deferred compensation from AI companies bidding on or serving federal defense and intelligence contracts, including public land leases, where the official has authority over those decisions. Provide a safe harbor for diversified index funds and qualified blind trusts, so the rule targets real conflicts rather than ordinary retirement savings.
    3. Ban NDAs on public-interest infrastructure. Void any NDA that binds public officials or covers projects using public funds, land, or incentives, with a narrow carve-out for real trade secrets.
    4. Require divestment as a condition of office. Anyone overseeing technology, public lands, or energy policy, including the proposed Secretary of Technology, should divest direct holdings in AI and tech companies before taking office. Violations should be prosecuted as threats to national defense, not settled with ethics fines.

    What Each of Us Can Do

    • Congress: pass the No Secrets for Data Centers Act and adopt divestment rules that cover both parties.
    • Statehouses: enact NDA bans like those introduced in at least ten states, and require public notice before any rezoning or tax abatement for a data center.
    • Voters: ask every candidate, at every level, two questions. Will you divest from AI and tech holdings while in office? Will you refuse NDAs on projects that use public land, money, or water?

    The Choice

    Our adversaries will not be stopped by a nation whose officials hold stock in the contractors they oversee, hide deals from the towns that host them, and brush off voters’ concerns about their own bills. To win the algorithmic cold war, we have to build the grid and earn public trust. We also have to make sure those who write AI policy have no stake in the outcome. The voters have already spoken. Now the law has to catch up.

    Summary

    Seven in ten Americans oppose a data center in their community, and the officials deciding where they go may own a piece of the companies building them.

    Gallup found that 71% of Americans oppose an AI data center in their local area, and last week voters made that opposition official, weighing nearly 40 data center-related ballot measures across 10 states. This week, ProPublica reported that the Interior Secretary, who is pushing to build data centers on public lands, holds between $18.1 million and $64.4 million in AI-company investments, according to an analysis by the advocacy group Save Our Parks.

    Interior disputes the characterization, and lawyers told ProPublica the holdings appear to be acceptable under current law. That last part is the heart of our new article; America Won’t Lose the AI Race to China’s Chips. It Will Lose It to Distrust, which argues that our race will be decided by the power grid and public trust as much as by chips, and that trust collapses when local officials sign NDAs that hide water and power costs from their own residents and when officials hold stakes in the industries they oversee.

    This is not a Republican or Democratic problem, and the rules we propose would cover every official in every administration. Imagine being able to see what your town agreed to before the contract is signed, knowing the people overseeing AI and energy policy have no financial stake in the outcome, and having a vote over whether a data center goes up beside your reservoir.

    That future is within reach: lawmakers in at least ten states have introduced bills to restrict or ban these NDAs, and a bipartisan federal bill, the No Secrets for Data Centers Act, would void NDAs signed by officials acting in their official capacity. What the momentum needs is public pressure, and public pressure starts with people knowing what is happening.

    So please share this article today: post it with one sentence on why it matters to your town, send it to your city council member or state legislator, forward it to a neighbor who pays an electric bill, and ask every candidate whether they will divest from AI and tech holdings while in office and refuse NDAs on projects that use public land, money, or water. The voters have already spoken, so help make sure the law catches up at department.technology/.

  • An Open Letter to Every Elected Official in America: Put the Country First

    To the Members of Congress, Governors, State Legislators, County Supervisors, Mayors, and City and Town Council Members of both parties:

    We write as an independent, nonpartisan policy project based in San Diego, California. We belong to no party and take no money from advertisers, PACs, or lobbyists. We are asking for one thing: start the public discussion on establishing a Department of Technology at the local, county, state, and federal levels, as proposed at department.technology/.

    What we did first, and what happened

    We did not begin with an open letter. We began by going directly to the executive branch. In February 2025, the Office of Science and Technology Policy asked the public for input on a national AI Action Plan, and we submitted our proposal by email. When the White House released America’s AI Action Plan in July 2025, we published a response. We welcomed its focus on innovation, infrastructure, and diplomacy, and pointed out the gap in it: no one in the plan is directly accountable to the American people for how it gets carried out.

    Those efforts have not led to any engagement with our proposal. We hold no grudge about that. A good idea should not depend on one administration. It has to be able to survive from one administration to the next, which is why we are now writing to all of you.

    Why this can’t wait

    Technology is no longer a niche subject. It is a daily political reality in your districts.

    We are not raising these points to attack any person or party. The pattern would be a problem under any administration, and the rules we propose cover every official, including every member of Congress.

    AI, data centers, surveillance, student data, autonomous systems, and the power grid are being governed by a patchwork of agencies and appointed officials, with no one in charge and often no one voters can hold accountable.

    What we propose

    A Department of Technology with layered accountability:

    • Federal: a cabinet-level Secretary of Technology, nominated by the President and confirmed by the Senate. That gives the country one accountable official for national AI policy, cybersecurity, and digital infrastructure.
    • State, county, and local: elected technology leaders, so the people deciding how technology is used in your community answer directly to the people who live there, much as an attorney general or district attorney does.

    The full proposals are public and free to use: Legal Guidelines for a Federal Department of Technology, Legal Framework for State, County, and Local Departments, a draft California ballot initiative, and our argument for why this is essential to American AI leadership. They are drafts, offered for debate, and we welcome amendments.

    What we are asking you to do

    You don’t have to agree with every detail. We are asking you to begin the conversation:

    1. Hold a public hearing or town hall on how technology is governed in your jurisdiction and who is accountable for it.
    2. Introduce a resolution calling for study of a Department of Technology, as proposed by us at www.department.technology, at your level of government.
    3. Adopt two interim safeguards now, whichever way the larger debate goes: a ban on NDAs for projects using public funds, land, or incentives, and disclosure and divestment rules for officials who oversee technology, energy, and public lands. A bipartisan federal bill, the No Secrets for Data Centers Act, would void NDAs signed by officials acting in their official capacity, and lawmakers in at least ten states have introduced bills to restrict or ban these NDAs.
    4. Tell us where you stand. If you will support the discussion, or if you have objections, to a Department of Technology, as proposed by us at www.department.technology, we want to hear them and will publish your response with your permission.

    A request across party lines

    This is not a Republican idea or a Democratic idea. Voters in both parties oppose secrecy around local projects, want their utility bills protected, and want to know that the people steering technology policy answer to them. Whoever holds power next year or in ten years will inherit the same questions.

    We are asking you to put the country’s interests ahead of party interests and start this discussion in the open, where voters can take part.

    Respectfully,

    The Founders, Department of Technology
    San Diego, California
    department.technology/

  • How a Future Department of Technology Will Transform Technology Audits: A Vision for Accountability and Efficiency

    In an era where technology is the backbone of government operations, the establishment of a future Department of Technology (DoT), as advocated for at department.technology/, represents a pivotal step towards ensuring transparency, accountability, and security in public technology management. This vision includes implementing comprehensive technology audits that address key areas critical to effective governance. Here’s how an elected and accountable DoT would tackle these audits to serve voters and taxpayers better.

    Who Will Conduct These Audits?

    The audits will be conducted by specialized teams within the Department of Technology, staffed by experts in finance, technology, compliance, and risk management. These teams will operate under the oversight of elected officials who are accountable to the public. By having elected representatives involved, the process ensures that the audits reflect the priorities and concerns of voters, providing an additional layer of accountability.

    What Are the Key Areas of Audit?

    1. Budget Allocation: Reviewing how funds are allocated to technology projects and systems.
    2. Procurement Process: Evaluating the purchasing process for hardware, software, and services.
    3. Cost Efficiency: Assessing the cost-effectiveness of technology purchases and upgrades.
    4. Licensing: Checking compliance with software licenses and managing licensing issues.
    5. Asset Management: Tracking and maintaining technology assets efficiently.
    6. Return on Investment (ROI): Measuring the benefits and savings from technology investments.
    7. Vendor Management: Assessing vendor performance and contract adherence.
    8. Compliance and Regulatory Oversight: Ensuring adherence to legal and regulatory standards.
    9. Inventory Control: Managing technology asset inventory levels.
    10. Maintenance and Support Costs: Reviewing ongoing maintenance and support expenses.
    11. Depreciation Tracking: Monitoring asset depreciation to plan replacements.
    12. Risk Management: Identifying and mitigating technology-related risks.
    13. Cost Allocation: Ensuring accurate cost distribution across departments and projects.

    When Will These Audits Be Conducted?

    Audits will be carried out on a regular schedule, with key areas assessed annually to ensure ongoing oversight and timely action. Additionally, ad-hoc audits may be initiated in response to significant changes in technology use, major projects, or emerging issues. This approach provides both routine checks and responsive measures to maintain high standards of technology management.

    Where Will the Audits Take Place?

    The audits will encompass all levels of government operations that utilize technology—from local municipal offices to state agencies and federal departments. By conducting audits across the board, the DoT ensures comprehensive oversight and identifies areas for improvement throughout the government’s technology landscape.

    Why Are These Audits Crucial?

    Technology audits are vital for several reasons:

    • Transparency: They provide a clear view of how taxpayer dollars are spent on technology, promoting openness and trust in government operations.
    • Accountability: By evaluating processes and expenditures, audits hold government entities accountable for their technology management practices.
    • Security: Regular audits help identify and address security vulnerabilities, ensuring that technology systems are protected against risks and threats.
    • Efficiency: They ensure that technology investments deliver value and support the effective functioning of government services.

    How Will the Audits Be Conducted?

    1. Budget Allocation: The DoT will review financial reports and project budgets to ensure funds are allocated effectively and align with strategic goals.
    2. Procurement Process: Auditors will examine procurement records, contracts, and vendor selection processes to ensure compliance with policies and competitive pricing.
    3. Cost Efficiency: The DoT will assess cost reports and performance metrics to verify that technology investments are yielding expected benefits and savings.
    4. Licensing: Compliance with software licenses will be verified through audits of licensing agreements and usage records.
    5. Asset Management: Technology assets will be tracked and assessed for maintenance and replacement needs through inventory management systems.
    6. Return on Investment (ROI): The impact of technology investments will be evaluated using performance data and benefit analyses.
    7. Vendor Management: Vendor performance will be reviewed through contract compliance checks and performance evaluations.
    8. Compliance and Regulatory Oversight: Audits will ensure that technology operations adhere to legal and regulatory requirements through policy reviews and compliance checks.
    9. Inventory Control: Inventory records will be examined to prevent excess or shortages and ensure proper asset management.
    10. Maintenance and Support Costs: Ongoing expenses for maintenance and support will be analyzed to ensure they are necessary and cost-effective.
    11. Depreciation Tracking: Depreciation of assets will be monitored to manage lifecycle costs and plan for replacements.
    12. Risk Management: Risks associated with technology will be identified and mitigated through risk assessments and management plans.
    13. Cost Allocation: Costs will be accurately allocated to benefiting departments or projects through detailed financial tracking and reporting.

    By implementing these audits, the future Department of Technology will enhance government efficiency, ensure responsible use of taxpayer funds, and safeguard the security and integrity of public technology systems. This commitment to transparency, accountability, and security will foster greater public trust and contribute to a more effective and responsive government.

    Scenarios

    Scenario Series for Technology Audits with and without a Department of Technology (DoT)

    1. Budget Allocation

    With DoT:
    Context: The county government allocates a significant budget for a new cybersecurity initiative.
    Scenario: The DoT reviews financial reports and project budgets, finding that funds were misallocated. This leads to a reallocation of resources to ensure proper investment in cybersecurity, aligning with strategic goals and legal requirements.

    Without DoT:
    Context: The same budget allocation occurs.
    Scenario: Without a DoT, the misallocation goes unnoticed, and funds are diverted to less critical areas. The cybersecurity initiative remains underfunded, resulting in significant security vulnerabilities and potential data breaches, undermining the county’s ability to protect sensitive information and comply with legal security requirements.

    2. Procurement Process

    With DoT:
    Context: The state is procuring a new enterprise resource planning (ERP) system.
    Scenario: The DoT audits procurement records and finds that the ERP system was purchased without competitive bidding. This results in revised procurement practices and ensures compliance with public procurement laws, leading to fair pricing and vendor reliability.

    Without DoT:
    Context: The procurement process is conducted as usual.
    Scenario: Without oversight, the ERP system is purchased through a non-competitive process, favoring a less qualified vendor. This results in overpayment, subpar performance, and potential legal challenges for not following procurement regulations, leading to inefficient operations and wasted taxpayer money.

    3. Cost Efficiency

    With DoT:
    Context: The city invests in a new data analytics platform.
    Scenario: The DoT assesses the platform’s performance and finds it has not met expected benefits. The audit leads to optimization recommendations, ensuring the investment delivers the anticipated value and complies with financial management laws.

    Without DoT:
    Context: The investment proceeds without scrutiny.
    Scenario: The platform fails to improve data analysis capabilities, resulting in wasted funds and missed opportunities for operational efficiency. The lack of oversight leads to inefficient spending and a failure to meet legal requirements for cost-effective public investments.

    4. Licensing

    With DoT:
    Context: A municipal office uses various software applications.
    Scenario: The DoT conducts a licensing audit and finds discrepancies in compliance. Corrective actions are taken to align with licensing agreements, avoiding legal penalties and ensuring proper software use.

    Without DoT:
    Context: Licensing practices continue unchecked.
    Scenario: The organization uses software beyond its licensing terms, risking legal action for non-compliance. The lack of oversight results in potential legal penalties and financial liabilities, damaging the organization’s reputation and wasting taxpayer funds.

    5. Asset Management

    With DoT:
    Context: The county manages its fleet of computers and servers.
    Scenario: The DoT performs an asset management audit and discovers outdated technology not properly tracked. Recommendations lead to improved inventory management and maintenance, ensuring compliance with asset management laws and optimizing resource use.

    Without DoT:
    Context: Asset management continues as usual.
    Scenario: Outdated and untracked technology remains in use, leading to inefficiencies and increased operational costs. The lack of oversight results in unnecessary expenditures and potential legal issues related to inadequate asset management practices.

    6. Return on Investment (ROI)

    With DoT:
    Context: The state invests in a cloud-based storage solution.
    Scenario: The DoT evaluates the ROI and finds that expected benefits are not being realized. The audit leads to a re-assessment of the investment, ensuring it meets legal standards for ROI and delivers value.

    Without DoT:
    Context: The investment is implemented without review.
    Scenario: The cloud storage solution fails to provide the anticipated benefits, leading to wasted funds and inefficiencies. Without oversight, the investment does not align with legal requirements for ROI, resulting in poor fiscal management and lost opportunities for cost savings.

    7. Vendor Management

    With DoT:
    Context: The city contracts with a technology service provider for IT support.
    Scenario: The DoT reviews the vendor’s performance and finds non-compliance with contract terms. Improved vendor management practices are implemented, ensuring legal compliance and better service.

    Without DoT:
    Context: Vendor management is left unmonitored.
    Scenario: The vendor fails to meet service levels, resulting in poor IT support and potential disruptions. The lack of oversight leads to contractual disputes and inefficiencies, impacting city operations and failing to meet legal standards for service delivery.

    8. Compliance and Regulatory Oversight

    With DoT:
    Context: A federal agency implements a new data privacy system.
    Scenario: The DoT audits the system for compliance with data protection regulations. Gaps are identified and corrected, ensuring adherence to legal requirements and protecting sensitive data.

    Without DoT:
    Context: The system is implemented without audit.
    Scenario: Compliance gaps remain unaddressed, leading to violations of data protection laws and potential breaches of sensitive information. The lack of regulatory oversight results in legal consequences and compromised data security.

    9. Inventory Control

    With DoT:
    Context: The state manages a large inventory of software licenses and hardware.
    Scenario: The DoT examines inventory records and finds discrepancies. Improved inventory tracking systems are implemented, ensuring compliance with legal requirements and efficient asset management.

    Without DoT:
    Context: Inventory management continues without oversight.
    Scenario: Discrepancies in inventory records lead to excess hardware and software shortages. Inefficient asset management results in waste and potential legal issues related to inaccurate inventory practices.

    10. Maintenance and Support Costs

    With DoT:
    Context: The city incurs regular maintenance expenses for its IT systems.
    Scenario: The DoT reviews these costs and identifies unnecessary expenditures. Reassessment of maintenance contracts and support costs ensures compliance with legal standards for cost-effectiveness and fiscal responsibility.

    Without DoT:
    Context: Maintenance costs are incurred without review.
    Scenario: Unnecessary and redundant maintenance expenses accumulate, leading to inefficient spending. The lack of oversight results in financial waste and non-compliance with legal requirements for cost-effective public expenditures.

    11. Depreciation Tracking

    With DoT:
    Context: A county manages the lifecycle of its technology assets.
    Scenario: The DoT monitors depreciation and finds assets are not replaced timely. Revised tracking practices ensure legal compliance with asset management laws and proper planning for replacements.

    Without DoT:
    Context: Depreciation tracking is neglected.
    Scenario: Assets are not replaced according to their lifecycle, leading to outdated equipment and inefficiencies. The lack of depreciation management results in higher lifecycle costs and potential legal issues related to asset management.

    12. Risk Management

    With DoT:
    Context: The state implements a new enterprise software solution.
    Scenario: The DoT conducts a risk assessment and identifies potential risks. A comprehensive risk management plan is developed to mitigate these risks, ensuring legal compliance and minimizing operational disruptions.

    Without DoT:
    Context: Risk management is not performed.
    Scenario: Risks such as vendor lock-in and unsupported software go unmanaged, leading to operational issues and potential legal disputes. The lack of risk oversight results in costly disruptions and legal challenges.

    13. Cost Allocation

    With DoT:
    Context: A municipal project involves multiple departments.
    Scenario: The DoT reviews cost allocation and finds inaccuracies. A detailed financial tracking system is implemented to ensure accurate cost distribution, complying with legal requirements for fair financial practices.

    Without DoT:
    Context: Cost allocation is handled without oversight.
    Scenario: Technology costs are inaccurately allocated, leading to financial discrepancies and potential disputes between departments. The lack of oversight results in unfair cost distribution and non-compliance with legal financial management requirements.

  • The Dangers of Unelected Bureaucrats Leading Technology Departments: Why Elected Technology Leaders Are the Logical Choice

    In today’s digital age, where technology is integral to the functioning of government, the leadership of Departments of Technology (DoTs) at the local, county, and state levels is more critical than ever. These departments are tasked with maintaining the digital infrastructure that underpins government operations, safeguarding our personal data, and ensuring the continuity of essential services during crises. However, when unelected bureaucrats are placed in charge of these vital roles, the risks to democracy, civil liberties, and effective governance become significant. The solution lies in electing technology leaders who are directly accountable to the public—a logical and necessary choice to ensure transparency, accountability, and the protection of our Constitutional rights.

    The Perils of Unelected Bureaucratic Control

    The blog post “Ensuring Continuity of Government (COG) Through a Department of Technology: A Collaborative Approach” emphasizes the importance of collaboration, accountability, and transparency in maintaining the continuity of government during emergencies. However, when unelected bureaucrats are in charge of DoTs, several dangers arise that undermine these principles:

    1. Lack of Accountability: As the COG blog post highlights, “Continuity of Government depends on the active engagement of leaders who are directly accountable to the people they serve.” Unelected bureaucrats, however, do not answer directly to the public. This lack of accountability can lead to decisions that prioritize bureaucratic efficiency or internal interests over the needs and rights of citizens, resulting in a disconnect between government actions and public expectations.
    2. Reduced Transparency: The COG blog post stresses that “transparency is a cornerstone of public trust,” and that maintaining open communication is essential for a successful COG strategy. Bureaucratic leadership, however, often operates with less transparency, making it difficult for the public to scrutinize decisions and hold leaders accountable. This opacity can erode trust in government, increase the risk of power abuses, and ultimately weaken the public’s faith in the democratic process.
    3. Concentration of Power: The COG blog post warns against the dangers of power being concentrated in the hands of a few, noting that “collaboration across government agencies is crucial to preventing the centralization of authority.” When unelected officials control key technology-related functions, there is a significant risk of power becoming overly concentrated, which can undermine the checks and balances essential to a healthy democracy. This concentration of power can lead to decisions that are made without sufficient oversight or input from the public, thereby jeopardizing civil liberties.
    4. Inflexibility and Resistance to Change: The rapidly evolving field of technology requires leaders who are adaptable and responsive to new challenges. The COG blog post underscores the importance of “a dynamic and flexible approach to leadership” in ensuring that government operations can continue without interruption. However, bureaucracies are often characterized by rigid structures and resistance to change, which can stifle innovation and prevent timely responses to emerging threats or opportunities. This inflexibility can leave the DoT ill-equipped to handle crises effectively, compromising the continuity of government.

    The Case for Elected Technology Leaders

    Electing technology leaders to head DoTs offers a robust solution to the dangers posed by unelected bureaucratic control. The COG blog post advocates for leadership that is accountable, transparent, and collaborative—all qualities more likely to be found in elected officials. Elected technology leaders bring several advantages that are crucial for effective and democratic management of technology in government:

    1. Direct Accountability: Elected officials are directly accountable to the voters, which ensures that technology leaders must remain attuned to the needs and concerns of the public. As the COG blog post notes, “Accountability to the electorate is a fundamental aspect of ensuring that government actions align with the will of the people.” This direct line of accountability ensures that decisions made by technology leaders reflect the public’s interests, rather than the preferences of a detached bureaucracy.
    2. Enhanced Transparency: Elected leaders are subject to public scrutiny and are required to operate in a transparent manner. The COG blog post emphasizes that “transparency is vital for building trust in the government’s ability to manage crises effectively.” Elected officials are more likely to maintain open lines of communication with the public, ensuring that the DoT’s actions are clear, justifiable, and aligned with democratic principles.
    3. Checks and Balances: The COG blog post underscores the importance of checks and balances in preventing the abuse of power, stating that “collaboration across different levels of government introduces necessary oversight.” Elected technology leaders introduce an essential layer of oversight, ensuring that the DoT’s operations are balanced with the protection of individual rights and the public good. This system of checks and balances is crucial for maintaining the integrity of the government’s digital infrastructure and safeguarding against potential overreach.
    4. Responsiveness and Adaptability: Elected officials, driven by the need to respond to their constituents, are more likely to be flexible and open to innovation. The COG blog post highlights the need for “a leadership approach that is both responsive and adaptable,” particularly in the face of rapidly changing technological landscapes. Elected technology leaders are better equipped to implement innovative solutions and respond swiftly to new challenges, ensuring that the DoT remains resilient and effective in all circumstances.

    Safeguarding Democracy and Civil Liberties

    The role of a DoT extends far beyond managing digital infrastructure—it involves making decisions that can have profound implications for privacy, surveillance, and the protection of civil liberties. The COG blog post underscores the importance of balancing security with the protection of civil liberties, noting that “government actions must always respect individual rights, even in times of crisis.” Unelected bureaucrats, however, may prioritize efficiency or security over these rights, leading to potential overreach and the erosion of freedoms.

    Elected technology leaders, on the other hand, are more likely to strike a balance between security and privacy, ensuring that the DoT’s actions are aligned with Constitutional values. They are better positioned to advocate for legislation and policies that protect individual freedoms while enabling the government to function effectively in the digital age.

    Summary

    As technology becomes increasingly central to government operations, the leadership of Departments of Technology must be entrusted to individuals who are directly accountable to the public. Unelected bureaucrats, with their lack of accountability and transparency, pose significant dangers to democracy and civil liberties. In contrast, elected technology leaders offer a logical and necessary alternative, ensuring that these critical departments operate transparently, responsively, and aligned with the principles of our Constitution.

    By placing the leadership of DoTs in the hands of voters for elected officials for that specific local, county, and state DoT, we can safeguard our democracy, protect our rights, and build a government that is both resilient and adaptable in the face of technological change. As highlighted in the COG blog post, this approach not only enhances the continuity of government during crises but also ensures that the power of technology is wielded in the best interests of the people.

    Scenarios


    In a near future where technology departments are headed by unelected bureaucrats during critical moments a COG plan is suddenly enacted. The risks will become all too real, as their lack of accountability, transparency, and flexibility will lead to poor decision-making, delayed responses, and ultimately, harm to the public.


    In times of crisis, the absence of elected leadership in technology will result in a government that is ill-equipped to respond swiftly or effectively. The bureaucrats, detached from the people, will struggle to make the right decisions, and the consequences will be dire for our communities.


    Now, envision a different future—one where technology leaders are elected by the people, for the people. These leaders will be directly accountable to their constituents, ensuring that every action taken is in the public’s best interest. They will act with transparency, make swift decisions, and protect our Constitutional rights, especially in times of crisis.


    By choosing to elect technology leaders at the local, county, and state levels, we will secure a future where our government is prepared to handle crises effectively. This decision will safeguard our rights and maintain the trust and confidence of the public. The choice will be clear—electing technology leaders is the path to a safer, more responsive government. Here some hypothetical scenarios what could happen:

    Scenario: Unelected Bureaucrats’ Inflexibility During a Cyber Attack

    Unelected Bureaucrats:
    During a widespread cyberattack on the state’s digital infrastructure, unelected bureaucrats, bound by rigid protocols and slow decision-making processes, fail to respond quickly. They delay the implementation of emergency measures due to bureaucratic red tape and fear of stepping outside their predefined authority. As a result, the attack cripples essential government services, leading to widespread disruption and public unrest. The lack of accountability means that these bureaucrats face minimal consequences for their inaction, further eroding public trust.

    Elected Technology Leaders:
    In contrast, an elected technology leader, driven by the need to protect their constituents and accountable to the public, acts swiftly. They convene an emergency task force, cut through bureaucratic delays, and deploy rapid-response cybersecurity teams. Their decisive actions minimize the damage, restore critical services quickly, and maintain public confidence in the government’s ability to handle crises. The leader’s transparency throughout the process ensures that the public remains informed and reassured.

    Scenario: Bureaucratic Control Hampering Disaster Recovery Efforts

    Unelected Bureaucrats:
    Following a natural disaster that disrupts communication networks, unelected bureaucrats struggle to coordinate the restoration of services. Their lack of direct accountability to the public leads to misaligned priorities, focusing on bureaucratic procedures rather than immediate public needs. The slow restoration of communication networks hinders relief efforts, leaving affected communities without vital information and assistance. The bureaucrats’ inability to adapt to the crisis results in prolonged recovery times and increased public frustration.

    Elected Technology Leaders:
    An elected technology leader, on the other hand, understands the urgency of restoring communication networks and prioritizes direct, actionable steps to do so. They leverage their authority to bypass unnecessary delays, mobilize resources, and work closely with other elected officials to ensure a coordinated response. Their actions enable faster recovery, efficient dissemination of critical information, and enhanced collaboration with local communities, ultimately leading to a more effective and compassionate disaster response.

    Scenario: Power Centralization Leading to Privacy Violations

    Unelected Bureaucrats:
    In the wake of a security threat, unelected bureaucrats, operating with minimal oversight, decide to implement widespread surveillance measures to monitor potential risks. Their approach, driven by a focus on efficiency and security, lacks consideration for privacy rights and civil liberties. The implementation of invasive surveillance technologies without public input leads to significant violations of privacy, sparking public outrage and legal challenges. The centralization of power in the hands of unelected officials exacerbates these issues, as there is no clear mechanism for public accountability.

    Elected Technology Leaders:
    An elected technology leader, aware of the importance of balancing security with civil liberties, takes a more measured approach. They engage with the public, legal experts, and civil rights organizations to develop surveillance measures that are effective yet respectful of privacy. The leader ensures that all actions are transparent, with clear safeguards and oversight in place. By prioritizing both security and civil rights, the elected leader not only addresses the security threat but also maintains public trust and upholds Constitutional values.

    Scenario: Bureaucratic Resistance to Innovation During a Pandemic

    Unelected Bureaucrats:
    During a pandemic, the need for rapid deployment of digital tools to manage public health data becomes apparent. However, unelected bureaucrats, resistant to change and innovation, rely on outdated systems and procedures. Their reluctance to adopt new technologies delays the effective tracking of infection rates and the distribution of vaccines. The slow response leads to higher infection rates, inadequate resource allocation, and widespread public dissatisfaction with the government’s handling of the crisis.

    Elected Technology Leaders:
    In contrast, an elected technology leader, driven by the urgency of the situation and the need to serve the public, champions the rapid adoption of advanced digital tools. They collaborate with tech companies and public health experts to develop and deploy innovative solutions that streamline data management, improve vaccine distribution, and enhance communication with the public. The leader’s proactive approach not only mitigates the impact of the pandemic but also demonstrates the value of adaptable, responsive governance.

    Scenario: Bureaucratic Mismanagement in Emergency Communications

    Unelected Bureaucrats:
    During a major crisis that disrupts traditional communication channels, unelected bureaucrats struggle to manage emergency communications effectively. Their reliance on outdated systems and rigid procedures results in confusion, with conflicting messages being sent to the public. The bureaucrats’ lack of direct accountability means there is little incentive to innovate or improve the communication strategy. The resulting miscommunication exacerbates the crisis, leading to panic and misinformation spreading among the public.

    Elected Technology Leaders:
    An elected technology leader, recognizing the critical importance of clear and consistent communication during a crisis, acts decisively to overhaul the emergency communication system. They implement modern, multi-channel communication strategies that ensure accurate information reaches the public quickly and efficiently. The leader’s transparent and responsive approach helps to calm public fears, provide clear guidance, and maintain order during the crisis, demonstrating the effectiveness of accountable, elected leadership in safeguarding the public’s well-being.

    Scenario: Nuclear Attack – Bureaucratic Paralysis vs. Decisive Elected Leadership

    Unelected Bureaucrats:
    In the event of a nuclear attack on a major city, unelected bureaucrats overseeing the technology department will struggle to coordinate an effective response. Their rigid adherence to outdated protocols will cause significant delays in activating emergency communication networks and deploying radiation monitoring systems. The lack of clear accountability will lead to confusion and miscommunication among agencies, exacerbating the disaster and leading to unnecessary loss of life.

    Elected Technology Leaders:
    In a future where elected technology leaders hold office, they will swiftly coordinate a comprehensive response to a nuclear attack. Understanding the gravity of the situation and their accountability to the public, these leaders will immediately activate emergency communication channels, deploy advanced radiation detection technologies, and ensure real-time information is available to the public. Their transparent and decisive actions will help minimize casualties and maintain public order during the crisis.

    Scenario: Biological Attack – Slow Bureaucratic Response vs. Proactive Elected Leadership

    Unelected Bureaucrats:
    During a biological attack involving the release of a deadly pathogen, unelected bureaucrats will hesitate to take immediate action due to their reliance on slow-moving government procedures. The delayed deployment of digital health monitoring systems and communication platforms will allow the pathogen to spread unchecked. The bureaucrats’ lack of flexibility and direct accountability will hinder their ability to adapt to the rapidly evolving crisis, resulting in widespread panic and loss of life.

    Elected Technology Leaders:
    With elected technology leaders at the helm, the response to a biological attack will be swift and effective. Recognizing their responsibility to protect the public, these leaders will immediately implement advanced digital health surveillance systems, coordinate with healthcare providers, and ensure that accurate information is disseminated to the public. Their proactive approach will help contain the spread of the pathogen, protect public health, and restore confidence in the government’s ability to manage the crisis.

    Scenario: Chemical Attack – Ineffective Bureaucratic Coordination vs. Efficient Elected Leadership

    Unelected Bureaucrats:
    In the aftermath of a chemical attack on a densely populated area, unelected bureaucrats will struggle to manage the crisis due to poor coordination between agencies. Their focus on bureaucratic procedures rather than immediate action will delay the deployment of chemical detection technologies and the dissemination of evacuation orders. The resulting chaos will lead to unnecessary exposure to the chemical agents, causing mass casualties and long-term environmental damage.

    Elected Technology Leaders:
    Elected technology leaders will respond to a chemical attack with precision and urgency. Fully aware of the need for coordinated action, they will quickly deploy advanced chemical detection systems, work closely with emergency responders, and ensure that the public is informed and evacuated promptly. Their efficient handling of the crisis will minimize exposure, save lives, and reduce the long-term impact on the environment.

    Scenario: Radiological Attack – Bureaucratic Mismanagement vs. Responsive Elected Leadership

    Unelected Bureaucrats:
    In the event of a radiological attack involving the dispersal of radioactive material, unelected bureaucrats will face challenges in managing the situation effectively. Their reliance on outdated communication systems and slow decision-making processes will prevent timely warnings and guidance from reaching the public. The bureaucrats’ inability to act decisively and their lack of direct accountability will lead to widespread radiation exposure, public fear, and a breakdown in trust in government institutions.

    Elected Technology Leaders:
    Elected technology leaders will take immediate action in response to a radiological attack. Understanding their responsibility to safeguard public safety, they will quickly deploy radiation detection technologies, ensure that accurate information is communicated to the public, and coordinate with local and federal agencies to manage the crisis. Their responsiveness and clear communication will help contain the threat, protect public health, and maintain confidence in the government’s ability to manage such emergencies.

    Scenario: EMP Attack – Bureaucratic Inaction vs. Strategic Elected Leadership

    Unelected Bureaucrats:
    In the aftermath of an electromagnetic pulse (EMP) attack that cripples the power grid and communication networks across a large region, unelected bureaucrats will struggle to respond effectively. Their reliance on pre-existing protocols, which were not designed for such a catastrophic event, will lead to paralysis and inaction. The bureaucrats’ inability to quickly adapt to the breakdown of critical infrastructure will delay the restoration of power, disrupt emergency services, and leave millions of citizens without access to vital information. The lack of clear accountability will exacerbate the situation, leading to widespread confusion, fear, and potential civil unrest.

    Elected Technology Leaders:
    Elected technology leaders, fully aware of their responsibility to the public, will take swift and decisive action in response to an EMP attack. Understanding the gravity of the situation and their direct accountability to the people, they will immediately mobilize resources to restore critical infrastructure, deploy alternative communication networks, and ensure that emergency services are coordinated effectively. Their strategic leadership will prioritize the rapid deployment of backup power systems and the use of innovative technologies to reconnect isolated communities. Through clear, transparent communication, these leaders will keep the public informed, maintain order, and work tirelessly to restore normalcy, ensuring that the government remains functional and responsive even in the face of such a devastating crisis.

  • Potential Scenarios Where the AI Whistleblower Protection Act Would Work at Municipal, County, State, and Federal Levels

    In today’s rapidly evolving technological landscape, artificial intelligence (AI) plays a pivotal role in shaping various aspects of our society. However, as AI becomes increasingly integrated into our daily lives, the potential for misuse, bias, and ethical violations grows. The AI Whistleblower Protection Act, as outlined in our blueprint, is designed to safeguard individuals who courageously expose unethical or illegal practices within the AI industry. This blog post will explore potential scenarios where the AI Whistleblower Protection Act would function effectively across different levels of government—municipal, county, state, and federal—highlighting the importance of such protections in maintaining transparency, accountability, and ethical AI development.

    Municipal Level: Ensuring Ethical Use of AI in Policing

    At the municipal level, AI technologies are being increasingly utilized by law enforcement agencies to enhance public safety. From facial recognition systems to predictive policing algorithms, these technologies have the potential to significantly impact communities. However, they also carry risks, particularly concerning bias and discrimination. Imagine a scenario where a city police department implements an AI-driven facial recognition system that disproportionately targets minority communities.

    An AI engineer working for the city identifies this bias and recognizes that the system is violating the Equal Protection Clause of the Fourteenth Amendment. The engineer, protected under the AI Whistleblower Protection Act, reports this issue to the relevant authorities. The Act ensures that the whistleblower is shielded from retaliation, such as job loss or legal threats, and that the city is held accountable for rectifying the bias within the system. This protection encourages transparency and helps to prevent discriminatory practices from taking root in municipal AI applications.

    County Level: Addressing AI Bias in Public Health Services

    Counties often oversee public health services, including the distribution of resources and medical care to underserved populations. AI systems are increasingly being used to allocate these resources efficiently. However, what if an AI system used by a county health department is discovered to be systematically denying care to certain demographic groups based on biased data?

    A public health analyst within the county identifies this flaw and decides to report it. Under the AI Whistleblower Protection Act, the analyst is protected from retaliation, ensuring that they can raise concerns without fear of losing their job or facing legal consequences. The county is then compelled to investigate the issue and take corrective action, ensuring that AI-driven decisions in public health are fair, transparent, and aligned with constitutional principles.

    State Level: Safeguarding Privacy in AI-Driven Surveillance Programs

    At the state level, AI is increasingly used in surveillance programs, including those monitoring public spaces, transportation systems, and even educational institutions. These systems can greatly enhance security but also pose significant privacy risks. Consider a scenario where a state government implements an AI-driven surveillance program that collects and stores vast amounts of personal data without proper oversight.

    A state employee, concerned about potential violations of the Fourth Amendment (protection against unreasonable searches and seizures), decides to report this overreach. The AI Whistleblower Protection Act ensures that the employee’s rights are protected, allowing them to bring attention to the issue without fear of reprisal. The state is then required to review and potentially reform its surveillance practices to align with constitutional protections, thereby safeguarding citizens’ privacy rights.

    Federal Level: Ensuring National Security without Overstepping Constitutional Bounds

    At the federal level, AI technologies are used in various national security applications, from intelligence gathering to military operations. While these applications are crucial for national defense, they also carry the risk of overreach and potential violations of civil liberties. Imagine a situation where a federal agency develops an AI system that unlawfully monitors citizens’ communications under the guise of national security.

    A federal contractor who discovers this unconstitutional practice decides to blow the whistle. The AI Whistleblower Protection Act provides them with the legal protection needed to report the issue to oversight bodies, ensuring that the agency’s actions are reviewed and corrected. This scenario underscores the Act’s critical role in balancing national security interests with the protection of individual liberties, ensuring that AI is used responsibly and within the bounds of the Constitution.

    The Importance of AI Whistleblower Protections Across All Levels of Government

    The AI Whistleblower Protection Act is a vital piece of legislation that ensures ethical AI development and deployment across all levels of government—municipal, county, state, and federal. By providing robust protections for those who expose unethical or illegal practices, the Act fosters a culture of transparency and accountability in the AI industry. It empowers individuals to speak out against injustices and ensures that AI technologies are developed and used in ways that respect constitutional rights and promote the public good.

    For more details on how the AI Whistleblower Protection Act aligns with constitutional principles and why it’s essential for the future of AI governance, check out our comprehensive blog post here.