<?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>Agent Runtime on TimoNova Tech Stack</title><link>/en/tags/agent-runtime/</link><description>Recent content in Agent Runtime on TimoNova Tech Stack</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0800</lastBuildDate><atom:link href="/en/tags/agent-runtime/index.xml" rel="self" type="application/rss+xml"/><item><title>The Evolution of AI Application Architecture: Methods Move into the Model, Boundaries Stay in Reality</title><link>/en/posts/ai-application-architecture-evolution/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0800</pubDate><guid>/en/posts/ai-application-architecture-evolution/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;: AI application architecture will be divided again according to responsibility. Cognitive structures that help models understand, reason, plan, remember, and correct themselves will gradually be internalized by stronger models and runtimes. Structures that define where goals come from, how systems connect to reality, who may act, what constraints apply, and how outcomes are proven cannot be self-granted by a model—and will not disappear. Architecture will shift from compensating for model weaknesses to establishing trustworthy real-world boundaries for powerful actors.&lt;/p&gt;</description></item><item><title>Agent Evolution Series (5): A Global View — Why the Three Paths Ultimately Converge</title><link>/en/posts/agent-evolution-convergence/</link><pubDate>Fri, 29 May 2026 00:00:00 +0800</pubDate><guid>/en/posts/agent-evolution-convergence/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;: The three paths ultimately converge because real tasks simultaneously require understanding the current situation, reusing historical experience, and executing real actions. The endgame for agents is not being better at conversation, but becoming a governed goal-completion system: understanding context, consolidating experience, calling tools, executing tasks, and accepting permissions, auditing, rollback, and user control.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is the final article in the Agent Evolution Series.&lt;/p&gt;
&lt;p&gt;In the previous four articles, we&amp;rsquo;ve already deconstructed the three paths separately: the execution path, the self-evolution path, and the personal context path, as well as the final form they may form after convergence. The first three articles were more like looking down each path: what it is, why it emerged, what stages it goes through, and where it ultimately leads. The fourth article put the three paths into the same system, discussing how they combine into a governed Agent Runtime.&lt;/p&gt;</description></item><item><title>Agent Evolution Series (4): The Final Form — Governed Agent Runtime</title><link>/en/posts/agent-evolution-final-form/</link><pubDate>Thu, 28 May 2026 00:00:00 +0800</pubDate><guid>/en/posts/agent-evolution-final-form/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;: The final form of agents is not one path winning over the others, but the convergence of execution, self-evolution, and personal context into a governed Agent Runtime. This system consists of an understanding layer, a learning layer, an action layer, and a governance layer. Key capabilities include context, memory, skills, tool execution, permissions, auditing, and rollback.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is the fourth article in the Agent Evolution Series.&lt;/p&gt;
&lt;p&gt;The first three articles discussed three paths:&lt;/p&gt;</description></item><item><title>Agent Evolution Series (1): The Execution Path — From Answering to Doing</title><link>/en/posts/agent-evolution-execution-path/</link><pubDate>Mon, 25 May 2026 00:00:00 +0800</pubDate><guid>/en/posts/agent-evolution-execution-path/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;: The core of the execution path is moving agents from &amp;ldquo;giving advice&amp;rdquo; to &amp;ldquo;completing tasks.&amp;rdquo; It will evolve from tool calling to browser operations, local automation, and governed action layers. The real moat isn&amp;rsquo;t how many tools you can call, but how many things you can stably accomplish within the constraints of permissions, auditing, and rollback.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This is the first article in the Agent Evolution Series.&lt;/p&gt;
&lt;p&gt;The series is divided into five parts: the first three deconstruct the three main agent paths, the fourth discusses the final form after convergence, and the fifth addresses a more fundamental question: why agents evolve along these paths.&lt;/p&gt;</description></item></channel></rss>