Pentagon

  • |

    The Pentagon Watchdog Sends the Starlink Question to Another Desk

    The Pentagon inspector general received a request to investigate reported Starlink and Starshield disruptions affecting Ukraine and pointed the senators toward the Air Force. The watchdog did not take up the requested investigation. It was a procedural handoff, not a finding about who caused anything. Still, the paperwork has moved: AP reported the response on October 28, and a separate Senate inquiry is seeking information from both the Defense Department and SpaceX.

    What the senators want examined

    The bipartisan request, led by Senators Jeanne Shaheen and Thom Tillis, asked the inspector general to examine a precise and consequential question: whether U.S. officials directed, authorized, approved, or knew in advance about changes affecting Ukraine’s access to Starlink. Those are questions for an investigation, not established facts. The distinction matters. A question printed on congressional letterhead remains a question, even when the letterhead is very good at making paper look like it knows something.

    According to AP, the inspector general said the concerns were better addressed by the Air Force and declined the requested investigation. That referral does not establish that the Air Force made or approved changes, nor does it answer what U.S. officials knew. It tells us where the watchdog thinks the issue should be handled next. In the records room, that is movement—but not resolution. The file has changed desks; the contents have not magically become findings.

    A separate inquiry, with a deadline

    Senator Richard Blumenthal announced a separate inquiry seeking information from the Defense Department and SpaceX. His announcement sets November 5, 2026, as the deadline for written responses. As of November 2, that deadline is still ahead. The inquiry therefore represents a request for records and answers, not evidence that either recipient has responded or that the questions have been settled.

    The two efforts should not be folded into one grand investigative machine. Shaheen and Tillis asked the Pentagon inspector general to investigate; that office declined and referred the concerns to the Air Force. Blumenthal’s inquiry is separately seeking information from the department and the company. The Senate releases document what lawmakers asked for, while AP reports the watchdog’s response. None of that, on its own, tells the public who made the relevant decisions, what authority applied, or whether anyone had advance knowledge.

    That is the uncomfortable center of the story: the unresolved issue is not merely which office owns the folder, but how decisions affecting access to a privately operated communications service were made and what government officials knew. Oversight is supposed to make that chain visible to the public. For now, the record establishes a referral, two congressional efforts, and a deadline approaching. The document coughed. The answer has not.

  • |

    Pentagon’s $350 Million Contract Trail Raises Questions About Old Ties

    The awards and the question

    The Pentagon’s contract paperwork has produced a familiar Washington puzzle: substantial public spending, a flexible procurement route, and a reported business connection that deserves a closer look without being mistaken for proof of misconduct. ProPublica reported that Alvarez & Marsal Federal received a $281 million no-bid Pentagon consulting contract; altogether, Alvarez & Marsal-related entities received nearly $350 million in military spending across two deals since December. The question is not whether a connection automatically proves a conflict. It does not. The question is whether the decisions, disclosures, and oversight are clear enough for the public to follow the money.

    Separate companies, relevant questions

    ProPublica’s investigation also reported that George Kollitides had an advisory connection to A&M Capital when the contracts were signed. That relationship is relevant context, but it is not evidence that Kollitides directed or influenced the awards, or personally benefited from them. Nor should Alvarez & Marsal Federal, the consulting business, and A&M Capital be collapsed into one convenient corporate blob. In procurement, names and relationships matter; so do the distinctions between them. The public deserves a map, not a fog machine.

    What the procurement route means

    The $281 million consulting award used an other transaction agreement, or OTA. The Government Accountability Office says OTAs can give the Defense Department flexibility to work with industry, but its broader review also identifies oversight risks, including less visibility into contractor costs. That is general context, not a GAO finding about these specific awards. Still, flexibility is not a magic word that makes scrutiny unnecessary. When a large contract uses a route with different oversight features, taxpayers have a reasonable interest in how the department tested costs and documented its decision.

    What officials say—and what remains

    The Pentagon told ProPublica that applicable ethics rules were followed. A&M Capital said it is separately managed from the consulting business. Those responses matter, and they should be included alongside the reporting. They do not, on their own, answer every public question about how the awards were evaluated, what disclosures decision-makers made, or what records support the department’s process. The reporting does not establish wrongdoing, and the available facts should not be stretched into an accusation. But “rules were followed” is a conclusion; accountability also depends on whether the underlying process can be examined.

    Follow the invoice

    Defense spending is not an abstract line in a spreadsheet. It is public money assigned to work the government says it needs, and the public should be able to understand why a contractor was selected and how the bill will be watched. A reported relationship is not a verdict. An OTA is not evidence of abuse. Together with a large award, however, they make disclosure and oversight ordinary questions—not hostile ones. Washington has never lacked confidence in its own paperwork. The useful test is whether the paperwork lets everyone else see who made the call, on what basis, and how the public gets its money’s worth.

  • |

    Please Do Not Invade the Voting Booth

    My corkboard has a new thread, and for once the knot is labeled clearly: nobody is supposed to send troops into polling places. Yet the national rumor machine has apparently submitted a military customer-service ticket asking whether the Pentagon plans to occupy the voting booth. The answer, according to Gen. Dan Caine’s written response, is no—not federal troops, not federalized National Guard members, not ballot seizures, not voting-machine seizures, and not unlawful election orders. This is an assurance against a feared action, not evidence that an invasion occurred.

    That distinction should be ordinary civic housekeeping. Instead, it arrives like a fire department explaining that the library is not currently on fire, while everyone refreshes the app to see who started the smoke. The online panic economy takes an extreme hypothetical, repeats it until it develops a necktie, and then demands an official statement proving the hypothetical has not become policy.

    The contradiction gets sharper because Caine provided the specific assurances requested by Sen. Elissa Slotkin, while Defense Secretary Pete Hegseth had not provided the same confirmation, according to reporting from The Associated Press and Slotkin’s office. So democracy is left with one senior military voice saying the voting booth is not a deployment zone and another top official declining to answer the same basic question. Follow the thread, but check the knot: silence is not proof of a plot, yet it is an excellent fertilizer for one.

    That is how ordinary voters get dragged into the group chat. They are not being handed clear information about an actual operation; they are being asked to treat the possibility of military interference as routine background noise, like a delayed flight or a website cookie nobody remembers accepting. Meanwhile, every rumor merchant benefits from the fog. Panic generates clicks, officials generate clarifications, and the public gets stuck paying attention to a crisis that exists primarily as a question.

    America has reached the stage where democracy needs a do-not-disturb sign beside the ballot scanner: “Please stop knocking. No amphibious landing is scheduled.” The Pentagon FAQ practically writes itself: No, We Are Not Invading the Voting Booth. A healthy republic should not need that sentence, but until the rumor machine learns the difference between asking questions and manufacturing smoke, we may want it printed in large type.

  • |

    The Pentagon’s $500 Million Drone Shield

    Washington announced a $500 million drone shield, and my money-trail desk immediately found the box labeled “maximum possible invoice.” The Army’s Joint Interagency Task Force 401 awarded CACI a three-year indefinite-delivery/indefinite-quantity contract for domestic counter-drone work. That contract carries a ceiling of $500 million. It does not mean the government has already spent $500 million, nor does it mean taxpayers have received $500 million worth of protection. In federal contracting, the headline arrives express; the receipt travels by carrier pigeon.

    CACI’s SkyValor system was selected for the first task order, according to the company and the Army. That is a real procurement step, but it is not a performance report, an operational-results report, or a guarantee that every dollar under the ceiling will be used. The distinction matters because “up to” is one of the most profitable phrases in public life. A restaurant cannot serve you an imaginary twelve-course meal and call it dinner, but a defense contract can reserve the table for three years and leave the final bill developing off-site.

    The Pentagon’s argument is speed. Counter-drone threats move quickly, so acquisition needs what officials describe as speed of relevance. Fair enough: nobody wants a security system designed at the pace of a committee hearing about whether the threat exists. An indefinite-delivery structure can give the government flexibility to order equipment and services as requirements develop. But flexibility for the buyer can become fog for the public, especially when the contract ceiling is easier to print than the eventual orders, prices, delivery milestones, and results.

    That is where Phil McCracken follows the invoice through the shrubbery. The concern is not that counter-drone technology is unnecessary, or that CACI has done something improper. The concern is that urgency can become a permission slip to explain the money later. A ceiling is an authorization limit, not a receipt. A first task order is an opening transaction, not proof that the whole promised shield has arrived and works as advertised. Taxpayers deserve to see what gets ordered, what it costs, what shows up, and what performs before the contract’s maximum becomes Washington’s favorite round number.

    America may need a drone shield. It does not need a public accounting shield protecting the invoice from daylight. The country gets protection now, defense contractors get a potentially recurring tab, and the details remain somewhere between “mission accomplished” and “please hold.” In Washington, even homeland security comes with an expandable subscription plan.

    Sources

  • |

    The Pentagon’s $7 Billion Software Subscription Comes With a Free Accountability Question

    Phil McCracken looks at a possible $7 billion Pentagon software commitment the way a diner waitress looks at a fake coupon: polite, tired, and already checking the fine print. The Defense Department can call the Oracle agreement a savings plan because it replaces scattered software purchases with one enterprise deal. That may reduce duplication. It does not magically reduce the number of questions attached to a very large bill.

    Federal News Network reports that the agreement could run for 10 years and reach up to $7 billion. The first five-year period is valued at $3.3 billion, with a possible extension worth another $3.6 billion. The Pentagon projects at least $441 million in savings through consolidation. Important word there: projects. That is a forecast, not a check cleared by reality.

    There is nothing inherently foolish about buying software in a more organized way. A government that discovers it has been purchasing the same digital wrench from several counters might reasonably try using one counter. But procurement efficiency and public accountability are different departments, even if both occupy the same enormous federal building. A cheaper arrangement should be demonstrated through verified costs, usable performance, renewal terms, and transparent oversight—not merely announced with the confidence of a man who has found a coupon for 40 percent off a yacht.

    The concentration matters because one vendor could receive a decade-long revenue runway while taxpayers are asked to trust the savings math. That is not evidence of wrongdoing, favoritism, or an illegal contract. It is evidence that a large, centralized commitment deserves more than a victory lap. When government replaces several smaller purchases with one giant agreement, it may simplify billing while increasing dependence on a single supplier. Follow the invoice, then follow the exit door. Someone should know what leaving would cost.

    Washington has apparently placed the projected savings in one column, the potential $7 billion commitment in another, and left the accountability column for the public to fill in with a pencil. The Pentagon may have cleaned up the invoice. Taxpayers still need to know whether the savings survive contact with delivery, renewals, upgrades, and the fine print. A tidier bill is not proof of accountable value; it is simply a tidier bill waiting for an audit.

End of content

End of content