<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Python on Mathias WOLFF</title><link>https://www.blog-des-telecoms.com/en/tags/python/</link><description>Recent content in Python on Mathias WOLFF</description><generator>Hugo</generator><language>en-US</language><copyright>&lt;a href="https://www.blog-des-telecoms.com"&gt;Blog des télécoms&lt;/a&gt; © 2009 - 2026 by &lt;a href="https://www.linkedin.com/in/mathias-wolff-47a7941/"&gt;Mathias WOLFF&lt;/a&gt; is licensed under &lt;a href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;CC BY-NC-SA 4.0&lt;/a&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/cc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/by.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/nc.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;&lt;img src="https://mirrors.creativecommons.org/presskit/icons/sa.svg" style="max-width: 1em;max-height:1em;margin-left: .2em;"&gt;</copyright><lastBuildDate>Tue, 21 Jul 2026 18:13:25 +0200</lastBuildDate><atom:link href="https://www.blog-des-telecoms.com/en/tags/python/index.xml" rel="self" type="application/rss+xml"/><item><title>From Manifesto to Code: How argentic-mw Runs Its Agents</title><link>https://www.blog-des-telecoms.com/en/blog/from-manifesto-to-code/</link><pubDate>Thu, 23 Jul 2026 09:00:00 +0200</pubDate><guid>https://www.blog-des-telecoms.com/en/blog/from-manifesto-to-code/</guid><description>&lt;p&gt;In the &lt;a
 href="https://www.blog-des-telecoms.com/en/blog/manifeste-supervised-agents"
 
 
&gt;first post of this series&lt;/a&gt;, I laid out a definition and a position: a supervised agent is a scheduled worker that executes a deterministic plan, where the LLM steps in only at extension points where it is useful, and where everything else is explicit, traceable, replayable code. Four pillars followed, determinism, control, auditability and token efficiency, which I presented as properties verifiable on a trace rather than as slogans. In the &lt;a
 href="https://www.blog-des-telecoms.com/en/blog/build-vs-buy-decision-framework"
 
 
&gt;second post&lt;/a&gt;, I proposed a six-criterion decision framework to compare this approach to full-LLM platforms and orchestration frameworks, and I concluded that for scheduled business pipelines with audit and bounded-cost requirements, the custom core remained the coherent answer, even at the price of a real boot cost.&lt;/p&gt;</description></item></channel></rss>