• |

    Musk and the Public-Private Tab

    I follow the invoice, and the Musk question is hard to miss: public science and infrastructure can help lower the risks around private enterprise, while private gains get presented as a solo performance. That does not mean every public dollar bought a particular rocket or car. It does mean the public should not disappear from the story when private wealth takes its bow.

    Companies can turn ideas and investment into products, services, and fortunes. Fine. But if the public shares the risk, it deserves a fair return—and billionaires should pay taxes fairly and give back to the society that makes enterprise possible. My audit is simple: the public helped build the runway. It should not get handed a second invoice for the applause.

  • |

    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.

  • |

    The Supreme Court Takes Up the Question of Who Gets to See DOGE’s Records

    On October 13, 2026, the Supreme Court agreed to hear the administration’s challenge to discovery in a case over records sought from the U.S. DOGE Service. That is a real procedural step. It is not a ruling that DOGE must answer FOIA requests, and it is not an order to release the records. The docket has opened a door to argument; it has not sent a records clerk sprinting toward the copier.

    The request and the refusal

    Citizens for Responsibility and Ethics in Washington, or CREW, sought DOGE records that included organizational information and financial disclosures. The government declined to process the request, saying DOGE was not subject to the Freedom of Information Act. CREW then sued. In its filing opposing Supreme Court review, CREW describes seeking discovery—information gathered during litigation—to help establish whether DOGE falls within FOIA’s reach.

    The administration is challenging the discovery allowed in the lower-court litigation. The dispute matters because information gathered there could help the parties address whether DOGE qualifies as an entity covered by FOIA. CREW’s filing gives its account of the request and the discovery dispute; it is a party’s argument, not a final judicial finding about DOGE’s status.

    What the Court has—and has not—done

    The Supreme Court docket records that the Court granted review on October 13. The case before the justices concerns discovery relevant to CREW’s FOIA case and DOGE’s status under the law. Discovery is a process for gathering information in a lawsuit. It is separate from deciding the ultimate legal question, and separate again from ordering an agency or other entity to disclose records to the public.

    That distinction is the whole machine. The Court has not decided whether DOGE is covered by FOIA. Nor does agreeing to hear the administration’s challenge mean the justices have endorsed the administration’s position or CREW’s. The grant concerns what information may be gathered as the case proceeds; it does not resolve what the requested records ultimately must reveal, or whether they must be released.

    For people trying to understand how a powerful government operation is organized and financed, the dispute matters because access rules determine what can be examined in public. But the development now is about the process for testing DOGE’s legal status, not a completed transparency ruling. A case can advance to the Supreme Court while the records remain undisclosed and the central FOIA question remains open. Paperwork can travel a long way while disclosure stays in the waiting room, holding a numbered ticket.

    Sources

  • |

    Tech Billionaires and the Public’s Unpaid Tab

    Here is the civic audit: Elon Musk, Jeff Bezos, Mark Zuckerberg, Larry Page and Sergey Brin, and Jensen Huang are presented alongside public foundations—NASA rocket science, public internet and roads, USPS, university and NSF research, public chip science. Treat that as the premise, not a neat causal ledger. Billionaire logic has a remarkably one-way turnstile: shared systems are welcome as launch equipment; the public asking for a return is suddenly begging.

    That is why a tax-funded public dividend makes sense as repayment, not charity. Workers, taxpayers, researchers, and neighbors help build and maintain the country that makes private fortunes possible. The check is not a tip jar tossed toward the people who built the road; it is an overdue invoice marked OUR SHARE. If the public helped lay the runway, the people should not be told to admire the takeoff from outside the fence.

  • |

    Republicans Run Washington, but Democrats Get the Blame

    Right-wing TV’s grievance script wants the keys and the victim’s alibi: “DEMS ARE RIGGING IT,” “ACTBLUE IS THE THREAT,” and Republicans need more seats. Beside those claims, the meme’s labels put Republicans in control of the White House, the U.S. House, the Senate, and the Supreme Court. Those labels are the premise of the argument, not a ledger of who held what when. The contradiction is the point: power gets presented as both possession and persecution.

    Here’s the newsroom-raccoon audit: if you’re holding the keys, you can’t file a break-in report and insist the cure is another key ring. Voters deserve a distinction between accountability and grievance dressed up as a request for still more power. When blame is the product, every setback becomes an ad—and nobody has to explain what they did with the keys.

  • |

    Ticketmaster’s FTC Lawsuit Survives the First Court Test—But Fans Haven’t Won Yet

    A ticket purchase can feel like courtroom drama: you enter your details, wait for the page to load, and wonder what the next screen will reveal. In the federal case against Live Nation and Ticketmaster, the drama has advanced—but only to the next legal scene. On September 28, a judge denied the companies’ motion to dismiss a consumer-protection lawsuit brought by the Federal Trade Commission and seven states. The case can proceed. That is not the same as saying the FTC has proved its case.

    What the FTC and states allege

    The FTC and states allege that Live Nation and Ticketmaster misled consumers about ticket prices and purchase limits. They also allege that the companies facilitated the resale of tickets by brokers who had obtained more tickets than artists’ limits allowed. Those are allegations in the lawsuit, not findings of fact. The distinction matters: a court deciding that a case may continue has not decided that every claim in it is true.

    A motion to dismiss is an early court test, not the finale where the underlying dispute is resolved. Denying it means the lawsuit is not being thrown out at this stage; it does not turn the allegations into established facts. The court order expressly leaves the truth of the accusations undecided. The case now continues, with its claims still to be resolved.

    A court hurdle, not a fan refund

    The September 28 order denied the defendants’ request to dismiss the case at this stage. In practical terms, that means the dispute keeps moving through court rather than ending on that motion. The FTC’s case timeline lists the order and describes the case as pending; Bloomberg Law also reported on the ruling. Neither the order nor the ruling itself hands fans refunds, changes a ticketing screen, or settles how tickets will be sold.

    That gap is easy to miss because “lawsuit survives” sounds like a victory headline—and, legally, it is a meaningful step for the claims to proceed. But the ticket buyer’s immediate reality is more modest: this ruling did not decide whether the alleged conduct happened. There is no court-ordered fix for fans in this decision. The legal process has cleared one obstacle; it has not reached a conclusion about the underlying claims.

    The encore is still unwritten

    For fans, the useful takeaway is to separate legal momentum from practical relief. The lawsuit is moving forward, and its allegations put ticket pricing, purchase limits, and resale under scrutiny. But the case remains unresolved. This order does not tell ticket buyers that the allegations have been proved, and it does not announce a new consumer protection at checkout. A court hurdle is not the same thing as a change to the buying experience.

    Until the claims are decided or the parties otherwise resolve the dispute, the order remains a procedural step—not proof of misconduct and not a remedy for fans. The song matters; so does the invoice. For now, the invoice is still waiting outside the courtroom while the case gets through its opening act.

  • |

    Apple and Epic Are Still Fighting Over the App Store Fee Math

    An October 9 joint status report in the Apple-Epic dispute records a disagreement over Apple’s production of documents concerning proposed commissions on purchases made through external links. 9to5Mac reported on the filing October 12. The report captures the parties’ competing accounts; it is not a decision on the fees or a finding about which account of the document search is correct.

    Two accounts of the document search

    Epic says Apple’s document production is inadequate and asks the court to set a November 1 deadline for production. That is Epic’s request, not a deadline the court has ordered. Apple disputes Epic’s characterization. According to Apple’s account, it agreed to broaden its searches and expects to make a substantial production later. The filing does not establish either party’s description as the definitive account, and it does not provide a specific later completion date.

    The parties do agree on one procedural point: Epic’s 60-day response period has not yet begun. That does not mean the commission dispute has been resolved or that the court has accepted either side’s position on the documents. It means the report describes an ongoing process, with the timing of the response period still ahead. The filing is a progress update, not a ruling wearing a tiny judge’s robe.

    Why the paperwork reaches users

    Records about how a platform sets fees can help clarify the rules developers must navigate when they offer ways to buy outside an app store. Those rules may affect which options developers choose to offer and, in turn, which choices users see. That is a reason the underlying documents matter. It is not proof that developers will pass a particular fee on to customers, or that prices will change.

    The immediate question in this report is narrower than the larger fight over app distribution and payments: what documents Apple will produce about the proposed external-link commissions, and when. Developers have an interest in understanding the terms of doing business on a major platform. Users have an interest in knowing what purchase routes are available and what rules shape them. Neither point tells us what the documents will show; the filing itself does not answer that.

    For now, the useful takeaway is modest. Epic wants a November 1 production deadline. Apple disputes Epic’s account, says it agreed to broaden its searches, and expects substantial production later. The parties say Epic’s 60-day response clock has not started. The proposed commissions remain undecided in this update, as does the dispute over the paperwork. The corporate maze is still open, now with two sets of annotations and no final map.

  • |

    When a Hurricane Map Makes Things Up

    A bad weather map and a real weather threat arrived in the same conversation: one part legitimate danger, one part visual confusion, and a group chat trying to decide whether the corkboard needs more string.

    The graphic was retracted

    AFP reported that Tampa-based Fox 13 meteorologist Paul Dellegatto briefly shared an inaccurate graphic described as AI-generated, then deleted it and acknowledged inaccuracies. That is the sequence the reporting supports: a weather communicator shared a faulty visual, removed it, and recognized that it was wrong. AFP’s account does not establish that the graphic caused specific harm or widespread panic, so there is no need to inflate the story into a disaster of its own.

    Even a short-lived map can complicate a fast-moving weather conversation. Maps borrow authority from tidy colors, sharp lines, and the general air of having passed a meeting. A viewer may not know whether an image is an official forecast, a repost, or an illustration that has wandered away from its facts. The graphic looked like it belonged in the briefing; that is exactly why accuracy matters.

    The threat was real—and geographically limited

    The faulty image should not be confused with the underlying hazard. The National Weather Service Storm Prediction Center’s outlook described a severe-weather setup with possible tornado risk associated with Isaias. The National Hurricane Center’s discussion also noted tornado potential and placed the greatest risk east of the storm’s center, particularly from the Florida Panhandle into southern Georgia. That was a specific forecast area, not a claim that all of Florida—or the entire storm track—faced equal risk.

    The distinction matters because misinformation can work in both directions. A misleading graphic can make a real threat harder to understand; finding a bad graphic can then tempt people to dismiss the threat itself. Neither reaction helps. The image’s accuracy and the official forecast’s assessment are separate questions. In this case, AFP reported inaccuracies in the graphic, while official forecast products described a real, geographically focused tornado risk.

    Check the forecast, not the vibes

    For anyone caught in the next weather group chat, the practical move is unglamorous: go directly to National Weather Service or National Hurricane Center forecast products and compare the location and hazard there. A polished visual is not a substitute for an official outlook, and an inaccurate visual is not proof that the weather danger was invented. Follow the thread, but check the knot.

    There is no need to pretend a correction instantly clears up confusion. The useful lesson is narrower: when an authoritative-looking image conflicts with official forecast information, verify the forecast itself before sharing the image or dismissing the risk. Weather already has enough plot twists without the panic boutique adding props.

  • |

    Freedom 250’s public bill—and the private donations still outside the ledger

    Freedom 250’s newly released budget estimate puts key event costs at $128.5 million and anticipated federal funding at $114.2 million. The narrow question in the paperwork is how the private money reportedly raised for the effort is reflected. The estimate does not appear to show how those donations were allocated to the events. That is a transparency gap worth tracking—not evidence, by itself, that anyone mishandled funds.

    What the records show

    On October 8, the watchdog group Public Employees for Environmental Responsibility (PEER) released records it obtained through a public-records request. The budget estimate lists $128.5 million in projected costs and $114.2 million in anticipated federal funding. The record packet also includes a procurement-waiver request and a National Park Service cooperative agreement, pieces of the federal arrangement behind the events. They help explain the public side of the financing; they are not a final, all-in accounting.

    An estimate is a planning document, not a paid invoice. PEER has raised questions about the contracting and taxpayer-funding arrangements, but those questions should not be upgraded into findings the documents do not establish. A waiver request is not, on its own, proof of improper contracting. Bureaucratic paperwork can be alarming without becoming a verdict. The money trail deserves scrutiny; it also deserves accurate labels.

    The private-money question

    The Washington Sun reported that earlier disclosures showed more than $50 million in private funds had been raised for Freedom 250. The outlet said the released estimate did not appear to assign those donations to the events. From this estimate alone, readers cannot see how the reported private funds fit alongside anticipated federal funding and projected costs. It does not show that donations are missing, diverted, or unlawfully handled. A ledger with an unanswered column is an unanswered question—not a crime scene.

    The Washington Sun reported that the administration disputed or qualified treating the estimate as final, and that costs were still being reconciled. So the $128.5 million figure should not be presented as the final cost, and the current documents should not be mistaken for a complete accounting. Reconciliation is part of settling expenses; it is also why the final version matters. Until the accounts are brought together, the estimate does not show how the private and federal funding streams relate.

    What a final accounting should clarify

    A clear final accounting would show total costs, funding sources, and how private donations were allocated, while distinguishing commitments from money actually spent. That would let taxpayers and donors follow the basic trail: what came in, what went out, and which expenses each source covered. For now, the released records offer meaningful figures and a limited view of the arrangement. The right conclusion is neither “nothing to see” nor “case closed.” It is simpler: publish the reconciled accounting, then let the numbers do their job.

  • |

    The Reflecting Pool Case Is Over. The Paper Trail Is Not.

    David Hearn’s Reflecting Pool case was dismissed with prejudice on October 1. On October 6, his lawyers asked the Justice and Interior departments’ inspectors general to review how the investigation and prosecution were handled. The criminal case is closed; the paperwork has been invited to remain in the building.

    The Associated Press reported that prosecutors dropped the case after information indicated flawed contractor installation caused the damage, rather than Hearn. That reported explanation matters: it shifts attention from the person accused to the work done on the pool. It does not, by itself, establish that investigators acted improperly. A case can end after evidence changes without every unanswered question becoming proof of misconduct.

    What the lawyers want reviewed

    Hearn’s attorneys asked the two watchdog offices to examine the investigation and prosecution. Their request raises concerns about how the case was handled, but those concerns remain allegations, not findings. That distinction is less dramatic than a courtroom reveal, but it is the load-bearing beam in any account of what happened. A letter asking for scrutiny is not an inspector general report, and it does not show that either office has opened an investigation.

    The dismissal with prejudice is a procedural ending to Hearn’s case. It is not, on its own, an official explanation of every decision made along the way, nor does it resolve the lawyers’ allegations. Their request asks for scrutiny of how the case was handled; the reporting available on October 6 did not establish what either inspector general would do next.

    A request is not a verdict

    That boundary is where accountability starts, not where it ends. Inspectors general may review institutional conduct, but receiving a letter does not turn its claims into proven facts. The public deserves clarity about how government decisions are made, especially when a case ends after information points elsewhere. It also deserves careful language while the record is incomplete.

    For now, the reported sequence is stark enough: the case was dismissed, prosecutors had information pointing to faulty installation, and Hearn’s lawyers asked federal watchdogs to review the handling. The request puts questions on the administrative record. Whether the watchdogs take them up—and what any review might conclude—remains unresolved. The filing cabinet has cleared its throat. It has not yet delivered a verdict.

End of content

End of content