ICE signed the contract with Compliant Technologies LLC on Wednesday, August 26, 2026, and formally posted the procurement paperwork Thursday, August 27. The award covers the company’s CTG-5 G.L.O.V.E. units, testers, refills, disinfectant, certification, training and support services.

What ICE bought

The procurement package is valued at $16,700,640 and runs for six months. The documents identify Compliant Technologies as the only responsible source ICE found for the specific wearable, direct-contact technology described in the requirement.

The apparent price for an individual glove is $2,495. That figure should not be treated as the total cost per glove or used to describe the entire award as a simple 6,000-unit purchase. The contract also includes support equipment, consumable supplies, training, certification and other services.

The G.L.O.V.E. is designed to deliver electrical pulses through direct contact with bare skin. ICE’s specifications list an operating voltage range of 324 to 362 volts and a maximum voltage limit of 380 volts. The procurement document distinguishes the device from probe-firing systems such as Tasers.

How ICE says it may be used

According to the procurement justification, ICE intends the gloves for enforcement operations, custodial transportation of detainees and civil disturbances around detention facilities. The document refers to situations involving active or passive resistance.

ICE describes the device as a non-lethal conductive distraction and de-escalation tool that could reduce reliance on more severe forms of force. That is the agency’s stated purpose, not an independent finding that the gloves are harmless or medically safe.

The public records establish that ICE bought the equipment. They do not establish that the gloves have been deployed in the field.

Why ICE used a sole-source contract

The procurement justification cites 41 U.S.C. §3304 and the federal exception allowing noncompetitive procedures when only one responsible source can meet the government’s requirements.

ICE says its market research found one open-market source and no comparable product on GSA Advantage. The agency considered alternatives, including Tasers, but concluded they were technically different from the wearable direct-contact system it sought.

That is ICE’s procurement conclusion, not an independently verified finding that no other product could satisfy the agency’s needs.

Senators seek safeguards and limits

Sixteen Democratic senators, led by Sen. Catherine Cortez Masto of Nevada, sent ICE a letter on August 27 questioning the purchase and asking the agency to refrain from deployment until it provides more information.

The lawmakers asked about authorized uses, whether the gloves would be prohibited in crowd-control situations, restrictions involving vulnerable people, training and recurring certification, medical risks and responses, reporting requirements, body-camera activation, supervisory review and independent oversight.

They also asked whether ICE would conduct a limited pilot program before broader deployment and requested records on testing, medical evaluations, risk assessments and internal concerns. The letter asks ICE to provide written responses and documents by September 10, 2026.

Those requests highlight what remains unclear in the publicly available procurement records: the final operational rules governing authorization, warnings, duration and repetition of shocks, medical evaluation, documentation, body-camera use and public reporting.

What happens next

The contract has been awarded and remains in place unless ICE changes course or takes another action. The next public milestone is the senators’ September 10 response deadline.

For taxpayers, the immediate issue is the scope of the six-month package: 6,000 electrical-shock gloves plus the equipment, supplies and services needed to certify and operate them. For detainees, officers and the public, the central unanswered question is how ICE will limit and document their use, particularly in transportation and civil-disturbance settings.

Sources

• ICE procurement justification for the G.L.O.V.E. contract
• Associated Press report on ICE’s electric-shock glove contract
• Sen. Catherine Cortez Masto’s August 27 letter to ICE

U.S. District Judge Rita Lin of the Northern District of California found that the government violated Anthropic’s First Amendment rights, denied the company required Fifth Amendment due process and acted unlawfully under the Administrative Procedure Act.

The order, filed August 27, 2026, says the Pentagon’s supply-chain-risk designation was contrary to the governing statutory scheme and arbitrary and capricious. It also says the record did not support the government’s stated national-security rationale.

The court granted Anthropic summary judgment on the central claims, but not on every claim. It rejected the company’s separate ultra vires separation-of-powers challenge and entered judgment for the government concerning certain agencies that did not take relevant action or took only interim measures.

What the judge found

The dispute began as the Pentagon sought an “all lawful uses” provision for Claude, Anthropic’s AI model. Anthropic agreed to remove most restrictions but kept limits on two uses: mass surveillance of Americans and lethal autonomous warfare.

Anthropic said those uses raised safety and civil-rights concerns. The Pentagon argued that private companies should not be able to constrain military operations and later designated Anthropic a national-security supply-chain risk.

Judge Lin concluded that the government’s administrative record was thin. The ruling says a four-page memorandum supplied most of the stated justification and did not establish that Anthropic could sabotage or alter its models after deployment. The court also pointed to the government’s prior approval and use of Claude, along with continued efforts to work with Anthropic after the designation.

