<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pygocen · Blog</title><link>https://pygocen.com/blog</link><atom:link href="https://pygocen.com/feed.xml" rel="self" type="application/rss+xml"/><description>Notes from building products, fixing what is stuck, and putting AI agents to work.</description><language>en-gb</language><lastBuildDate>Wed, 23 Sep 2026 09:00:00 GMT</lastBuildDate><item><title>The model never does the arithmetic: letting an AI agent write your analysis without trusting its numbers</title><link>https://pygocen.com/blog/the-model-never-does-the-arithmetic</link><guid isPermaLink="true">https://pygocen.com/blog/the-model-never-does-the-arithmetic</guid><pubDate>Wed, 23 Sep 2026 09:00:00 GMT</pubDate><author>hello@pygocen.com (Edoardo Pirani)</author><description>How we let an agent write valuation assumptions and an investment thesis for 32 companies, twice a day, unattended, and why not one number in the workbook comes from the model. Fixed inputs, a schema on the way out, a second computation, and a job that checks the work actually landed.</description><category>ai agents</category><category>guardrails</category><category>data</category><category>finance</category></item><item><title>Nobody was told: why silence is the failure mode of alerting</title><link>https://pygocen.com/blog/silence-is-the-failure-mode-of-alerting</link><guid isPermaLink="true">https://pygocen.com/blog/silence-is-the-failure-mode-of-alerting</guid><pubDate>Wed, 26 Aug 2026 09:00:00 GMT</pubDate><author>hello@pygocen.com (Edoardo Pirani)</author><description>A watchdog died 38 times in a week and every dashboard stayed green. Alerting can only report what someone thought to alarm on, so its failure mode is silence. The five rules we run our systems by, each one paid for by an incident.</description><category>monitoring</category><category>alerting</category><category>reliability</category><category>automation</category></item><item><title>Beyond prompt engineering: the five layers of working with AI agents</title><link>https://pygocen.com/blog/five-layers-of-ai-agent-engineering</link><guid isPermaLink="true">https://pygocen.com/blog/five-layers-of-ai-agent-engineering</guid><pubDate>Tue, 28 Jul 2026 09:00:00 GMT</pubDate><author>hello@pygocen.com (Edoardo Pirani)</author><description>Prompt, context, environment, loop, graph. What each layer of AI agent engineering decides, the failure it fixes, when to climb, when to stop, and the two layers the ladder leaves out, from a team that runs a dozen agents on its own products.</description><category>ai agents</category><category>engineering</category><category>automation</category></item></channel></rss>