TOMMASO MANGONE

TOMMASO MANGONE

Solo founder building DEALVY 🇮🇹

Badges

Gemologist
Gemologist
Tastemaker
Tastemaker
Tastemaker 10
Tastemaker 10
Tastemaker 5
Tastemaker 5
View all badges

Recently Supported

Clade
CladeAI COO that runs your team in tools you already use
Oakamo
OakamoYour quiet space for reading articles later.
Tinkerfont
TinkerfontFree font playground for live websites
PMB
PMBStop re-explaining your project to AI coding agents
Intelli
IntelliConvert leads into customers with AI conversations
Outpaint - Ad Reframe
Outpaint - Ad ReframeAI to turn vertical UGC into widescreen ads for Youtube & TV
ClinePass
ClinePassRun the best open-weights models in Cline
Agent Mode by Receiptor AI
Agent Mode by Receiptor AIBookkeeping assistant that runs receipt workflows end-to-end

Forums

OpenBoxp/openbox•

2mo ago

Would you trust an AI output if you could not see who approved it?

Been thinking about this after something that came up recently. Imagine an AI agent makes a recommendation that ends up influencing a customer workflow. The recommendation gets reviewed, approved, and eventually becomes part of how the team operates. Fast forward a few months and someone wants to understand why that decision was made.
The interesting part is that the technical history is usually still available. You can find the output. You can find the prompt. You can usually figure out which model generated it. What can be surprisingly difficult to find is the human context around the decision. Who reviewed the recommendation? Who approved it? What information did they have that made the recommendation seem reasonable at the time?
The more AI becomes part of everyday workflows, the more I find myself paying attention to that layer. Understanding the output matters, but understanding why someone trusted that output often matters just as much. A lot of conversations around AI accountability focus on the model. I suspect a lot of the missing context lives around the people making decisions with it.
Curious how your team is keeping track of that today, lets discuss it below...

View more