<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI Architecture on Ivaldo de Oliveira Batista Júnior</title><link>https://ivaldo.eti.br/tags/ai-architecture/</link><description>Recent content in AI Architecture on Ivaldo de Oliveira Batista Júnior</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Ivaldo de Oliveira Batista Júnior</copyright><lastBuildDate>Mon, 16 Nov 2026 19:30:00 -0300</lastBuildDate><atom:link href="https://ivaldo.eti.br/tags/ai-architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Your AI Can Execute Operations in Your Systems. Who Controls What It Is Allowed to Do?</title><link>https://ivaldo.eti.br/blog/ai-agent-governance-permissions-control/</link><pubDate>Mon, 16 Nov 2026 19:30:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/ai-agent-governance-permissions-control/</guid><description>&lt;p&gt;Until recently, AI inside companies answered questions. It summarized documents, drafted text, and classified requests. If it got something wrong, a person read the answer and decided what to do.&lt;/p&gt;
&lt;p&gt;Now AI is starting to &lt;strong&gt;act&lt;/strong&gt;. Agents connected to ERPs, CRMs, and internal APIs can create orders, change customer records, issue refunds, open tickets, and message customers.&lt;/p&gt;
&lt;p&gt;The promise is real: less repetitive work, faster service, processes that keep running outside business hours. So is the risk. &lt;strong&gt;An agent that can execute an operation can execute it wrongly, twice, for the wrong customer, or at a volume nobody anticipated.&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>