
		<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
				<title>Samuel Wang – AI-native Systems Builder</title>
				<link>https://wanglushan.cn/blog</link>
				<description>AI-native Systems Builder，专注把模糊意图、AI 协作、工程流程和运行证据组织成可执行、可验证、可持续迭代的产品系统。</description>
				<language>zh-CN</language>
				<managingEditor>wanglushan3344@gmail.com (samuel)</managingEditor>
				<webMaster>wanglushan3344@gmail.com (samuel)</webMaster>
				<lastBuildDate>Mon, 01 Jun 2026 00:00:00 GMT</lastBuildDate>
				<atom:link href="https://wanglushan.cn/tags/wiki-core/feed.xml" rel="self" type="application/rss+xml"/>
				
		<item>
			<guid>https://wanglushan.cn/blog/agent-harness-from-tool-calls-to-governance</guid>
			<title>Agent Harness 拆解：从工具调用到组织级治理</title>
			<link>https://wanglushan.cn/blog/agent-harness-from-tool-calls-to-governance</link>
			<description>Agent harness 不只是 tool calling，而是 context、memory、policy、adapter、validation、handoff 和证据层的组合。</description>
			<pubDate>Mon, 01 Jun 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>ai-agent</category><category>intentdna</category><category>agent-harness</category>
		</item>
	
		<item>
			<guid>https://wanglushan.cn/blog/company-brain-is-verifiable-workflow-layer</guid>
			<title>公司大脑不是聊天机器人，而是组织工作流的可验证执行层</title>
			<link>https://wanglushan.cn/blog/company-brain-is-verifiable-workflow-layer</link>
			<description>Company Brain 的关键不是一个入口，而是能把组织知识、角色边界、任务执行和证据沉淀连起来。</description>
			<pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>career-market</category><category>intentdna</category><category>company-brain</category>
		</item>
	
		<item>
			<guid>https://wanglushan.cn/blog/intentdna-governance-language-for-agent-harnesses</guid>
			<title>IntentDNA: harness 的治理语言和编译层</title>
			<link>https://wanglushan.cn/blog/intentdna-governance-language-for-agent-harnesses</link>
			<description>IntentDNA 不是新的聊天入口，而是把意图、约束、组织知识和运行证据编译进 agent harness 的治理层。</description>
			<pubDate>Sat, 30 May 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>intentdna</category><category>ai-agent</category><category>agent-harness</category>
		</item>
	
		<item>
			<guid>https://wanglushan.cn/blog/my-ai-native-workflow-from-vague-idea-to-running-system</guid>
			<title>我的 AI-native 工作流：从模糊想法到可运行系统</title>
			<link>https://wanglushan.cn/blog/my-ai-native-workflow-from-vague-idea-to-running-system</link>
			<description>记录我如何用 Codex、浏览器 QA、类型检查、构建验证和提交协议，把模糊想法推进成系统。</description>
			<pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>ai-native-delivery</category><category>frontend-systems</category><category>codex</category>
		</item>
	
		<item>
			<guid>https://wanglushan.cn/blog/skill-workflow-agent-productivity-route</guid>
			<title>为什么我认为 skill -&gt; workflow -&gt; agent 才是生产力路线</title>
			<link>https://wanglushan.cn/blog/skill-workflow-agent-productivity-route</link>
			<description>生产力不是从更松散的 agent 开始，而是从可复用 skill、可验证 workflow 和可治理 agent 逐层上升。</description>
			<pubDate>Fri, 29 May 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>ai-agent</category><category>ai-native-delivery</category><category>workflow</category>
		</item>
	
		<item>
			<guid>https://wanglushan.cn/blog/workflow-first-agent-design-principles</guid>
			<title>为什么松散 agent 不好用：workflow-first agent 的设计原则</title>
			<link>https://wanglushan.cn/blog/workflow-first-agent-design-principles</link>
			<description>松散 agent 缺少边界、回放和验收。workflow-first agent 先定义工作系统，再让 agent 执行。</description>
			<pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate>
			<author>wanglushan3344@gmail.com (samuel)</author>
			<category>wiki-core</category><category>ai-agent</category><category>workflow</category><category>validation</category>
		</item>
	
			</channel>
		</rss>
	