<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systems Integration on Ivaldo de Oliveira Batista Júnior</title><link>https://ivaldo.eti.br/tags/systems-integration/</link><description>Recent content in Systems Integration 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/systems-integration/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><item><title>Does Your Business Depend on External APIs? How to Keep One Failure From Stopping Everything</title><link>https://ivaldo.eti.br/blog/external-api-resilience-business-continuity/</link><pubDate>Mon, 16 Nov 2026 18:30:00 -0300</pubDate><guid>https://ivaldo.eti.br/blog/external-api-resilience-business-continuity/</guid><description>&lt;p&gt;At 10 a.m. on a Monday, the shipping-rate provider slows down. It doesn&amp;rsquo;t go down — it just starts responding in 40 seconds instead of 400 milliseconds.&lt;/p&gt;
&lt;p&gt;Within minutes, checkout freezes. Server connections are exhausted waiting for replies. The product catalog, which has nothing to do with shipping, slows down too because it shares the same resources. The support team can no longer look up orders. The dashboard says the site is &amp;ldquo;up,&amp;rdquo; but nobody can buy anything.&lt;/p&gt;</description></item></channel></rss>