<?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 Safety on Cairo Cananea</title>
    <link>https://cairocananea.com.br/en/tags/ai-safety/</link>
    <description>Recent content in AI Safety on Cairo Cananea</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <lastBuildDate>Tue, 14 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://cairocananea.com.br/en/tags/ai-safety/index.xml" rel="self" type="application/rss+xml" />
    <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>
  </channel>
</rss>
