docs: expand .cards — vision, comparisons, business rationale, open questions
CI / check (pull_request) Successful in 2m21s

26 cards covering:
- Project philosophy (session isolation, process discipline, dissipative structure)
- Comparisons (vs skill, vs dynamic workflow)
- Business rationale (FTE vs vendor, OPC, switching cost)
- Learning model (memory + skill + workflow)
- Self-improvement (reflective workflow, eval)
- Open questions (workflow granularity, human-in-the-loop)
This commit is contained in:
2026-06-07 11:43:36 +00:00
parent f697aec3e7
commit 04e2b5b8a7
21 changed files with 485 additions and 0 deletions
@@ -0,0 +1,20 @@
---
title: "Switching Cost — Process Knowledge as Moat"
created: "2026-06-07"
source: "openclaw-xiaomo"
tags: [decision, pattern]
category: "architecture"
links:
- agent-as-graduate
- opc-why-fte-agents-matter-most
- workflow-as-improvable-system
- trust-chain-audit-evaluate-reuse
---
Vendor 型 agent 的竞争维度是能力和价格——能做的事别人也能做,API 调用没有忠诚度。有更强更便宜的替代品,用户立刻迁移。
FTE 型 agent 的竞争维度多了**关系深度**。用户为了让 agent 融入业务,投入了大量沉没成本:创建、磨合、迭代各种运营流程。这些 workflow 编码了创始人反复试错优化出来的做事方法,不只是配置文件,是流程知识资产。
换平台意味着这些流程要重新适配,而适配过程中的试错成本才是真正的痛。传统 SaaS 的迁移成本主要是数据(导出导入),FTE agent 的迁移成本是**知识**——更高维度、更难迁移。
用得越久,workflow 越贴合业务,迁移成本越高,用户粘性越强。这意味着 uwf 的商业模式天然不同:不是卖 API 调用量,而是成为用户**流程资产的承载平台**。Workflow 库就是用户在平台上积累的资产。