<?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/"><channel><title>LLM Systems on Yuchen Du</title><link>https://dudusoar.github.io/tags/llm-systems/</link><description>Recent content in LLM Systems on Yuchen Du</description><generator>Hugo -- 0.164.0</generator><language>en-us</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dudusoar.github.io/tags/llm-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Separate Schemas, Prompts, Tools, Workflows, and Memory in an LLM System</title><link>https://dudusoar.github.io/posts/llm-system-architecture/01-five-layer-llm-system/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/01-five-layer-llm-system/</guid><description>Why an LLM decision system needs five separable layers rather than one increasingly large prompt.</description></item><item><title>Separate Offline Memory Extraction from Online Action Execution</title><link>https://dudusoar.github.io/posts/llm-system-architecture/02-offline-memory-online-action/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/02-offline-memory-online-action/</guid><description>A clean LLM architecture separates the production of reusable experience from its read-only use during online decisions.</description></item><item><title>Separate Facts from Model Judgment in LLM Schemas</title><link>https://dudusoar.github.io/posts/llm-system-architecture/03-schema-design-facts-and-judgment/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/03-schema-design-facts-and-judgment/</guid><description>A schema preserves the boundary between computed facts, model judgments, explicit rationale, and external feedback.</description></item><item><title>Separate Plausible Environments from LLM Task Distributions</title><link>https://dudusoar.github.io/posts/llm-system-architecture/04-environments-and-task-distributions/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/04-environments-and-task-distributions/</guid><description>Reliable evaluation separates plausible executable environments from meaningful LLM task distributions.</description></item><item><title>Treat the Prompt as a Decision Interface, Not a State Dump</title><link>https://dudusoar.github.io/posts/llm-system-architecture/05-prompt-as-decision-interface/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/05-prompt-as-decision-interface/</guid><description>A prompt follows the order of an actual decision and keeps facts, memory, tools, actions, and runtime logic in separate layers.</description></item><item><title>Treat LLM Evidence Tools as Read-Only Interfaces</title><link>https://dudusoar.github.io/posts/llm-system-architecture/06-tools-as-read-only-evidence-interfaces/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/06-tools-as-read-only-evidence-interfaces/</guid><description>Evidence tools expose structured facts and deterministic calculations without making decisions on the model&amp;#39;s behalf.</description></item><item><title>Use the Action Space to Anchor LLM System Design</title><link>https://dudusoar.github.io/posts/llm-system-architecture/07-action-space-as-design-anchor/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/07-action-space-as-design-anchor/</guid><description>Define what an LLM is allowed to change before designing its schemas, prompts, tools, workflows, and memory.</description></item><item><title>Establish Fact Ownership and Evidence Provenance in LLM Systems</title><link>https://dudusoar.github.io/posts/llm-system-architecture/08-fact-ownership-and-provenance/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/08-fact-ownership-and-provenance/</guid><description>Every fact, interpretation, proposal, and outcome in an LLM system needs a clear owner and a traceable evidence lineage.</description></item><item><title>Share Only Modules Whose Meaning Survives a Method Change</title><link>https://dudusoar.github.io/posts/llm-system-architecture/09-share-only-stable-meaning/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/09-share-only-stable-meaning/</guid><description>Share code across LLM methods only when its meaning, lifecycle, failure handling, and tests remain unchanged.</description></item><item><title>Give Every Decision Point a Shared Information Boundary</title><link>https://dudusoar.github.io/posts/llm-system-architecture/10-shared-information-boundary/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/10-shared-information-boundary/</guid><description>Fair online comparison requires every method to decide from the same semantic snapshot and the same boundary on future information.</description></item><item><title>Use Only Observable and Executable Training Targets</title><link>https://dudusoar.github.io/posts/llm-system-architecture/11-observable-and-executable-training-targets/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://dudusoar.github.io/posts/llm-system-architecture/11-observable-and-executable-training-targets/</guid><description>A strong teacher result is a valid target only when the model can observe its basis and execute the same action.</description></item></channel></rss>