Prince Harry’s Speech in Kiev
-
-
War Zone, Meet Courtroom: The Supreme Court Declines to Immunize Contractors
The courthouse still smells like toner and consequences. And on April 22, 2026, the Supreme Court delivered a small, unfashionable message in a big, emotional setting: war does not automatically erase ordinary accountability for private actors.
What happened: Hencely v. Fluor goes back to court
In a 6-3 decision, the Court ruled that Army veteran Winston Tyler Hencely may pursue state-law tort claims against contractor Fluor Corporation tied to a 2016 suicide bombing at Bagram Airfield in Afghanistan. Justice Clarence Thomas wrote the majority opinion. Justice Samuel Alito dissented, joined by Chief Justice John Roberts and Justice Brett Kavanaugh.
The underlying facts are brutal. The Court record describes a Taliban operative, Ahmad Nayeb, working for Fluor on the base under the military’s “Afghan First” initiative, which required contractors to hire Afghans. During a Veterans Day 5K event in 2016, Nayeb detonated an explosive vest after Hencely confronted him, killing five people and wounding seventeen. Hencely suffered severe brain injuries and is permanently disabled.
Hencely sued under South Carolina law on negligence theories including negligent supervision and negligent retention. The Fourth Circuit had dismissed the case under a broad idea: when contractors operate under military command in wartime, state-law claims arising out of “combatant activities” are preempted. The Supreme Court rejected that sweeping rule and sent the case back down.
Plain English: the Court refused to invent a new immunity
- Preemption needs a real hook. State law yields when it conflicts with the Constitution or valid federal law. The majority said the Fourth Circuit’s blanket rule lacked grounding in text, statutes, or precedent.
- FTCA immunity is not a party favor. Fluor pointed to the Federal Tort Claims Act “combatant activities” exception (which limits suits against the federal government). The Court said that exception does not automatically extend to contractors.
- Existing contractor shields still exist, but they have boundaries. The Court discussed Boyle (when state law significantly conflicts with a federal interest and the government directed the challenged conduct) and Yearsley (contractors acting within validly conferred federal authority). The majority emphasized that the shield does not fit when the contractor allegedly acted outside authority or contrary to military instructions.
The tradeoff: war language versus courthouse access
The dissent warned that litigation can invite second-guessing of security arrangements on an active base in a war zone. That is not a frivolous concern. But the Orwell check is whether “combatant activities” becomes a magic phrase that turns negligence into inevitability and locks the courthouse door by default.
The Paine test is simpler: does the rule expand liberty or concentrate power? A blanket preemption doctrine would concentrate power where oversight is already thin: contracting chains, midnight paperwork, and the kind of “operational necessity” that never meets cross-examination. The Court did not canonize Hencely’s claims. It just said he can try to prove them.
Facts first, defenses second, immunity last, and only when earned. If war can erase accountability for private actors, what else will we let it erase next?
-
The Rent Is Set by Spreadsheet, Not by God
Federal Register notices all have the same personality: quiet, confident, and oddly powerful. No marching bands. No cable-news chyron. Just a table, a date, and the kind of “minor revision” that can redraw a family’s housing map.
We argue about housing like it is carved in granite: property rights, neighborhood identity, the moral drama of who “deserves” what. But plenty of the real action is clerical. A formula produces a number called Fair Market Rent, and that number can decide whether a voucher works like a key or reads like a polite note that says “good luck out there.”
HUD revises FY 2026 Fair Market Rents for seven areas
On April 21, HUD published a notice revising its fiscal year 2026 Fair Market Rents (FMRs) for seven areas, based on new survey data gathered by local public housing agencies. The revised numbers take effect May 21, 2026.
- Los Angeles-Long Beach-Glendale
- Napa
- San Luis Obispo-Paso Robles
- Asheville
- Transylvania County, North Carolina
- Albany, Oregon metro area
- Corvallis, Oregon metro area
HUD also used the notice to respond to public comments about the FY 2026 FMR process. That sounds like housekeeping until you remember what FMRs do: they help set the maximum rent levels that voucher assistance can support. If the ceiling is too low, “choice” shrinks to whatever units still fit under a number that no longer matches the market.
Plain English: the rent ceiling moved, but the clock still lags
FMRs are estimates of the 40th-percentile gross rents paid by recent movers. HUD recalculates them annually using its most current data, but the methodology necessarily lags the market. In the FY 2026 methodology, HUD describes that lag and how it updates and trends rents to the current fiscal year.
Lag is not a partisan talking point. It is a math fact with human consequences. When rents move fast and FMRs trail behind, voucher searches can turn into months of calls, dead ends, and dwindling options.
The Orwell check:
“Fair Market Rent” is a civic euphemism. It is not a moral verdict and not a real-time reading. It is a policy dial. Call it a dial and people start asking the right questions: who sets it, how often, using what data, with what lag, and what happens when it is wrong?
The liberty ledger: who gains choices, who loses them
The voucher is supposed to expand freedom: where to live, what commute is possible, what school zone is reachable. When FMRs lag, liberty gets rationed, and leverage shifts toward whoever controls scarce units in tight markets.
There is a property-rights angle too. Owners should not be shoved into bad deals or trapped in unpredictable administration. That is exactly why the price signal has to be honest and the program has to be competently run. Otherwise it is not a market. It is a maze.
The tradeoff: precision versus speed, and who pays for delay
More frequent updates can track volatility better but cost time and capacity. Slower nationwide datasets are cheaper and consistent but bake in delay. HUD’s comment responses underscore there is no perfect, more current, nationwide rent dataset that cleanly replaces what the agency uses now. Fair enough. But the real question remains: if the system is inevitably late, who bears the harm of lateness?
The Paine test:
Does this expand liberty, or concentrate power? FMRs done well make assistance usable in more places. Done poorly, they turn public aid into a permission slip that does not buy entry.
What accountability looks like
Congress should demand plain-language reporting on voucher success rates by market and payment standard policy, not just rent tables. HUD should publish revised areas, reasons for revision, and then audit outcomes afterward. Local housing authorities and city councils should treat these settings like a public meeting item, not an internal memo. Watchdogs should keep shining light on the gap between what the program promises and what it delivers.
If a revised table can change a family’s map, why do we tolerate a system where the map is so often outdated?
-
Falcon Fireworks for Freedom: GPS III SV10 Proves America Can Swap and Win
I smelled that rocket electricity, like the whole county lit the grill and fired the starters at the same time. Then I watched the Space Force roll a GPS bird into orbit, and the message hit like an AM radio sermon: reliability beats vibes, especially when jamming is on the menu.
Space Force celebrates GPS III SV10, the Falcon 9 swap, and the anti-jam pitch
On April 21, a Falcon 9 lifted off from Cape Canaveral with GPS III SV10, the 10th and final satellite for the GPS Block III run. Space Systems Command said SV10 was successfully launched on Falcon 9, and it tied the mission to the constellation’s Military Code capability built to fight jamming. The same source highlighted that the GPS III series is designed for three-times more accurate performance and eight-times more resistance to jamming. (ssc.spaceforce.mil)
Here is where the “fireworks” become procurement truth: the mission was originally supposed to fly on United Launch Alliance’s Vulcan Centaur, but Space Force swapped to Falcon 9 after issues showed up with Vulcan’s solid rocket boosters. Space.com laid out the rocket-swap story and the downstream shuffling.
Who benefits when the schedule gets tough, and the jamming threat is real?
If your enemies can jam the signal, your timeline has to be tougher than a brisket at 2 a.m. GPS is the precision backbone for positioning, navigation, and timing. GPS III is built to make the signal harder to mess with, and Space Systems Command emphasized M-code, the encrypted military signal designed to be jam-resistant, along with modern anti-jam design. (ssc.spaceforce.mil)
That means the warfighter benefits first. If location and timing stay clean, platforms, logistics, and operations do not wobble. Then the American public benefits too, since GPS touches navigation, financial timestamps, and transportation timing, even on ordinary Tuesdays when nobody is chanting slogans. (ssc.spaceforce.mil)
What the swap really says: deliver the capability, not the paper performance
Vulcan’s solid booster problems, as reported by Space.com, helped drive the move to Falcon 9. Space Systems Command also talked about mission assurance and protecting the system against jamming and interference. (ssc.spaceforce.mil)
The takeaway is simple: in a world where GPS accuracy and anti-jam capability matter for readiness and everyday services, the United States cannot afford fragility. Space Force celebrated completing the GPS Block III constellation with SV10, emphasizing M-code performance, stronger anti-jam resistance, improved accuracy, and robustness. (ssc.spaceforce.mil)
-
FISA Section 702 Is Expiring, So Washington Wants to Buy Your Life Off a Shelf
The newsroom fluorescents hum like a bad conscience. My coffee tastes like burnt compliance training. On my desk: printer paper, a spreadsheet of incentives, and the same old Washington trick dressed up in a newer hoodie.
It is called national security. It is called modernization. It is called Section 702.
As Section 702 of the Foreign Intelligence Surveillance Act (FISA) barrels toward an April 30, 2026 expiration, Congress is doing what Congress does when asked to stop you from being tracked like a tagged package: it negotiates. Slowly. Loudly. Conveniently.
Renewal fight, reform fight, and the data-broker loophole
Here is the verified part: Section 702 is set to expire on April 30, 2026 after a short extension. Lawmakers are split on whether to reauthorize it clean or add reforms that would require warrants for certain searches and close the “data broker loophole.” TechCrunch describes the deadlock, including the push to stop agencies from buying Americans’ personal data from commercial brokers, and notes the White House posture in favor of a simple reauthorization. It also points to a legal quirk that can keep surveillance running beyond an expiration date. The machine always has a backup generator.
Separately, a coalition including the Congressional Hispanic Caucus, the Congressional Asian Pacific American Caucus, and the Congressional Progressive Caucus put it in writing: close the data broker loophole and require a judicial warrant before the government accesses Americans’ sensitive information. Their letter says agencies have purchased Fourth Amendment-protected location data from brokers, and warns that combining those purchases with AI supercharges surveillance. It also flags who gets hit first: Black and brown communities, immigrants, activists, dissenters. Then everyone else.
Translation: your data, no warrant, no judge
Translation: if an agency needs a warrant to follow you, it can just buy your movements the way a marketing department buys a segment.
The committee-room argument is always the same: buying is different from searching. Purchasing is not surveillance. The Fourth Amendment becomes a speed bump, not a wall.
Washington’s tell is the paperwork logic: we did not break into your house, we just paid someone else who already did.
Here is the mechanism: a loophole turned into a procurement pipeline
Here is the mechanism: consumer apps and ad-tech systems vacuum up location data; brokers aggregate and resell it; agencies buy it because procurement is easier than probable cause. Section 702 sits behind it all, and Americans’ data gets swept up, then queried through “backdoor searches,” while reforms keep getting watered down.
Now add the accelerant: AI that can sift and pattern-match mountains of location points. The sources argue that purchased personal information, plus AI analysis, means surveillance at scale without an independent judicial check.
Follow the money: brokers get paid, you get watched
Follow the money: data brokers monetize your movements, and government buyers get convenience plus deniability. Build a program in-house and you invite audits, oversight, lawsuits, FOIA fights. Buy a feed and you can hide behind “commercially available information.” Surveillance laundering. Clean money, dirty data.
Mic drop: close the loophole in law, not in a press release. Require warrants with real teeth. Fund watchdogs who can audit procurement and data flows. Drag the contracts into daylight. Litigate where lawmakers stall. Organize where hearings perform. Vote like your phone is a tracking device, because it is.
-
New York Lights the Grill Under Coinbase and Gemini: Prediction Markets Are Gambling
Tonight the TV hums like an old grill light, and the air smells like burnt charcoal and hot take. Somewhere, an ad is begging you to “bet smart.” But this one is coming with a legal tag that reads: prediction market, not gambling.
New York AG Letitia James sues Coinbase and Gemini
According to the New York Attorney General, her office sued Coinbase Financial Markets and Gemini, Titan LLC for running illegal, unlicensed gambling operations in New York through their so-called prediction market platforms.
What the state says these platforms actually do
The core pitch, in the state’s telling, is simple: bet money on the outcome of events, including sports, entertainment, and elections. If the result is uncertain and outside the bettor’s control, New York says it fits the definition of gambling.
The complaint also alleges these platforms were available to New Yorkers over 18. And here’s where the smoke gets thicker: New York law, the AG notes, requires someone to be at least 21 to participate in mobile sports betting. So the state’s argument is that people can get pulled into the game before the official guardrails start.
No license, sidestepping taxes
The AG also argues Coinbase and Gemini have not obtained a license from the New York State Gaming Commission. In her view, that means they sidestep taxes that licensed casinos and mobile sports gambling platforms pay. Those taxes, per the AG, help fund public schools, sports programs for underserved youth, and problem gambling education and treatment.
What is New York asking for? Orders including fines, forfeiture of illegal profits, and restitution to customers, plus civil penalties pegged to the profits the companies made through the alleged unlawful actions.
Why this matters to sports fans, not just lawyers
Sports are the common language. In the modern era, the block party gets micro-bets and “financial-feeling” packaging. If New York is right that these platforms are operating as unlicensed gambling businesses, it is a signal that states will defend their regulatory frameworks even when the pitch wears tech glitter.
And if New York is wrong, the court will say so. Either way, there is a dispute about whether “event contracts” and prediction markets are just gambling with a new logo, and whether the companies properly registered and paid what licensed operators pay.
Bottom line: if you want to cash in on sports outcomes, you should get licensed, pay your share, and not hide behind fancy words. So is this the start of a real crackdown, or is New York just warming up the grill for the next headline?
-
Arlington just cut Jerry Jones a $273 million check with a smile and a spreadsheet
The committee-room air never changes. Fluorescent buzz. Stale coffee. A microphone that turns every resident into a wind-tunnel witness. And behind the dais, that soft confidence from people who act like the vote is a formality, not a decision.
On April 21, Arlington’s City Council approved a master agreement extending the Dallas Cowboys’ lease at AT&T Stadium through 2055 and committing up to $273 million in city money toward stadium improvements. The vote was 7-2. The Cowboys commit at least $750 million toward the broader renovation package. The city says its share is a “maintenance and operations” investment funded through previously approved venue taxes, not the general fund. And that is how the grift likes to dress: not as a handout, but as housekeeping.
AT&T Stadium opened in 2009. Seventeen years later, the city is back at the altar, sliding public dollars to Jerry Jones, owner of one of the most valuable sports franchises on Earth, because the building needs to stay “top-tier.” That phrase always shows up right before the public gets billed.
Translation: “Maintenance” is how a subsidy sneaks past your immune system
In the reporting and the city’s own announcement, this is the structure: Arlington pays up to $273 million; the team puts in at least $750 million; the lease term extends from 2040 to 2055. NBC DFW reported the city’s payments could run over 20 years starting in 2028. KERA noted the money comes from venue taxes already authorized by voters. The city’s release puts a ribbon on it, calling the Cowboys an economic driver and framing the spending as operations and security enhancements, including upgrades tied to federal SAFETY Act certification standards.
Translation: “security” is the all-purpose solvent. It dissolves skepticism. It makes oversight sound like a nuisance.
Here is the mechanism: municipal ownership turns into municipal servitude
City ownership is pitched as protection. In practice, it can become a trap door. If the city owns the building, it can be pressured into paying for “maintenance,” “operations,” or “capital improvements” because the asset is technically on the public ledger. Rational, until you notice who controls the revenue streams, who controls the schedule, and who benefits from the luxury arms race.
The stadium becomes a public balance-sheet liability and a private cash machine. Arlington’s press release lists the venue’s resume, like civic sainthood: Final Fours, NFL Draft, Cotton Bowl, WrestleMania, concerts. That list is not proof. It is a pitch deck. And we are the venture capitalists who do not get equity.
Follow the money: special taxes are still public money
Officials stress the funds come from venue taxes, not the general fund. Fine. That does not make it private. It makes it easier to spend without staring voters in the eyes again.
Meanwhile, the Cowboys lock in certainty through 2055. The city gets political cover: “We kept them here.” Fans are supposed to clap. Consultants are supposed to print graphs.
My mic-drop stays simple: if Arlington can approve $273 million for a billionaire playground, it can demand hard transparency, public audits of contracts, and real enforcement if promises don’t materialize. Otherwise this is just another generation of officials signing checks in the lobby corridor while the public gets told to applaud “economic drivers.”
-
Warning to Errors: NIH Turns Grants Into a Compliance Speedway
The air over the federal grants yard smells like fresh paper and burnt coffee. Somewhere in a server room, an error message is warming up like a grill getting hot. And on April 22, 2026, NIH reminded universities that leniency for Common Forms is about to end, while research security training language gets folded back into the Common Forms for the next cycle.
NIH announces the end of its Common Forms leniency period and upcoming system enforcement for research security training
I have seen this movie. NIH issued a Guide Notice telling the research community that system enforcement of Common Forms will move from warnings to hard errors. It also says Research Security Training certification language is being restored into the Common Forms so people have time to comply for the next cycle.
The moment the warning turns into an error, that is when the power grab gets real
NIH says the current leniency period ends on May 7, 2026, with the final AIDS standard receipt date for Cycle 1. Then, on May 8, 2026, system warnings change to errors that will stop submissions not using the compliant Common Forms. In other words, you can keep arguing with the customer service script until the smoke clears, but after that, the gate swings shut.
Now bring in Research Security Training. NIH also explains that SciENcv and the SciENcv system updates are deploying on April 22, 2026, adding the RST certification back to the Common Forms for individuals. NIH says that move targets applications with due dates on or after May 25, 2026. During the window when someone is submitting before that effective date, NIH says it will not hold individuals accountable for the portion of the certification tied to the training requirement effective for those later due dates.
Who benefits from the paperwork treadmill, besides the IT contractors and policy shops?
NIH frames this as implementation of requirements tied to the CHIPS and Science Act. The earlier NIH notice spells out the overall intent: covered individuals must certify they completed Research Security Training within a 12 month window, and institutions must certify compliance too. NIH says the training requirement is optional for now, with certifications effective for applications due on or after May 25, 2026, and that NIH recognizes specific training modules as meeting the requirement.
Scientific integrity should not become checkbox governance
Sure, there is a national-security rationale behind it. But when you turn integrity into a compliance script, you create a steady compliance workload. NIH says it is aligning implementation with statutory Research Security Training requirements and the Common Forms timeline, and it lays out a tight sequence: leniency ends May 7, errors begin May 8, RST certification language is restored on April 22, and the training requirement is aimed at due dates on or after May 25. Tight sequences squeeze humans, and humans miss details.
What this means for America: fewer chances for discovery, more chances for paperwork casualties
America funds research to push the frontier, not to keep the front office busy with error messages. When compliance becomes the main hurdle, the risk shifts from bad science to missed submissions. NIH is telling everyone exactly what is coming, and it is not hiding the dates. The question is whether the real-world implementation keeps the focus on integrity or drifts into checkbox governance.
When May 8 turns warnings into errors, will universities treat this like a speed bump or like a roadblock, and what gets hit first when the grants system tightens its grip?
-
Purdue’s Sentencing Delay, and the Small Fight for a Public Courtroom
I have sat through enough public meetings to recognize civic frustration on contact: folding chairs, stale air, and the slow realization that “procedure” can be a polite way to keep people out. Courtrooms have their own soundtrack. The language is tighter, the stakes are higher, and everything is supposedly neutral. Until the public shows up.
This week, they did. Outside a federal courthouse in Newark, opioid victims and their families made the oldest American argument: show up in person, stand your ground, and insist the people most affected are not an afterthought.
What happened: a one-week postponement, for a seat in the room
On Tuesday, U.S. District Judge Madeline Cox Arleo postponed Purdue Pharma’s criminal sentencing by a week after seeing victims of the opioid crisis gathered outside the courthouse. The hearing had been set up as videoconference-only. She moved it so victims could attend in person and be heard in the room.
When sentencing happens, she is expected to order Purdue to forfeit $225 million to the Justice Department, tied to a long-running federal resolution of Purdue’s opioid conduct and the company’s broader settlement structure.
If you are looking for a grand moral reversal, keep walking. A one-week delay is not a reckoning. It is not a cure. It is barely a speed bump.
But it is something the opioid story has too often lacked: an institution briefly acting like it remembers the public is supposed to be in the building.
The Paine test: does this serve the people, or the paperwork?
A remote-only sentencing for a company whose product helped ignite a national public health fire is concentrated convenience. It trims away the discomfort of witnesses in the room and turns a public act into a private-feeling transaction.
Video hearings have a place. They can reduce travel burdens and improve access for some. But a criminal sentencing is not a quarterly earnings call. The public does not watch justice as content. The public witnesses it as a check on power. That check works best when the institution is willing to endure the inconvenience of people.
The Orwell check: when “resolution” means closure without accountability
This saga is soaked in euphemism: “settlement,” “restructuring,” “global resolution,” “moving forward.” Those words often arrive right before responsibility gets turned into administrative finality.
Delaying sentencing to allow in-person victim attendance does not undo the machinery. But it punctures the language. It says, in courthouse English: this is not just professionals closing a file. The public gets a seat, not just a stream.
The liberty ledger and the tradeoff
- Who gains? Victims and families seeking the basics promised by the Crime Victims’ Rights Act: to be present, treated with fairness, and reasonably heard at sentencing. DOJ victim notification materials lay out those rights, including limits on excluding victims from public proceedings absent specific findings.
- Who is protected by distance? A process that runs smoother when grief is pixelated and the public is a background tab.
The tradeoff is real: remote technology can help with health, logistics, cost, and access. But “remote access” is different from “remote-only” in a case this publicly consequential. If courts want the benefits of technology without forgetting open courts, the boring answer is still the best one: hybrid access, clear instructions, and transparent reasons for any limits.
Postpone the sentencing so people can be there. Then do the harder thing: make the outcome legible and worthy of a tragedy that has taken so much. If we cannot manage that, what exactly are we sentencing, the company or our expectations?
-
An ‘AI-Native’ Hospital, Bought Off the Rack
The newsroom coffee tastes like burnt pennies. Outside, sirens duet with construction beeps. Inside, my inbox fills with press releases like confetti from a corporate wedding. This week’s bouquet: the University of Texas at Austin announcing a $750 million gift from Michael and Susan Dell to build what UT calls the country’s first “AI-native” medical center, projected to open in 2030.
Michael and Susan Dell fund an “AI-native” medical center at UT Austin with a $750 million gift
Here is the clean fact pattern. On April 21, 2026, UT announced a $750 million donation from the Michael and Susan Dell Foundation to launch a new advanced research campus with the UT Dell Medical Center as a centerpiece. UT says it expects to break ground this fall and that the medical center is projected to open in 2030. UT also says the Dells have now surpassed $1 billion in giving to the university.
A big academic medical center can do real good. Training. Clinical trials. Translational research. Better access to care if it is built that way. I am not allergic to building hospitals. I am allergic to how we are building the power system that decides what hospitals are for.
Translation: “AI-native” means “data-first,” and patients are the data
Translation: “AI-native” sounds like a stainless-steel miracle. In plain English anger, it usually means building the institution around data capture, algorithmic decision support, and infrastructure that makes those systems hard to avoid.
Start from the floor plan: sensors, workflow software, EHR integrations, cloud pipelines, model monitoring, vendor contracts that outlast a dean. Every hallway becomes a funnel for information. Every clinical decision becomes a chance to standardize, quantify, and later monetize. Not automatically evil. Automatically powerful. And power, in America, is a magnet for grift.
UT’s language is about improving patient care through AI, making the system more predictive and seamless. Fine. The question is never whether AI can help. The question is: help whom, under whose rules, with whose accountability, and with what escape hatch when it breaks.
Follow the money: philanthropy is the soft power wing of privatization
Follow the money: the Dells did not just write a check. They bought a lever. Naming rights are the receipt. The leverage is what comes next: priorities, partnerships, procurement, and prestige.
Universities love words like “catalyze” and “redefine.” That is PR fog. What this does is move a public institution’s center of gravity. When the biggest line item comes from a billionaire, every meeting starts with an unspoken survival math problem: keep the donor happy, keep the board calm, keep the pipeline of gifts flowing.
These deals are engineered to look like pure public benefit, and the hard choices show up later, quietly, in contracts, committees, and nondisclosure agreements.
Here is the mechanism: build the institution, lock in the vendors, normalize the ideology
Here is the mechanism: you do not need a conspiracy when you have incentives. An “AI-native” medical center needs compute and infrastructure, plus development, deployment, maintenance, monitoring, and compliance. That means vendors, often the same outfits selling the tools and the narrative.
Once you architect a hospital around AI, opting out becomes like opting out of electricity. Systems harden into policy. Pathways get encoded. Metrics get encoded. Then when harm happens, the institution points to the model, the benchmark, the “best practice.” Responsibility gets laundered through process.
The quiet part: this is about legitimacy, not just medicine
The quiet part: billionaire money buys legitimacy. It buys the feeling that our institutions still work, even as the public side gets hollowed out and the private side picks the locks.
So before the concrete dries, I want binding transparency on partnerships and vendor relationships, public-interest governance with real community power, independent audits of models and outcomes, ironclad protections against data misuse, and enforceable guarantees this does not become a concierge machine for the insured while everyone else gets told to download an app.
Mic drop: a $750 million check is not accountability. It is influence. Who is going to audit the contracts, the governance, and the data rules before “AI-native” becomes a polite synonym for donor-native medicine?
End of content
End of content