Those facts, the judge concluded, were inconsistent with the administration’s claim that Anthropic posed a genuine sabotage threat. The court found that the challenged actions were tied instead to Anthropic’s public criticism and its refusal to accept the requested contract language.

“The empty invocation of national security is not a blank check to punish and retaliate against government critics,” Lin wrote in the order.

What changes now

The court said Anthropic is entitled to vacatur and permanent injunctive relief, but it also said that the operative relief would be issued in a separate order. The judge denied the government’s request to administratively stay the permanent injunction for seven days, noting that officials had already complied with the preliminary injunction for more than five months.

Until the separate relief order and any appellate action are clear, agencies and defense contractors will need to examine the precise scope of the ruling and how it affects existing restrictions, contracts and procurement systems.

The decision does not require the Pentagon or any other agency to use Claude, restore Anthropic to every federal contract or select the company as a vendor. The court expressly recognized the government’s authority to choose the AI products that meet its operational needs through lawful procurement procedures.

That distinction is central. The case was not about whether the government must continue buying Anthropic’s technology. It was about whether officials could impose sweeping government-wide and contractor restrictions as punishment for the company’s position on high-risk AI uses and its public criticism of the administration.

Two legal tracks remain

The administration is expected to appeal, but an appeal should not be described as filed unless a notice of appeal or appellate motion is confirmed. The government could also seek an emergency stay in the appeals court.

A separate case remains pending in the U.S. Court of Appeals for the D.C. Circuit. That litigation concerns a March 3, 2026 designation under a different statute, 41 U.S.C. § 4713. In an April order, the appeals court denied Anthropic’s request for a stay but granted expedited consideration, leaving the merits unresolved.

The two cases therefore involve related events but different legal tracks. The Northern District of California ruling addresses the broader government-wide restrictions and the designation challenged under 10 U.S.C. § 3252. The D.C. Circuit matter concerns the separate Section 4713 action barring Anthropic from providing goods or services to the Defense Department.

Why the ruling matters

For AI companies, defense contractors and federal procurement officials, the decision is a significant test of how far national-security and supply-chain authorities may reach when a vendor disputes the government over surveillance, autonomous weapons or other sensitive AI applications.

The ruling does not eliminate the government’s ability to reject a vendor for legitimate operational, security or business reasons. It says broad punitive restrictions cannot be justified by an unsupported national-security rationale or imposed in retaliation for protected speech.

The next major markers are the court’s separate relief order, any emergency stay request, a possible government appeal and further proceedings in the D.C. Circuit. Those actions will determine how quickly the ruling changes procurement practice and how much discretion future administrations retain when technology companies challenge high-risk uses of artificial intelligence.

Sources

• Northern District of California summary-judgment order
• Axios report on the Anthropic blacklist ruling
• D.C. Circuit order in Anthropic’s related case

The five-year base term is valued at $84,909,900.53. Two optional two-year renewals could raise the contract’s potential maximum value to $109,381,984.13, but those renewal periods are not money committed immediately.

The project will affect election administration in every Maryland county and Baltimore City. It covers the acquisition, deployment and support of a new voting system, but deployment has not been completed.

What Maryland approved

The board approved Item 49-IT, contract D38B5600001, after discussion. The procurement agenda identifies Election Systems and Software LLC of Omaha, Nebraska, as the awardee selected through a competitive sealed-proposal process.

The procurement agenda lists a contract term beginning August 6, 2026, and ending August 31, 2031, with two optional two-year renewal periods. The first renewal is valued at $12,099,255.80 and the second at $12,372,827.80. The board’s meeting summary lists the item as approved after discussion and describes the base amount as not to exceed $84,909,901.

The procurement record says the system is intended for statewide implementation in time to support the 2028 presidential election cycle. The approved funding plan is 50% general funds and 50% special funds identified as county funds.

Why the state is replacing its current system

The State Board of Elections said Maryland’s current voting system has been in service for more than 10 years. Some components have reached the end of their manufacturing life, and the vendor has sunset hardware used in Maryland.

The agency said those conditions limit its ability to obtain additional equipment and that the supporting infrastructure is also aging. State officials have cited increasingly difficult access to replacement parts and vendor support as reasons to replace the system.

The new contract is intended to provide updated equipment and related infrastructure, along with vendor support for statewide election operations. The procurement documents describe a future acquisition and deployment project, not a completed installation.

What officials said about certification

State Administrator Jared DeMarinis told the Board of Public Works that the system being procured for the 2028 election had received federal and Maryland certification. He said Maryland conducted three days of testing at three locations as part of the state certification process.

