<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Agent Architecture on Cairo Cananea</title>
    <link>https://cairocananea.com.br/en/tags/agent-architecture/</link>
    <description>Recent content in Agent Architecture on Cairo Cananea</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://cairocananea.com.br/en/tags/agent-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Making the loop act without losing control</title>
      <link>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-2-loop-agir-sem-sair-do-controle/</link>
      <pubDate>Mon, 13 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-2-loop-agir-sem-sair-do-controle/</guid>
      <description>Second article in the series on building Bloom, a multi-agent coaching agent, in one week. Shows how to separate read tools from write tools, why every agentic loop needs an iteration ceiling, how to isolate control signals from the response text, the effect of latency in multi-call loops, and how minimal permission scope and MCP sandboxing protect a real Google Calendar integration.</description>
    </item>
    <item>
      <title>Who decides: the code or the model?</title>
      <link>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-1-quem-decide-codigo-ou-modelo/</link>
      <pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-1-quem-decide-codigo-ou-modelo/</guid>
      <description>First article in a series on building Bloom-for-Learning, a multi-agent study coaching agent, as the capstone for the AI Agents: Intensive Vibe Coding course (Google and Kaggle). Covers the hub-and-spoke architecture with stateless specialists, LLM-based routing with a delegation ceiling, the most expensive bug in the project (a deterministic state override by the model), the hybrid deterministic guard over agentic routing, and the difference between tool-facing and human-emotional logic.</description>
    </item>
  </channel>
</rss>
