<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Manifesto on Unladen swallow - Olivier Wulveryck</title>
    <link>https://blog.owulveryck.info/tags/manifesto.html</link>
    <description>Recent content in Manifesto on Unladen swallow - Olivier Wulveryck</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Olivier Wulveryck</copyright>
    <lastBuildDate>Fri, 17 Jul 2026 18:42:49 +0200</lastBuildDate>
    <atom:link href="https://blog.owulveryck.info/tags/manifesto/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Four Pillars, One Loop: A Manifesto Is Not a Compass</title>
      <link>https://blog.owulveryck.info/2026/07/17/manifesto-through-the-loop.html</link>
      <pubDate>Fri, 17 Jul 2026 10:00:00 +0200</pubDate>
      <guid>https://blog.owulveryck.info/2026/07/17/manifesto-through-the-loop.html</guid>
      <description>I liked the AI-Driven Development Manifesto until I saw it implemented as guiding principles. A manifesto is raw material; guiding principles are what you refine from it, and the refining is work nobody can do for you. This article does that work pillar by pillar, reading each value (Method over Model, Ownership over Delegation, Understanding over Acceptance, Outcome over Output) from inside the agentic loop, and ends with principles a platform can execute.</description>
    </item>
  </channel>
</rss>
