<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" xml:lang="es"><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="https://amloii.github.io/feed.xml" rel="self" type="application/atom+xml" /><link href="https://amloii.github.io/" rel="alternate" type="text/html" hreflang="es" /><updated>2026-06-23T09:36:48+00:00</updated><id>https://amloii.github.io/feed.xml</id><title type="html">Daniel Gómez Domínguez</title><subtitle>AI Director &amp; systems architect. Agentic AI, LLM infrastructure, RAG, and production ML — from strategy to deployment.</subtitle><author><name>Daniel Gómez Domínguez</name><email>danigdominguez@gmail.com</email></author><entry xml:lang="en"><title type="html">Shipping agent graphs without burning your margin budget</title><link href="https://amloii.github.io/2026/05/05/agent-graph-margin-budgets.html" rel="alternate" type="text/html" title="Shipping agent graphs without burning your margin budget" /><published>2026-05-05T00:00:00+00:00</published><updated>2026-05-05T00:00:00+00:00</updated><id>https://amloii.github.io/2026/05/05/agent-graph-margin-budgets</id><content type="html" xml:base="https://amloii.github.io/2026/05/05/agent-graph-margin-budgets.html"><![CDATA[<p>Autonomous agents are cheap to demo and expensive to keep honest. The moment you wire “just one more tool” without a contract, your margin graph looks like a crypto wallet after a bridge hack.</p>

<h2 id="1-budget-the-graph-not-the-model">1. Budget the graph, not the model</h2>

<p>Most cost spikes are not raw token spend — they are <strong>unbounded fan-out</strong> and <strong>orphaned retries</strong>. Before choosing an orchestration library, answer three numbers on paper:</p>

<ul>
  <li>Max tool calls per user intent</li>
  <li>Max wall-clock per agent hop</li>
  <li>Max dollars per successful outcome (not per request)</li>
</ul>

<p>If you cannot answer those, you are not ready to productionize — you are cosplaying infrastructure.</p>

<h2 id="2-evaluators-are-part-of-the-dag">2. Evaluators are part of the DAG</h2>

<p>Treat evaluators as first-class nodes, not weekend notebooks. They should run on the same artifacts as production (prompt versions, memory snapshots, tool traces) and block promotion when drift exceeds your policy.</p>

<h2 id="3-memory-is-a-liability-ledger">3. Memory is a liability ledger</h2>

<p>Persistent memory is not “helpful context” — it is <strong>debt</strong>. Every write needs an owner, TTL, and audit strategy. Otherwise you will spend Q3 hunting silent poisoned entries that only appear on long-horizon tasks.</p>

<h2 id="4-multilingual-leadership-note">4. Multilingual leadership note</h2>

<p>I write in English on this site first because it is the lingua franca of the teams I advise day to day. When I cross-post externally, canonical URLs stay anchored here so Google (and recruiters parsing JSON résumés) always see one source of truth.</p>

<hr />

<p><em>Want this delivered with smaller essays? Subscribe via the footer embed.</em></p>]]></content><author><name>Daniel Gómez Domínguez</name><email>danigdominguez@gmail.com</email></author><summary type="html"><![CDATA[Lessons learned keeping agent swarms economically bounded while still passing safety evals.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://amloii.github.io/assets/img/og-default.svg" /><media:content medium="image" url="https://amloii.github.io/assets/img/og-default.svg" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>