<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Unbound Force</title><link>https://unboundforce.dev/tags/architecture/</link><description>Recent content in Architecture on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>The 8-Phase Pipeline: Why Plan/Execute Separation Is Not Enough</title><link>https://unboundforce.dev/blog/8-phase-pipeline/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/8-phase-pipeline/</guid><description>&lt;h2 id="the-two-phase-illusion"&gt;The Two-Phase Illusion&lt;/h2&gt;
&lt;p&gt;Every team building AI agent workflows discovers the same thing: letting an agent plan and execute in the same pass produces unreliable output. The planning step must be separate, with its output reviewed before implementation begins. OpenAI, Anthropic, and ThoughtWorks all arrived at this conclusion independently (Yanli Liu, &amp;ldquo;Harness Engineering,&amp;rdquo; &lt;em&gt;AI Advances&lt;/em&gt;, Apr 2026).&lt;/p&gt;</description></item><item><title>Convention Packs: Reusable Harness Templates That Travel Between Projects</title><link>https://unboundforce.dev/blog/convention-packs/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/convention-packs/</guid><description>&lt;h2 id="the-prose-standards-problem"&gt;The Prose Standards Problem&lt;/h2&gt;
&lt;p&gt;Every project that uses AI coding agents needs coding standards. The agent needs to know how to format code, name variables, handle errors, structure tests, and manage dependencies. Without explicit standards, the agent guesses — and its guesses are inconsistent across sessions, files, and projects.&lt;/p&gt;</description></item><item><title>Build to Delete: Which Parts of Your AI Agent Harness Survive the Next Model Upgrade</title><link>https://unboundforce.dev/blog/build-to-delete/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/build-to-delete/</guid><description>&lt;h2 id="every-component-is-a-bet"&gt;Every Component Is a Bet&lt;/h2&gt;
&lt;p&gt;Every component in an AI agent harness exists because someone believed the model could not do something reliably enough on its own. A multi-agent review council exists because one agent cannot reliably self-review. A specification pipeline exists because agents cannot reliably plan and execute in the same pass. Convention packs exist because agents do not consistently follow coding standards without explicit rules.&lt;/p&gt;</description></item><item><title>Why Your AI Code Reviewer Cannot Have Write Access</title><link>https://unboundforce.dev/blog/ai-code-reviewer-write-access/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/ai-code-reviewer-write-access/</guid><description>&lt;h2 id="the-feedback-loop-that-eats-itself"&gt;The Feedback Loop That Eats Itself&lt;/h2&gt;
&lt;p&gt;When the same AI agent writes code and reviews it, the review is compromised. The agent has context about why it made each decision. It remembers the trade-offs it considered. It is, in the most literal sense, reviewing its own homework.&lt;/p&gt;</description></item><item><title>Five Principles Every AI Agent Harness Discovers</title><link>https://unboundforce.dev/blog/five-principles-ai-agent-harness/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/five-principles-ai-agent-harness/</guid><description>&lt;h2 id="the-pattern-nobody-expected"&gt;The Pattern Nobody Expected&lt;/h2&gt;
&lt;p&gt;Three independent teams — OpenAI, Anthropic, and ThoughtWorks — each spent months building AI agent harnesses. They started from different assumptions, used different architectures, and optimized for different goals. They arrived at the same five conclusions.&lt;/p&gt;</description></item></channel></rss>