Maryland’s voting-system testing guidance says a system used in the state must complete both federal and state certification. State certification addresses requirements including ballot secrecy, security, accurate vote counting, voter and candidate rights, and the creation of a paper record for audits and recounts.

The State Board of Elections also says Maryland uses a paper-based election system, tests voting units before use and before each election, and conducts post-election audits. The agency says risk-limiting audits will be performed beginning in 2026.

DeMarinis also told the board that payments would occur after the contractor meets deliverables. That payment structure does not change the approved contract ceiling or guarantee that every optional renewal will be exercised.

Why critics objected

Election-security advocates who spoke at the meeting did not focus their objections on whether Maryland should replace its aging system. Their concerns centered on a later upgrade contemplated in the procurement.

Susan Greenhalgh of Free Speech for People, speaking with support from Common Cause Maryland and Save Our Votes Maryland, said the procurement covered the system intended for 2028 as well as a later version associated with updated federal voting-system standards known as VVSG 2.0.

Greenhalgh argued that the later version had not yet been demonstrated, tested or certified for Maryland. She also questioned whether the contract clearly separated the cost and obligations for the initial system from the future upgrade.

Those statements were objections raised during the board meeting, not a finding that the system planned for 2028 lacks certification. DeMarinis said any future version would have to meet applicable federal and Maryland certification requirements before it could be used.

What happens next

The approval resolves the state’s procurement decision, but implementation work remains. Maryland officials and the vendor must execute the contract, acquire and deploy equipment, complete required testing and document readiness before the 2028 presidential election.

The potential VVSG 2.0 upgrade is a separate oversight issue. The unofficial meeting transcript records questions about whether that later system will be delivered and certified by 2030. DeMarinis said failure to meet that obligation would constitute a contractual failure and could lead to further state action.

Residents should watch for deployment schedules, public demonstrations, certification records, testing results and readiness reports. Those records will show whether the state completes the replacement on schedule and how officials handle any later upgrade.

For voters, the immediate change is not a new voting rule or a stated change to Maryland’s paper-ballot, audit or contingency framework. It is a statewide technology replacement project whose accountability will depend on contract performance, testing, certification, deployment and continued public oversight before the 2028 election.

Sources

• Maryland Board of Public Works July 22, 2026 procurement agenda
• Maryland State Board of Elections Voting System Testing guidance
• Maryland Matters report on the contract approval

The county issued the request for proposals on July 2 for work at the garage at 1331 Helen Highway. The solicitation seeks a licensed commercial general contractor to address termite damage and related building repairs.

What the county wants repaired

The requested work includes repairs to termite-damaged stud walls, interior paneling, exterior siding and insulation. The project also includes securing loose or unattached truss bracing identified at the facility.

The repair documents describe a requested performance period of 30 days after the county issues a notice to proceed. That is the county’s requested completion period in the solicitation, not a confirmed construction schedule.

The project is still in the bidding stage

No contractor has been selected, and the county has not published a final project cost or construction start date. The next formal milestone is the proposal deadline on July 31 at 3 p.m. Eastern time.

After proposals are received, the county will review the submissions before deciding whether to award the work and issue a notice to proceed. Until those steps occur, the timing and cost of the repairs remain unsettled.

Why it matters in Cleveland

The project concerns a county EMS facility on Helen Highway, making the condition and repair of the building a local public-service issue. White County Emergency Medical Services lists Cleveland as the location of its county EMS headquarters.

The available procurement documents do not establish that ambulance service has been interrupted or that operations are being moved. They show that the county is seeking bids to repair identified building components while the project remains under procurement.

A contractor award and notice-to-proceed date will determine when the requested work can begin. Until then, the contractor, final cost and construction schedule remain undecided.

Sources

• White County EMS Ambulance Garage Repairs RFP, Final Revision

What changed on July 16, 2026

This July 16 sentencing is the next step after Jones entered a guilty plea on April 2, 2026. DOJ says the sentencing—imposed by a federal judge—converts the case from a plea-stage matter into a court-imposed penalty, followed by supervised monitoring.

DOJ’s account: steering a Census employee assistant contract

According to DOJ and court documents described in the releases, Jones admitted that she steered a large employee assistant program contract to a prime contractor and a subcontractor, YMJ Consulting, which was owned by a relative of Jones. DOJ says Jones received kickbacks in exchange for steering the contract and related modifications; prosecutors described the contract as being worth “millions of dollars.”

Why prosecutors say the case involved obstruction

