<?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>AI on Cairo Cananea</title>
    <link>https://cairocananea.com.br/en/categories/ai/</link>
    <description>Recent content in AI on Cairo Cananea</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://cairocananea.com.br/en/categories/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Market for Exhaustion: The Strategic Risk of Using AI Without Data Governance</title>
      <link>https://cairocananea.com.br/en/posts/2026/07/custo-ia-sem-governan%C3%A7a-dados/</link>
      <pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://cairocananea.com.br/en/posts/2026/07/custo-ia-sem-governan%C3%A7a-dados/</guid>
      <description>What happens when companies use AI while fearing the loss of their proprietary knowledge? A Market for Exhaustion emerges: a cycle where only low-value data circulates while strategic knowledge stays locked away. Drawing on Arrow and Akerlof, this article shows how this dynamic impoverishes the market, examines how major vendors are responding, and argues that the solution lies in returning to companies control over the learning generated by their own use of AI.</description>
    </item>
    <item>
      <title>Memory, small models, and how to validate any of it</title>
      <link>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-4-memoria-modelos-validacao/</link>
      <pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-4-memoria-modelos-validacao/</guid>
      <description>Fourth and final article in the series on building Bloom, a multi-agent coaching agent, in one week. Covers long-term memory without vector search, the non-linear behavior of small models when swapping the underlying LLM, and the evaluation harness (LLM-as-a-judge, layered testing, per-call telemetry) used to validate every change.</description>
    </item>
    <item>
      <title>The prompt before the architecture</title>
      <link>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-3-prompt-antes-arquitetura/</link>
      <pubDate>Tue, 14 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://cairocananea.com.br/en/posts/2026/07/bloom-capstone-3-prompt-antes-arquitetura/</guid>
      <description>Third article in the series on building Bloom, a multi-agent coaching agent, in one week. Shows how to diagnose the right layer before overhauling architecture, prompt techniques that reduce conversational rigidity (information-goal states, few-shot examples, soft limits), the importance of honestly modeling the &amp;#39;unknown&amp;#39;, fallback path design, and why behavioral safety needs to be hard-coded, not left to the prompt alone.</description>
    </item>
    <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>
