张凌豪Linghao Zhang
EN
1/2 养成优先开发的整体框架。
2/2 三层认知架构。

arXiv2026预印本独立作者

Nurture-First Agent Development: Building Domain-Expert AI Agents Through Conversational Knowledge Crystallization

Linghao Zhang

arXiv 预印本, 2026

摘要

The emergence of large language model (LLM)-based agent frameworks has shifted the primary challenge in building domain-expert AI agents from raw capability to effective encoding of domain expertise. Two dominant paradigms—code-first development, which embeds expertise in deterministic pipelines, and prompt-first development, which captures expertise in static system prompts—both treat agent construction as a discrete engineering phase preceding deployment. We argue that this sequential assumption creates a fundamental mismatch with the nature of domain expertise, which is substantially tacit, deeply personal, and continuously evolving. We propose Nurture-First Development (NFD), a paradigm in which agents are initialized with minimal scaffolding and progressively grown through structured conversational interaction with domain practitioners. The central mechanism is the Knowledge Crystallization Cycle, whereby fragmented knowledge embedded in operational dialogue is periodically consolidated into structured, reusable knowledge assets. We formalize NFD through: (1) a Three-Layer Cognitive Architecture organizing agent knowledge by volatility and personalization degree; (2) the Knowledge Crystallization Cycle with formal definitions of crystallization operations and efficiency metrics; and (3) an operational framework comprising a Dual-Workspace Pattern and Spiral Development Model. We discuss the conditions, limitations, and broader implications of NFD for human-agent co-evolution.

引用

Linghao Zhang, “Nurture-First Agent Development: Building Domain-Expert AI Agents Through Conversational Knowledge Crystallization”, arXiv 预印本, 2026.

深入解读

专家智能体不是造出来的,是养出来的。

一种开发范式:智能体从最少的脚手架起步,在与使用者的结构化对话中逐步长大。

问题在哪

领域智能体通常有两种造法。代码优先,把专业知识写进确定性的流水线;提示词优先,把专业知识写进一段很长的系统提示。两者都把构建当作部署之前就结束的阶段。

这个假设和专业知识的实际样子对不上。专业知识大多是隐性的、个人的,而且一直在变,很难事先写清楚。

关键想法

让开发和部署同时发生。智能体从小开始,在日常使用中长大。核心机制是知识结晶循环:日常对话里零散的知识,定期沉淀为结构化、可复用的资产,这些资产又塑造下一轮对话。

图版 1 整体框架:三层知识架构位于四阶段结晶循环之内,外加两个工作区和随时间展开的螺旋。

架构

知识按变动频率和个人化程度分层。宪法层存放身份和规则,每次会话都加载;技能层存放模块和参考资料,按需加载;经验层存放日志和案例,用语义检索。

图版 2 三层结构:结晶把知识向上提炼,落地把知识向下带回。

由此有两种工作方式。双工作区模式把批量修改的“手术台”和日常对话的“养成台”分开,共用一个文件系统。螺旋开发模型让脚手架、养成和结晶交替进行。

适用在哪

论文并不认为这种范式处处更好。它适合这样的情形:专业知识大多是隐性的、因人而异,而且一直在变;使用者通过对话和智能体协作;调出使用者自己过去的判断有价值。如果专业知识可以完全形式化、也不再变化,比如报税表格处理,代码优先更合适。

还没做的

起步阶段的智能体帮不上太多忙,使用者可能因此坚持不下去,而养成恰恰需要长期投入。养成出来的知识质量很难客观评估,智能体还可能把使用者的偏见和专业知识一起学进去。结晶目前仍要半人工地引导。要定量证明这种范式的优势,还需要多名从业者参与、评价标准统一、并与代码优先和提示词优先对比的对照研究。我有一个开源仓库和这个想法很接近:personal-knowledge-wiki。

100%

↑↓ 选择↵ 打开