<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <title>Architecture on Xinwei Xiong (cubxxw) - AI, Open Source &amp; Nomad Blog</title>
    <link>https://cubxxw.com/tags/architecture/</link>
    <description>Tech blog by Xinwei Xiong — AI Builder, open source contributor and digital nomad sharing Kubernetes, Go, AI projects and travel.</description>
    <image>
      <title>Xinwei Xiong (cubxxw) - AI, Open Source &amp; Nomad Blog</title>
      <url>https://cubxxw.com/assets/og-image.png</url>
      <link>https://cubxxw.com/</link>
    </image>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 09:30:00 +0800</lastBuildDate>
    <atom:link href="https://cubxxw.com/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dissecting open-lovable: An App Generator That Tames the Raw API Without an Agent Framework</title>
      <link>https://cubxxw.com/ai-technology/posts/dissecting-open-lovable/</link>
      <pubDate>Mon, 29 Jun 2026 09:30:00 +0800</pubDate>
      <atom:updated>Mon, 29 Jun 2026 23:33:51 +0800</atom:updated>
      <dc:creator>熊鑫伟 (Xinwei Xiong)</dc:creator>
      <guid isPermaLink="true">https://cubxxw.com/ai-technology/posts/dissecting-open-lovable/</guid>
      <description>A full dissection of firecrawl/open-lovable (27k★, paste a URL and get a working React app in seconds), from product to code. Its most interesting trait isn&#39;t that it generates code — it&#39;s that it uses no agent framework, no Claude Agent SDK, no native tool-calling. Instead it hand-rolls an entire harness on top of the raw LLM API: a text DSL protocol, streaming regex parsing, truncation detection and recovery, manual context orchestration, plus a swappable cloud sandbox layer (E2B / Vercel Sandbox). This is a case study in taming the raw API.
</description>
      <category domain="category">AI &amp; Technology</category>
      <category domain="tag">AI</category>
      <category domain="tag">Agent</category>
      <category domain="tag">LLM</category>
      <category domain="tag">Architecture</category>
      <category domain="tag">Sandbox</category>
      <category domain="tag">Harness</category>
    </item>
    <item>
      <title>Building a Production-Grade AI Agent System from Scratch: A Full Architecture Breakdown of Relay</title>
      <link>https://cubxxw.com/ai-technology/posts/relay-agent-architecture-design/</link>
      <pubDate>Wed, 24 Jun 2026 10:00:00 +0800</pubDate>
      <atom:updated>Wed, 24 Jun 2026 14:18:19 +0800</atom:updated>
      <dc:creator>熊鑫伟 (Xinwei Xiong)</dc:creator>
      <guid isPermaLink="true">https://cubxxw.com/ai-technology/posts/relay-agent-architecture-design/</guid>
      <description>Using the Relay open-source job-search Agent project as a case study, this article fully breaks down every key design decision in a production-grade multi-agent system: why split a single Agent into 5, how to implement HITL checkpoints with LangGraph, how a three-tier LLM router precisely tracks costs, how a fabrication guard validates at runtime, and how a hybrid backend (Hono/Bun + FastAPI/Python) decouples cleanly. Whether you are building your first Agent PoC or pushing toward production, there are design patterns here you can take away.
</description>
      <category domain="category">AI &amp; Technology</category>
      <category domain="tag">AI</category>
      <category domain="tag">Agent</category>
      <category domain="tag">LangGraph</category>
      <category domain="tag">LLM</category>
      <category domain="tag">Architecture</category>
      <category domain="tag">TypeScript</category>
      <category domain="tag">Python</category>
      <enclosure url="https://cubxxw.com/images/blog/relay-agent-architecture.webp" type="image/jpeg" length="0" />
      <media:content url="https://cubxxw.com/images/blog/relay-agent-architecture.webp" medium="image"><media:description>Technical diagram showing the five-layer architecture of the Relay job-search Agent system: UI layer, API orchestration layer, Agent execution layer, shared services layer, and data and integration layer</media:description></media:content>
    </item>
    <item>
      <title>The Agent Engineering Map: Where Does That 98.4% of the Work Actually Live?</title>
      <link>https://cubxxw.com/ai-technology/posts/agent-engineering-the-98-percent-harness/</link>
      <pubDate>Wed, 17 Jun 2026 09:30:00 +0800</pubDate>
      <atom:updated>Wed, 24 Jun 2026 14:18:30 +0800</atom:updated>
      <dc:creator>熊鑫伟 (Xinwei Xiong)</dc:creator>
      <guid isPermaLink="true">https://cubxxw.com/ai-technology/posts/agent-engineering-the-98-percent-harness/</guid>
      <description>A panoramic map that treats Agent Engineering as a discipline. Starting from the widely cited claim that only 1.6% of Claude Code is AI decision logic while 98.4% is infrastructure, it walks the eight pillars one by one — orchestration, context, memory, tools, reliability, evaluation, cost, governance — explaining the gap each fills, its minimal implementation, and its failure boundary. It fuses 2025 to 2026 frontline engineering from Anthropic, OpenAI, Cognition, Manus, and Temporal, and lands on one line: the model is bought, the harness is built, and your entire engineering leverage lives in that 98.4%.
</description>
      <category domain="category">AI &amp; Technology</category>
      <category domain="tag">AI</category>
      <category domain="tag">Agent</category>
      <category domain="tag">LLM</category>
      <category domain="tag">Context Engineering</category>
      <category domain="tag">Architecture</category>
      <category domain="tag">MCP</category>
      <enclosure url="https://cubxxw.com/images/blog/agent-engineering-harness.webp" type="image/jpeg" length="0" />
      <media:content url="https://cubxxw.com/images/blog/agent-engineering-harness.webp" medium="image"><media:description>A technical diagram with a tiny agent loop at the center, surrounded by concentric rings of the eight pillars: orchestration, context, memory, tools, reliability, evaluation, cost, governance</media:description></media:content>
    </item>
  </channel>
</rss>