DOJ also says Jones tried to obstruct investigators by drafting a service agreement between YMJ Consulting and a mental health company she owned. In DOJ’s account, both Jones and her relative signed the agreement in 2024 but backdated it to 2020 to make the kickbacks appear like legitimate consulting payments. Prosecutors say the relative then provided the document to law enforcement during the investigation.

Confidential procurement information and a related-pay allegation

DOJ further says Jones used her official position to share the Census Bureau’s confidential procurement information with another government contractor. DOJ says that contractor hired another one of Jones’s relatives for a “minimal-work” job, while Jones largely performed the work—yet the relative received $83,000, according to DOJ’s description.

How the case was investigated and prosecuted

DOJ says the investigation involved the U.S. Department of Commerce Office of Inspector General (DOC-OIG). DOJ’s Criminal Division Public Integrity Section and the U.S. Attorney’s Office for the District of Maryland prosecuted the case.

Timeline to watch: co-defendant status

DOJ notes that on Aug. 14, 2025, Jones’s relative, Yolanda Jones, pleaded guilty as well and was awaiting sentencing as of the July 16 announcements. Any later sentencing or related rulings could be a key follow-on development for readers tracking the procurement-integrity accountability chain.

What this means for taxpayers and federal contractors

For taxpayers and contractors, this case underscores how federal procurement disputes can quickly become criminal when prosecutors believe officials misused contracting influence and handled sensitive procurement information improperly—especially when prosecutors also allege efforts to shape the paper trail.

Sources

• DOJ: Former Census Bureau program manager sentenced (July 16, 2026)

What GAO reviewed

GAO examined cloud procurement across agencies covered by the Chief Financial Officers (CFO) Act. GAO’s headline finding: senior officials from 22 of the 24 selected agencies reported mainly relying on historical procurement data to help make cloud decisions.

The procurement challenges GAO says show up most often

GAO reports that senior officials most frequently identified these cloud procurement obstacles:

• Control of cloud costs requires changes in IT management approaches (17 agencies). GAO says because cloud services are billed on a consumption model, agencies may need to adjust day-to-day practices to track and control usage spending.
• Conflicting OMB and NIST software guidance caused confusion (17 agencies). GAO says the inconsistency created unnecessary burdens for collecting and storing key software components.
• Outdated Federal Acquisition Regulations (FAR) impeded cloud procurements (15 agencies). GAO says the FAR still lacks cloud-related definitions and that other core definitions don’t align with how cloud computing is used today—even after FAR changes made between April 2025 and October 2025.
• Agencies encountered difficulties obtaining authorized cloud solutions (15 agencies).
• Multi-vendor cloud adoption faced new technical considerations (11 agencies), including interoperability.
• Resource constraints hindered cloud workforce acquisition (10 agencies).

Why this matters for taxpayers and federal users

GAO does not argue that cloud procurement is automatically wasteful. Instead, it frames these items as procurement challenges that can translate into inefficiencies—and it also notes that agencies’ ongoing and planned actions, if implemented effectively, could lead to substantial savings.

Practically, the GAO report centers on a simple accountability question: do procurement rules, guidance, and day-to-day cost management practices match how cloud services actually work (including consumption-based billing and multi-vendor implementation)? When those don’t line up, agencies can face more friction in contracting, compliance, and scaling modernization.

What GAO wants Congress and agencies to do next

GAO’s “matter for congressional consideration” focuses on updating how cloud is defined in law and acquisition rules:

• Congress should consider updating statutory definitions of commercial products and commercial services, and requiring acquisition regulations to reflect these definitions.
• Congress should consider requiring acquisition regulations be updated to define information technology consistent with FITARA and to define “cloud computing” consistent with NIST’s definition.

GAO’s executive-action recommendations are aimed at specific agencies and governance bodies:

• GSA: require agencies to use FinOps practices and report the extent of benefits resulting from the practices.
• DHS (CISA): issue additional SBOM implementation guidance, including how agencies should integrate SBOM generation, consumption, and analysis into risk management, purchasing, and software development.
• Federal CIO Council: collect and share examples of leading practices for multi-vendor cloud solutions, including containerization and testing platform interoperability.

What to watch next

• Whether Congress moves to update acquisition-related definitions as GAO recommends.
• Whether GSA, DHS/CISA, and the Federal CIO Council provide and implement the guidance and governance steps GAO called for.
• Whether agencies tighten cloud cost management (especially around consumption-based spending) and improve how they implement multi-vendor environments.

Sources

• GAO-26-107530 product page (published June 23, 2026)
• GAO-26-107530 full report (readable HTML)