---
title: "Discussion on \"What We Learned Running a Visible AI-Agent Workflow for a News Product\" | Hashnode"
description: "Discussion on \"What We Learned Running a Visible AI-Agent Workflow for a News Product\". Five practical lessons for coordinating AI agents with shared state, human approvals, clear ownership and attributable decisions."
url: "https://hashnode.com/posts/what-we-learned-running-a-visible-ai-agent-workflow-for-a-news-product/6aae94a099921a136e26a71c"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What We Learned Running a Visible AI-Agent Workflow for a News Product](https://informedclearly.hashnode.dev/what-we-learned-running-a-visible-ai-agent-workflow-for-a-news-product?utm_source=hashnode&utm_medium=feed)

Five practical lessons for coordinating AI agents with shared state, human approvals, clear ownership and attributable decisions.

Sep 19 · 4 min read · informedclearly.hashnode.dev  
Updated Sep 21  
Read the article

-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#devops](https://hashnode.com/tag/devops)
-   [#software-development](https://hashnode.com/tag/software-development)

## Written by

[Informed Clearly](https://hashnode.com/@informedclearly)

@informedclearly

  
[View profile](https://hashnode.com/@informedclearly)

Engineering and product notes from a multilingual, source-led news platform.

Informed Clearly builds a calmer, source-led way to understand the news across web and Android. Engineering notes will cover recommendations, accessibility, multilingual publishing, provenance and performance. https://informedclearly.com/

## Responses 3

Markdown supported · ⌘↵ to post

[Ascendra Ventures](https://hashnode.com/@ascendra-ventures)

[Oct 6](https://hashnode.com/posts/what-we-learned-running-a-visible-ai-agent-workflow-for-a-news-product/6aae94a099921a136e26a71c/comment/6ac45f8029ec5152f8b4fa08)

The exchange in the responses about stale approvals is the most practical part of this for me. An approval tied to the reviewed revision and its evidence, rather than a permit with no expiry, is the difference between a human in the loop and a human rubber stamp.

We use the same rule when agents work on client systems: the approval records what was reviewed, the commit or data snapshot it was checked against, and who approved it. If any of those moved before delivery, the approval no longer counts and the change goes back for review. It feels slow for about a week, and then it becomes the thing everyone relies on when someone asks why a change shipped.

The coordination framing matches what we see as well. With several agents running, the model is rarely the bottleneck. Knowing who owns which decision is.

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 19](https://hashnode.com/posts/what-we-learned-running-a-visible-ai-agent-workflow-for-a-news-product/6aae94a099921a136e26a71c/comment/6aaef4465575bf920e2b06cf)

The approval-as-object point matches something we hit building a Jira workflow validator: an approval can go stale between when it's raised and when a human actually clicks it, if the evidence underneath shifted in that gap (code changed, a dependency moved) while the approval object still shows the old state. Do you re-check the evidence at the moment of approval, or is an approval good against whatever it was checked against when it was first raised?

[Informed Clearly](https://hashnode.com/@informedclearly)

[Sep 21](https://hashnode.com/posts/what-we-learned-running-a-visible-ai-agent-workflow-for-a-news-product/6aae94a099921a136e26a71c/comment/6aaef4465575bf920e2b06cf#reply-6ab0da59ff412a23ce014e04)

That is exactly the failure mode an approval gate should defend against. We treat approval as being tied to the reviewed revision and evidence, not as a timeless permit. At decision and delivery time the workflow checks whether the task revision, code lineage, dependency state or test evidence changed. If they drifted, the approval is stale and the changed evidence must be reviewed again. The useful distinction is between “a human approved this snapshot” and “this snapshot is still the one being delivered.”
